JP2016045926A - Ward medicine business support system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a ward medicine business support system capable of achieving efficiency of a business of a ward pharmacist.SOLUTION: A ward medicine business support system 10 comprises: an acquisition processing part 111 for acquiring a check result of prescription checking which determines whether or not, one or plural first confirmation items are proper about prescription data; and a display control part 112 for displaying a first display area for displaying a determination result of one or plural first confirmation items for every patient, based on the check result of the prescription checking. The display control part 112 divides corresponding display columns corresponding to the respective first confirmation items in the first display area, for displaying a first division area for displaying confirmation priority and a second division area for displaying presence/absence of confirmation..SELECTED DRAWING: Figure 1

Description

  The present invention relates to a ward drug operation support system for supporting a ward drug operation performed by a pharmacist in a ward of a medical institution.

In a medical institution such as a hospital, prescription data is issued by inputting prescription contents into an electronic medical record system or the like, and medicines are dispensed based on the prescription data. Thereafter, the medicine dispensed based on the prescription data is taken by a patient admitted to the ward. A prescription inspection system is known that can perform a prescription check that automatically determines the suitability of the prescription data before dispensing medicine based on the prescription data (see, for example, Patent Document 1). The pharmacist who dispenses the drug (hereinafter referred to as “dispensing pharmacist”) confirms whether the prescription content is appropriate according to the check result of the prescription check, and makes a question inquiry to the doctor if necessary. May be executed.

  In recent years, a pharmacist (hereinafter referred to as “ward pharmacist”) is sometimes performed in a ward where patients are hospitalized. The ward drug business is a business that is subject to the ward drug business operation addition, for example, grasping drug administration / injection status, grasping and disseminating drug safety information, etc., and consultation demand from medical staff, Confirmation of drugs to be brought into hospital and proposal of medication plan, confirmation of interaction before administration when two or more drugs are administered simultaneously, detailed explanation before administration related to high-risk drugs for patients, etc. The administration includes the calculation of the flow rate or the dosage, and other operations (operations specified by the Notification of the Bureau of Medical Affairs as necessary).

JP 2013-125377 A

  However, it is not easy for the ward pharmacist to carry out the work while judging the priority of the work that needs to be performed.

  An object of the present invention is to provide a ward drug operation support system that can improve the efficiency of the operation of a ward pharmacist.

  The ward drug business support system according to the present invention includes an acquisition processing unit that acquires a check result of a prescription check that determines whether or not one or more first confirmation items are appropriate for prescription data, and the check of the prescription check A display control unit that displays, for each patient, a first display region that displays a determination result of one or more of the first confirmation items based on the result. Then, the display control unit divides a display field corresponding to each of the first confirmation items in the first display area, and displays a first divided area for displaying the priority of confirmation and a second for displaying confirmation. Display the divided area.

  According to the present invention, by referring to the first display area, it is possible to easily grasp the priority of confirmation of the first confirmation item and the presence / absence of confirmation of each patient. Therefore, for example, the ward pharmacist can efficiently perform the work with reference to the confirmation priority of the first confirmation item and the presence or absence of confirmation.

  In addition, the acquisition processing unit sets a confirmation condition for one or a plurality of second confirmation items that are set in advance separately from the first confirmation item for either or both of the prescription data and the patient corresponding to the prescription data. A second display that further acquires a check result of a condition check for determining whether or not the second check item is satisfied, and displays the determination result of one or a plurality of the second confirmation items based on the check result of the condition check. It is conceivable to display the first divided area and the second divided area by displaying the area for each patient and dividing the display column for each of the second confirmation items in the second display area.

  Thereby, by referring to the first display area and the second display area, it is possible to easily grasp the priority of confirmation of the first confirmation item and the second confirmation item, the presence or absence of confirmation, etc. for each patient. Is possible. Accordingly, for example, the ward pharmacist can efficiently perform the work with reference to the priority of confirmation of the first confirmation item and the second confirmation item, the presence or absence of confirmation, and the like.

  Further, the display control unit is configured to display the first confirmation item determined to be inappropriate by the prescription check and the second display item corresponding to the second confirmation item determined to satisfy the confirmation condition by the condition check. It is conceivable to display the priority of confirmation and the presence / absence of confirmation only in the one divided area and the second divided area. Furthermore, it is conceivable that the display control unit displays the first divided area in a display mode that is predetermined according to the priority. Thereby, it is possible to easily grasp the necessity of confirmation of the first confirmation item and the second confirmation item, the priority, the presence or absence of confirmation, etc. for each patient.

  The ward drug business support system includes one or a plurality of first client terminals having an operation unit that receives a confirmation operation of the first confirmation item and the second confirmation item, and the display control unit includes the operation unit. It is conceivable to display that the confirmation has been made in the second divided area of the first confirmation item and the second confirmation item in response to the confirmation operation for. Here, it is conceivable that the first client terminal is a terminal operated by a ward pharmacist who performs work in a ward in which a patient is hospitalized.

  The ward drug operation support system includes one or a plurality of second client terminals operated by a dispensing pharmacist who performs operations in a dispensing room where a dispensing operation based on the prescription data is performed, and the display control unit includes the display controller It may be possible to display on the second client terminal whether or not the first confirmation item and the second confirmation item are confirmed by the first client terminal.

  In addition, the display control unit may display the first divided area of the first confirmation item and the second confirmation item on which the confirmation operation has been performed in a predetermined display mode corresponding to confirmed. Conceivable. Further, the display control unit displays the display mode of the first divided area of the first confirmation item and the second confirmation item, and the pharmacist who performed the confirmation operation of the first confirmation item and the second confirmation item. It is possible to change between other pharmacists.

  Further, the ward drug business support system stores information processing time required for confirming each item included in the first confirmation item and the second confirmation item and scheduled work time corresponding to each ward pharmacist. And a schedule creation processing unit that creates a confirmation schedule for each of the first confirmation item and the second confirmation item for each ward pharmacist based on the processing time and the scheduled work time. Thereby, the said confirmation schedule is created automatically and the efficiency of the operation | work by a ward pharmacist can be aimed at. Moreover, the omission of confirmation of the first confirmation item and the second confirmation item is also suppressed.

  Further, the information storage unit stores a processing capability for each ward pharmacist of each item included in the first confirmation item and the second confirmation item, and the schedule creation processing unit includes the processing capability and the processing It is conceivable to create the confirmation schedule for each ward pharmacist based on the time and the scheduled work time. More specifically, the schedule creation processing unit calculates an individual processing time corresponding to each ward pharmacist based on the processing time and the processing capacity, and confirms based on the individual processing time and the scheduled work time. It is conceivable to create a schedule. This makes it possible to create a practical confirmation schedule that takes into account the processing capabilities of the ward pharmacist.

  Further, when there is no first confirmation item determined to be inappropriate by the prescription check, or when a confirmation operation is performed on the first confirmation item determined to be inappropriate by the prescription check, Alternatively, a dispensing control process for starting dispensing of a medicine based on the prescription data using a plurality of dispensing devices is executed, and a confirmation operation for the first confirmation item determined to be inappropriate by the prescription check is performed. If not, it may be possible to provide a dispensing control unit that does not start the dispensing control process. More specifically, the dispensing control unit determines that the second check item determined to satisfy the confirmation condition by the condition check is not appropriate by the prescription check even if the second confirmation item exists. When one confirmation item does not exist or when a confirmation operation is performed on the first confirmation item determined to be inappropriate by the prescription check, the dispensing control process is executed.

  In addition, it is conceivable that the ward drug business support system includes a setting processing unit that can arbitrarily set a determination condition for determining whether each of the first confirmation item and the second confirmation item is necessary according to an operation input. Furthermore, it is conceivable that the setting processing unit can add and delete items included in one or both of the first confirmation item and the second confirmation item. Thereby, the display contents of the first display area and the second display area can be arbitrarily customized, and versatility can be improved.

  Further, the present invention provides a check result of a prescription check for determining whether or not one or more first confirmation items are appropriate for prescription data, and either one of the prescription data and the patient corresponding to the prescription data or An acquisition processing unit for acquiring a check result of a condition check for determining whether or not a confirmation condition of one or a plurality of second confirmation items set in advance separately from the first confirmation item is satisfied; An information storage unit for storing a confirmation item and a processing time necessary for confirmation of each item included in the second confirmation item and a scheduled working time corresponding to each ward pharmacist, and the processing time and the scheduled working time. A ward drug operation support system comprising: a schedule creation processing unit that creates a confirmation schedule for each of the first confirmation item and the second confirmation item for each ward pharmacist based on It may be regarded Te. In this case, the processing capacity for each ward pharmacist of each item included in the first confirmation item and the second confirmation item is stored in the information storage unit, and the schedule creation processing unit includes the processing capacity and the It is conceivable to create the confirmation schedule for each ward pharmacist based on the processing time and the scheduled work time. The schedule creation processing unit calculates an individual processing time corresponding to each ward pharmacist based on the processing time and the processing capacity, and creates the confirmation schedule based on the individual processing time and the scheduled work time. It is possible to do.

  In addition, the present invention is an inspection determination processing unit that determines whether or not an inspection by a ward pharmacist who performs work in a ward where a patient is hospitalized is necessary based on prescription data and predetermined ward inspection conditions. And an issuance control processing unit that issues the prescription data determined to be inspected by the ward pharmacist by the ward pharmacist as an object to be dispensed when an operation is performed by the ward pharmacist. It may be understood as a drug business support system. Thereby, the necessity of the ward side inspection is automatically determined for the prescription data, and the ward pharmacist can automatically distribute and execute the inspection work.

  For example, the ward inspection condition corresponds to the prescription category of the prescription data being predetermined, the hospital ward corresponding to the prescription data being a predetermined ward, and the prescription data. The patient's department is a predetermined department, the patient corresponding to the prescription data is a predetermined patient, and the patient's disease corresponding to the prescription data is a predetermined disease And any one or a plurality of combinations in which a predetermined drug is included in the prescription data is satisfied.

  Further, when the ward drug operation support system further includes an acquisition processing unit that acquires a check result of a prescription check for determining whether or not the prescription data is appropriate, the ward inspection condition is, for example, the check result The prescription data includes a predetermined error, a prescription classification of the prescription data is a predetermined classification, a hospital ward of a patient corresponding to the prescription data is a predetermined ward, the prescription data The corresponding patient's department is a predetermined department, the patient corresponding to the prescription data is a predetermined patient, and the patient's disease corresponding to the prescription data is a predetermined disease And that any one or a combination of a predetermined drug is included in the prescription data is satisfied.

  Further, it is conceivable that the issuance control processing unit can collectively issue a plurality of the prescription data determined to be inspected by the ward pharmacist by the inspection determination processing unit. Thereby, the user can easily issue a plurality of the prescription data.

  The ward drug business support system is held by the hold processing unit and the hold processing unit for holding the prescription data issued by the issuance control processing unit in a state before starting dispensing according to a predetermined hold condition. When the prescription data is displayed as a list, it may be possible to further include a hold display processing unit that displays whether each of the prescription data is subject to inspection by the ward pharmacist. Thereby, the said dispensing pharmacist can select easily only the prescription data which was the object of the said ward side inspection.

  The ward drug business support system may further include a batch dispensing processing unit that collectively starts dispensing processing for a plurality of preselected prescription data among the prescription data held by the holding processing unit. It is done. Thereby, since the dispensing process can be started collectively for arbitrary prescription data, it is possible to increase the work efficiency of the final audit performed by the pharmacist after the dispensing, for example.

  The issuance of the prescription data by the issuance control processing unit may be a process for starting dispensing based on the prescription data in a dispensing device used for dispensing medicine.

  ADVANTAGE OF THE INVENTION According to this invention, the ward pharmacy work support system which can aim at the efficiency improvement of the work of a ward pharmacist is implement | achieved.

FIG. 1 is a block diagram showing a configuration of a ward drug business support system according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of prescription check information and condition check information used in the ward drug business support system according to the embodiment of the present invention. FIG. 3 is a diagram showing an example of business basic information used in the ward drug business support system according to the embodiment of the present invention. FIG. 4 is a diagram showing an example of schedule configuration information used in the ward drug business support system according to the embodiment of the present invention. FIG. 5 is a flowchart showing an example of the procedure of the dispensing start process executed by the ward drug business support system according to the embodiment of the present invention. FIG. 6 is a diagram showing an example of an error list screen displayed on the ward drug business support system according to the embodiment of the present invention. FIG. 7 is a diagram showing an example of an error detail screen displayed on the ward drug business support system according to the embodiment of the present invention. FIG. 8 is a diagram showing an example of a medicine history screen displayed by the ward drug business support system according to the embodiment of the present invention. FIG. 9 is a flowchart showing an example of a procedure of a ward drug operation support process executed by the ward drug operation support system according to the embodiment of the present invention. FIG. 10 is a diagram showing an example of a task management screen displayed by the ward drug task support system according to the embodiment of the present invention. FIG. 11 is a diagram showing an example of a calendar display screen displayed on the ward drug business support system according to the embodiment of the present invention. FIG. 12 is a diagram showing an example of a confirmation item setting screen displayed on the ward drug business support system according to the embodiment of the present invention. FIG. 13 is a diagram showing an example of a condition input screen displayed on the ward drug business support system according to the embodiment of the present invention. FIG. 14 is a block diagram showing a configuration of a ward drug business support system according to another embodiment of the present invention. FIG. 15: is a figure which shows the outline of the processing flow of prescription data in the ward chemical | medical agent business support system which concerns on other embodiment of this invention. FIG. 16: is a flowchart which shows an example of the process sequence of the prescription reception process performed with the ward drug operation | work assistance system which concerns on other embodiment of this invention. FIG. 17: is a flowchart which shows an example of the process sequence of the ward side inspection process performed with the ward drug operation | work assistance system which concerns on other embodiment of this invention. FIG. 18 is a flowchart showing an example of the processing procedure of the dispensing side inspection process executed in the ward drug business support system according to another embodiment of the present invention. FIG. 19 is a flowchart showing an example of a processing procedure of a prescription data issuing process executed by a ward drug business support system according to another embodiment of the present invention. FIG. 20 is a flowchart showing an example of a processing procedure of a closing management process executed by a ward drug business support system according to another embodiment of the present invention. FIG. 21 is a diagram showing an example of an operation screen displayed in a ward drug business support system according to another embodiment of the present invention. FIG. 22 is a diagram showing an example of an operation screen displayed in a ward drug business support system according to another embodiment of the present invention. FIG. 23 is a diagram showing an example of an operation screen displayed in a ward drug business support system according to another embodiment of the present invention. FIG. 24 is a diagram showing an example of an operation screen displayed in the ward drug business support system according to another embodiment of the present invention. FIG. 25 is a diagram showing an example of an operation screen displayed in the ward drug business support system according to another embodiment of the present invention. FIG. 26 is a diagram showing an example of an operation screen displayed in the ward drug business support system according to another embodiment of the present invention. FIG. 27 is a diagram showing an example of an operation screen displayed in a ward drug business support system according to another embodiment of the present invention. FIG. 28 is a diagram showing an example of an operation screen displayed in the ward drug business support system according to another embodiment of the present invention. FIG. 29 is a diagram showing an example of an operation screen displayed in a ward drug business support system according to another embodiment of the present invention. FIG. 30 is a diagram showing an example of an operation screen displayed in the ward drug business support system according to another embodiment of the present invention. FIG. 31 is a diagram showing an example of an operation screen displayed in a ward drug business support system according to another embodiment of the present invention. FIG. 32 is a diagram showing an example of an operation screen displayed in the ward drug business support system according to another embodiment of the present invention.

  Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings for understanding of the present invention. In addition, the following embodiment is an example which actualized this invention, Comprising: The thing of the character which limits the technical scope of this invention is not.

[Ward Drug Business Support System 10]
As shown in FIG. 1, a ward drug business support system 10 according to an embodiment of the present invention includes a server 1, a client terminal 2, a dispensing device 3, and a printer 4. The client terminal 2 is provided in each of a dispensing room 100 where dispensing based on prescription data is performed by a dispensing pharmacist and a ward 200 where guidance or confirmation regarding drug administration is performed by a ward pharmacist. When there are a plurality of the dispensing rooms 100 or the ward 200, the client terminal 2 is provided in each of the dispensing room 100 and the ward 200. Hereinafter, the client terminal 2 provided in the dispensing room 100 and operated by the dispensing pharmacist is referred to as “dispensing room terminal 2A”, and the client terminal 2 provided in the ward 200 and operated by the ward pharmacist is referred to as “ward”. The term “terminal 2B” refers to “client terminal 2” when these are collectively referred to without distinction. The dispensing room terminal 2A is an example of a second client terminal, and the ward terminal 2B is an example of a first client terminal.

  Here, in the server 1, it is conceivable that a business authority for each pharmacist who uses the client terminal 2 is set in advance in a pharmacist master described later in which pharmacist information is registered in advance. Specifically, in the server 1, information such as whether or not the pharmacist has authority as a dispensing pharmacist and whether or not the pharmacist has authority as a ward pharmacist can be set in advance. Conceivable. Note that the operation authority setting operation is performed using the server 1 or the client terminal 2 by, for example, a preset administrator. In the server 1, when the pharmacist who has logged into the client terminal 2 has the authority of a dispensing pharmacist, the client terminal 2 is recognized as the dispensing room terminal 2A. Similarly, in the server 1, when a pharmacist who logs in to the client terminal 2 has the authority of a ward pharmacist, the client terminal 2 is recognized as the ward terminal 2B. Furthermore, in the server 1, when the pharmacist who has logged in to the client terminal 2 has the authority of both the dispensing pharmacist and the ward pharmacist, the client terminal 2 can be selected by the logged-in pharmacist according to any mode selection. It is recognized as either the terminal 2A or the ward terminal 2B. That is, it is conceivable that the server 1 identifies whether the client terminal 2 is the dispensing room terminal 2A or the ward terminal 2B on a pharmacist basis.

  As another embodiment, in the server 1, the client terminal 2 installed in the dispensing room 100 is preset as the dispensing room terminal 2A, and the client terminal 2 installed in the ward 200 is It may be preliminarily set as the ward terminal 2B. That is, it is conceivable that the server 1 identifies whether the client terminal 2 is the dispensing room terminal 2A or the ward terminal 2B in units of the client terminal 2. In this case, in the server 1, each of the client terminals 2 is identified by an IP address, a MAC address, a terminal name, or the like, and is preliminarily set as the dispensing room terminal 2A or the ward terminal 2B. It is done.

  The server 1, the client terminal 2, the dispensing device 3, and the printer 4 are connected via a communication network 5 so that they can communicate wirelessly or by wire. The communication network 5 is a LAN, a WAN, the Internet, an intranet, or the like. The server 1 includes a host system 6 such as an electronic medical record system, an ordering system, or a reception system that inputs prescription data indicating prescription contents and patient data indicating patient information to the server 1. 5 is connected. The prescription data includes, for example, basic information such as the patient's name, sex, age, ward, doctor in charge, pharmacist in charge, and information such as the type, dose, and usage of the medicine prescribed to the patient. The server 1 may be configured to read the prescription data and the patient data from the host system 6. For example, the server 1 monitors whether or not the prescription data is stored in a prescription data storage area in a preset storage device of the host system 6, and the prescription data is stored in the prescription data storage area. If stored, the prescription data is obtained.

[Dispensing equipment 3]
Each of the dispensing devices 3 is used in a medicine dispensing operation in a medical institution such as a hospital or a pharmacy where the ward drug operation support system 10 is used. For example, each of the dispensing devices 3 is a tablet dispenser, a powder dispenser, a liquid dispenser, a PTP sheet dispensing device, a mixed injection device, or the like. For example, the tablet packaging machine has a plurality of medicine cassettes containing a plurality of types of tablets, dispenses tablets from the medicine cassette according to dispensing data input from the server 1, and dispenses them for each dose. A wrapping operation for wrapping with wrapping paper is executed. In accordance with the dispensing data input from the server 1, the powder medicine packaging machine performs a packaging operation for packaging the powdered powder in a dosed paper for each dose. The liquid medicine dispenser has a plurality of medicine bottles containing a plurality of kinds of liquid medicines, and dispenses a required amount of liquid medicine from the medicine bottles according to dispensing data input from the server 1. put out. The PTP sheet dispensing apparatus has a plurality of sheet cassettes in which PTP sheets or heat seals in which tablets are packaged in advance are accommodated, and according to dispensing data input from the server 1, the PTP sheets or Discharge the heat seal. The mixed injection device automatically executes a mixed injection operation for injecting a medicine such as an anticancer drug into an infusion solution according to the dispensing data input from the server 1 using a robot arm.

[Printer 4]
The printer 4 prints information included in print data input from the server 1 and the client terminal 2 via the communication network 5 on a sheet such as paper. For example, the printer 4 is used for printing a prescription or a medicine bag in the ward drug business support system 10.

[Server 1]
The server 1 is a computer including a control unit 11, a storage unit 12, a communication I / F 13, a display device 14, an operation device 15, a drive device 16, and the like. The server 1 is provided inside or outside a medical institution such as a hospital or a pharmacy where the ward drug operation support system 10 is used. The server 1 may be a mobile terminal such as a smartphone or a tablet terminal.

  The control unit 11 includes control devices such as a CPU, a ROM, a RAM, and an EEPROM. The CPU is a processor that executes various arithmetic processes. The ROM is a non-volatile storage unit in which information such as a control program for causing the CPU to execute various processes is stored in advance. The RAM is a volatile storage unit, and the EEPROM is a non-volatile storage unit. The RAM and the EEPROM are used as a temporary storage memory (working area) for various processes executed by the CPU. And the said control part 11 performs various processes according to the various control programs previously stored in the said ROM, the said EEPROM, or the said memory | storage part 12 using the said CPU.

  The storage unit 12 is a non-volatile storage unit such as a hard disk or an SSD that stores various application programs and various data executed by the control unit 11. Specifically, the storage unit 12 includes a program storage unit 121, a master storage unit 122, and an information storage unit 123.

  The program storage unit 121 is a storage area in which a control program for causing the control unit 11 to execute a dispensing start process (see FIG. 5) and a ward drug operation support process (see FIG. 9) described later is stored. The program storage unit 121 also stores application programs such as an operating system (OS) and browser software.

  The master storage unit 122 is a storage area for storing various master information such as a medicine master, a patient master, a pharmacist master, a prescription division master, a clinical department master, and a ward master. For example, the chemical master includes a chemical code (YJ code, etc.), a chemical name, a JAN code, an RSS code, a vial code, a dosage form, a unit, a specific gravity, a chemical type, a composition change, and an excipient for various chemicals. , Information such as notes.

  The patient master includes information such as a patient name, patient ID, sex, age, alcohol consumption, smoking presence, and disease name for each patient. In addition, the patient master includes various types of information confirmed at the time of examination or inquiry such as whether the patient is a pregnant woman or a lactating woman. The pharmacist master includes information such as a pharmacist code of a pharmacist who performs business at the medical institution, a pharmacist name, a ward in charge, and the presence / absence of administrator authority. The pharmacist master stores information such as a pharmacist's business authority (dispensing pharmacist, ward pharmacist).

  The control unit 11 can update various master information stored in the master storage unit as needed based on information acquired from the host system 6. The control unit 11 can also edit the various master information according to user operations using the server 1 and the client terminal 2.

  The information storage unit 123 is a storage area for storing various information such as the prescription data, prescription check information D11, condition check information D12, business basic information D21, and schedule configuration information D22. The prescription data is acquired from the host system 6 by the control unit 11 and stored in the information storage unit 123.

  2A shows an example of the prescription check information D11, FIG. 2B shows the condition check information D12, FIG. 3 shows an example of the business basic information D21, and FIG. It is a figure which shows an example of the said schedule structure information D22.

  As shown in FIG. 2 (A), the prescription check information D11 stores one or a plurality of first confirmation items to be confirmed for prescription data before dispensing. Specifically, the prescription check information D11 shown in FIG. Twenty types of first confirmation items corresponding to “1” to “20” are included. The prescription check information D11 includes a determination condition that is predetermined for each first confirmation item in order to determine whether the content of the first confirmation item is appropriate for the prescription data. The determination condition is predetermined for each medicine. In addition, it can be considered that the determination condition corresponding to each medicine is determined for each medicine by the medicine master instead of the prescription check information D11.

  For example, for the “interaction check” that is the first confirmation item shown in FIG. 2A, information for determining whether there is a problem relating to a combination of medicines in the prescription data is defined. As for the “dosage” as the first confirmation item, the single dose and the daily dose of the medicine in the prescription data are not more than the upper limit of the predetermined single dose and the daily dose of the medicine. Information for determining whether or not is determined. Furthermore, for the “contraindication check” as the first confirmation item, information for determining whether or not the medicine included in the prescription data is a medicine that may be prescribed to the patient based on the patient's disease name or the like Is stipulated. In addition, regarding “pregnant / lactating administration restriction” as the first confirmation item, when the patient corresponding to the prescription data is a pregnant / lactating woman, the prescription data restricts administration to the pregnant / lactating woman. Information for determining whether or not a medicine that has been used is included is defined.

  As shown in FIG. 2 (B), in the condition check information D12, either one or both of the prescription data and the patient corresponding to the prescription data is determined separately from the first confirmation item. A plurality of second confirmation items are stored. Specifically, the condition check information D12 shown in FIG. Four types of second confirmation items corresponding to “1” to “4” are included. Further, the condition check information D12 includes a determination condition predetermined for each second confirmation item in order to determine whether or not a pharmacist should confirm the content of the second confirmation item.

  For example, the “pre-operative withdrawal drug” that is the second confirmation item shown in FIG. 2 (B) is a pre-operative withdrawal medicine that should not be taken before surgery. Information for determining whether or not is determined. For the “additional prescription” as the second confirmation item, information for determining whether or not the prescription data is additionally issued to the patient is defined. Furthermore, with respect to the “change in dosage” as the second confirmation item, in order to determine whether or not there has been a change in the usage and dosage of the drug compared with the content previously prescribed to the patient corresponding to the prescription data Information is defined.

  The first confirmation item is a relatively high importance item such as an item that requires a prescription proposal to a doctor or an item that requires a question inquiry. On the other hand, the second confirmation item is a confirmation item that needs to be confirmed, for example, when the ward pharmacist performs a ward drug operation such as grasping a side effect of a patient and taking a medication instruction.

  As shown in FIG. 3, in the business basic information D21, the first confirmation item, the priority classification (an example of priority) of confirmation of the first confirmation item, and the processing time required for confirmation of the first confirmation item The correspondence with is defined. In the business basic information D21, there is also a correspondence relationship between the second confirmation item, the priority classification (an example of priority) of the confirmation of the second confirmation item, and the processing time required for confirmation of the second confirmation item. It has been established.

  The first confirmation item and the second confirmation item are items that may be confirmed by a ward pharmacist. For example, "Contraindications for combination use", "Caution for combination use", "Dosage", "Allergy", "Combination change" , “Disease name”, “administration interval”, “maternal lactation”, “pre-operative withdrawal drug”, “additional prescription”, “administration dose change”, and “test report”.

  The priority classification is information related to the priority of processing of each of the first confirmation item and the second confirmation item. In this embodiment, “contraindication (high)”, “caution (medium)”, and “information provision” A case where three types of priority classification “low” are used will be described as an example. Note that the description in parentheses in the priority category indicates the priority level. The processing time is information set in advance as a time that is considered necessary for the ward pharmacist to confirm the suitability of the first confirmation item and the second confirmation item. For example, in the business basic information D21, the priority classification is set to “Contraindication (high)” and the processing time is set to “10 minutes” for the “concomitant use in combination” as the first confirmation item. Similarly, for the “precaution for combined use” that is the first confirmation item, the priority classification is set to “attention (medium)”, the processing time is set to “10 minutes”, and the “pre-operative withdrawal drug” that is the second confirmation item. , The priority classification is set to “information provision (low)” and the processing time is set to “15 minutes”.

  As shown in FIG. 4, in the schedule configuration information D22, for each pharmacist, scheduled execution time of a daily ward drug operation, predetermined ability information such as the number of years of work experience, the first confirmation item and the The processing capacity for each second confirmation item is stored in association with each other. Specifically, in the schedule configuration information D22, a pharmacist name, experience, ward, ward work time, and processing capability are set in association with each other. The processing capacity is set in advance as a numerical value for calculating an individual processing time necessary for the pharmacist to perform the confirmation of the first confirmation item or the second confirmation item. High individual processing time. For example, when the processing time is “10 minutes” and the processing capacity is “0.5”, the control unit 11 multiplies the processing time and the processing capacity as the individual processing time. It is possible to calculate “5 minutes”.

  The communication I / F 13 performs data communication between the client terminal 2, the dispensing device 3, and the external device such as the printer 4 via the communication network 5 in a wireless or wired manner according to a predetermined communication protocol. Is a communication interface having a network card or the like for executing.

  The display device 14 is a display unit such as a liquid crystal display or an organic EL display that displays various types of information in accordance with control instructions from the control unit 11. The operation device 15 is an operation unit operated by a user in order to input various kinds of information to the server 1. Specifically, the operation device 15 includes a keyboard and a mouse (pointing device) that accept input operations on various operation screens displayed on the display device 14. The operation device 15 may include a touch panel that accepts touch operations on various operation screens displayed on the display device 14 or a voice input device that accepts input of various information by voice recognition.

  The drive device 16 can read the control program from a computer-readable recording medium 161 on which the control program is recorded. The recording medium 161 is a CD, DVD, BD, or USB memory, and the drive device 16 is a CD drive, DVD drive, BD drive, USB port, or the like. In the server 1, the control program read from the recording medium 161 by using the drive device 16 is stored in the program storage unit 121 of the storage unit 12 by the control unit 11. Installed. Accordingly, in the control unit 11, the CPU can execute the control program stored in the program storage unit 121 while expanding the control program in the RAM.

  The control unit 11 of the server 1 includes an acquisition processing unit 111, a display control unit 112, a schedule creation processing unit 113, and a setting processing unit 114. Specifically, the control unit 11 functions as the acquisition processing unit 111, the display control unit 112, the schedule creation processing unit 113, and the setting processing unit 114 by executing various processes according to the control program. To do.

  The acquisition processing unit 111 performs a prescription check (prescription inspection) for determining whether one or a plurality of the first confirmation items is appropriate for the prescription data based on the prescription check information D11, and the prescription Get check result of check. The prescription check is performed by the control unit 11 when the server 1 acquires the prescription data from the host system 6, when dispensing is started for the prescription data, or when a prescription check is requested by a user. It is executed by the processing unit 111. In addition, about the said prescription check, since what is necessary is just to use various conventionally well-known methods, detailed description is abbreviate | omitted here. Then, the acquisition processing unit 111 records the check result of the prescription check in the storage unit 12 in association with the prescription data. Thereby, the control unit 11 can refer to the check result of the prescription check corresponding to the prescription data stored in the storage unit 12 in a dispensing start process and a ward drug operation support process described later. is there. In addition, if the acquisition processing unit 111 can acquire the check result of the prescription check, the external processing unit 111 can execute the prescription check from an external device such as the host system 6 via the communication network 5. It is also conceivable to obtain the check result of the prescription check by the device.

  In addition, the acquisition processing unit 111 determines whether the pharmacist should check one or a plurality of the second confirmation items for one or both of the prescription data and the patient corresponding to the prescription data. A condition check that is determined based on the check information D12 is executed, and a check result of the condition check is acquired. For example, when the server 1 acquires the prescription data from the host system 6, when dispensing is started for the prescription data, or when a condition check is requested by a user, the acquisition of the control unit 11 is performed. It is executed by the processing unit 111. Note that various known methods may be used for the condition check, and a detailed description thereof will be omitted here. The acquisition processing unit 111 records the check result of the condition check in the storage unit 12 in association with the prescription data. Thereby, the control unit 11 can refer to the check result of the condition check corresponding to the prescription data stored in the storage unit 12 in a dispensing start process and a ward drug operation support process described later. is there. If the acquisition check unit 111 can acquire the check result of the condition check, the external processing unit 111 can execute the condition check from an external device such as the host system 6 via the communication network 5. It is also conceivable to obtain a check result of the condition check by the apparatus.

  The display control unit 112 causes the client terminal 2 or the like to display a later-described work management screen P1 (see FIG. 10) that is referred to by the ward pharmacist when performing the ward drug work. Specifically, the display control unit 112 displays the necessity of confirmation of one or a plurality of the first confirmation items based on the check result acquired by the acquisition processing unit 111 on the job management screen P1. One display area and a second display area for displaying the necessity of confirmation of one or a plurality of the second confirmation items confirmed by the ward pharmacist are displayed for each patient. In particular, the display control unit 112 divides each display column of the first display area and the second display area, and displays a first divided area for displaying the priority of confirmation and a second divided area for displaying the presence or absence of confirmation. Is displayed. The business management screen P1 will be described in detail later with reference to FIG.

  The schedule creation processing unit 113 realizes a later-described schedule creation function for creating a confirmation schedule for each of the first confirmation item and the second confirmation item. In the schedule creation process, the first confirmation item and the second confirmation in the scheduled work time based on the processing time included in the business basic information D21 and the scheduled work time included in the schedule configuration information D22. A confirmation schedule is created for each item.

  The setting processing unit 114 can arbitrarily set a determination condition for determining whether the first confirmation item and the second confirmation item are necessary according to an operation input. The setting processing unit 114 can add and delete the first confirmation item and the second confirmation item.

[Client terminal 2]
On the other hand, the client terminal 2 is a computer including a control unit 21, a storage unit 22, a communication I / F 23, a display device 24, an operation device 25, a drive device 26, and the like. Among the client terminals 2, the dispensing room terminal 2A is an operation terminal provided in a dispensing room where dispensing is performed and used by a dispensing pharmacist, and the ward terminal 2B is provided in a ward where a patient is hospitalized, and a ward An operation terminal used by a pharmacist. The client terminal 2 may be a mobile terminal such as a smartphone or a tablet terminal, and may be carried between the dispensing room 100 or the ward 200 by a user such as a pharmacist.

  The control unit 21 includes control devices such as a CPU, a ROM, a RAM, and an EEPROM. The CPU is a processor that executes various arithmetic processes. The ROM is a non-volatile storage unit in which information such as a control program for causing the CPU to execute various processes is stored in advance. The RAM is a volatile storage unit, and the EEPROM is a non-volatile storage unit. The RAM and the EEPROM are used as a temporary storage memory (working area) for various processes executed by the CPU. And the said control part 21 performs various processes according to the various control programs previously stored in the said ROM, the said EEPROM, or the said memory | storage part 22 using the said CPU.

  The storage unit 22 is a non-volatile storage unit such as a hard disk or an SSD in which various application programs executed by the control unit 21 and various data are stored. Specifically, the storage unit 22 includes a program storage unit 221 in which application programs such as an operating system (OS) and browser software are stored. The browser software displays the various operation screens on the display device 24 by accessing the server 1 via the communication network 5 and performs an input operation on the operation screen using the operation device 25. Application software for transmission to the server 1. Specifically, when address information such as a URL (Universal Resource Locator) corresponding to the server 1 is input at a predetermined position on the operation screen displayed by the browser software, the control unit 21 receives the address information. The server 1 is accessed based on the above.

  The communication I / F 23 performs data communication between the server 1, the dispensing device 3, and the external device such as the printer 4 via the communication network 5 in a wireless or wired manner according to a predetermined communication protocol. A communication interface having a network card or the like to be executed.

  The display device 24 is a display unit such as a liquid crystal display or an organic EL display that displays various types of information in accordance with control instructions from the control unit 21. The operation device 25 is an operation unit operated by a user in order to input various information to the client terminal 2. Specifically, the operation device 25 includes a keyboard and a mouse (pointing device) that accept input operations on various operation screens displayed on the display device 24. The operation device 25 may include a touch panel that accepts touch operations on various operation screens displayed on the display device 24, or a voice input device that accepts input of various information by voice recognition.

  The drive device 26 can read the OS or the browser software from a computer-readable recording medium 261 on which the OS or the browser software is recorded. The recording medium 261 is a CD, DVD, BD, or USB memory, and the drive device 16 is a CD drive, DVD drive, BD drive, USB port, or the like. In the client terminal 2, the OS or the browser software read from the recording medium 261 using the drive device 26 is stored in the program storage unit 221 of the storage unit 22 by the control unit 21. Installed on server 1. As a result, in the control unit 21, the CPU can execute the control program stored in the program storage unit 221 while expanding the control program in the RAM.

  In the ward drug operation support system 10, display, recording, printing, and the like of various information related to the operation of the dispensing pharmacist and the ward drug operation can be executed in accordance with the operation of the client terminal 2 by the user. Specifically, in the present embodiment, a server client system is configured by the server 1 and the client terminal 2, and the server 1 performs the operation of the dispensing pharmacist according to the user operation of the client terminal 2 and the ward drug. A case where display, recording, printing, and the like of various types of information related to business are executed will be described. Therefore, “display”, “operation”, “selection”, “input” and the like described below are performed using the display device 24 and the operation device 25 of the client terminal 2.

  On the other hand, it is also possible for the server 1 to execute various displays and printing related to the dispensing pharmacist's work and the ward medicine work using the display device 14 and the operation device 15, and the server 1 alone is the present invention. It may be considered as a ward drug business support system related to the above. Further, the client terminal 2 may be regarded as a medication instruction system according to the present invention. That is, a part or all of the control program is installed in the client terminal 2, and the control unit 21 of the client terminal 2 appropriately acquires necessary information from the server 1, and operates as a dispensing pharmacist. It is also conceivable to execute various displays and printing related to the ward drug operation.

[Dispensing start processing]
Next, the dispensing start process executed by the control unit 11 of the server 1 will be described with reference to FIG. The dispensing start process is executed in units of the prescription data by the control unit 11 when the prescription check is completed or when a dispensing start request is made by a dispensing pharmacist, for example. The dispensing start request by the dispensing pharmacist is sent from the control unit 21 of the dispensing room terminal 2A to the control unit 11 of the server 1 in accordance with, for example, an operation for selecting and issuing the prescription data to the dispensing room terminal 2A. Done.

<Step S11>
In step S11, the control unit 11 determines whether the check result of the prescription check for the prescription data to be dispensed is appropriate. And when the said control part 11 judges that the said check result is appropriate (S11: Yes side), it transfers a process to step S111, and when it judges that an error exists in the check result of the said prescription check (S11) : No side), the process proceeds to step S12. The step S11 is a process for determining whether or not there is an error in the check result of the prescription check, and it is not determined whether or not there is a confirmation item in the check result of the condition check. Therefore, in the dispensing start process, even if there is a required confirmation item in the check result of the condition check, if there is no error in the check result of the prescription check, the process proceeds to step S111. Dispensing control processing is executed. This is because the second confirmation item for which the necessity of confirmation is determined in the condition check is an item that the ward pharmacist confirms about the patient's condition or an item that is explained to the patient. This is because there is little impact on the dispensing business. On the other hand, as another embodiment, in step S11, the control unit 11 determines whether the check result of the prescription check is appropriate, and there is a confirmation item in the check result of the condition check. It is also possible to determine whether or not. In this case, when there is an error in the check result of the prescription check, or when there is a confirmation required item in the check result of the condition check, the control unit 11 shifts the process to step S12.

<Step S111>
In step S111, the control unit 11 executes a dispensing control process for starting dispensing of a medicine based on the prescription data. For example, the control unit 11 generates dispensing data corresponding to each of the dispensing devices 3 based on the prescription data, and stores it in a shared data folder secured in the storage area of the storage unit 12. Thus, each of the dispensing devices 3 acquires the dispensing data from the shared data folder, and executes the dispensing of the medicine based on the dispensing data. It is also conceivable that the control unit 11 transmits the dispensing data to each of the dispensing devices 3. In addition, the control unit 11 may print picking information necessary for a pharmacist to pick a medicine based on the prescription data, or transmit the picking information to a picking assisting device.

<Step S12>
In step S12, the control unit 11 determines whether or not the check result error has already been confirmed. Here, the error of the check result is confirmed by operation of the dispensing room terminal 2A by the dispensing pharmacist or by operation of the ward terminal 2B by the ward pharmacist described in the ward drug work support process described later. The confirmation operation is performed, for example, on an error detail screen P22 (see FIG. 7) described later. If it is determined that the error of the check result has been confirmed (S12: Yes side), the process proceeds to Step S111. If it is determined that the error has not been confirmed (S12: No side), the process is performed. Goes to step S13.

  In addition, even when the control unit 11 has confirmed the error of the check result, the dispensing room terminal 2A displays that the error has been confirmed, and the dispensing pharmacist performs further confirmation operation. If this is done, it is also conceivable to move the processing to step S111. Thereby, the dispensing pharmacist can confirm that the check result has been confirmed by the ward pharmacist or another dispensing pharmacist.

<Step S13>
In step S13, the control unit 11 performs a predetermined error notification process. For example, in the error notification process, a warning that an error exists in the prescription data is displayed on the display device 24 or the like of the dispensing room terminal 2A, or that there is an error in the prescription data. To be notified.

  FIG. 6 is a diagram showing an example of the error list screen P21 displayed by the error notification process. As shown in FIG. 6, in the error list screen P21, a list of the prescription data in which an error has occurred in the check result of the prescription check among the prescription data dispensed in the dispensing chamber 100 is displayed in the display area A211. Is done. When the error list screen P21 is already displayed, the display is updated so that, for example, the prescription data in which an error has occurred in the check result is added to the display area A211.

  In the error list screen P21, an operation key K211 for displaying an error detail screen P22 for displaying details of the error contents of the prescription data, and a medicine for displaying a drug history of the patient corresponding to the prescription data are displayed. An operation key K212 for displaying the history screen P23 is displayed corresponding to each prescription data. Then, the control unit 11 displays the error detail screen P22 according to the operation of the operation key K211 and displays the medicine history screen P23 according to the operation of the operation key K212.

  FIG. 7 is a diagram showing an example of the error detail screen P22. As shown in FIG. 7, the error detail screen P22 displays a display area A21 in which the content of the error item of the first confirmation item whose check result of the prescription check is an error is displayed. ing. Furthermore, in the error detail screen P22, when the pharmacist has already confirmed the comment display area A22 in which comments inputted by the doctor are displayed and the first confirmation item has already been confirmed, the name and entry date of the pharmacist , And a comment display area A23 in which comments input by the pharmacist are displayed.

  As described above, in the ward drug operation support system 10, when the pharmacist confirms that there is no problem with the contents of the error item of the first confirmation item, the reason or background is entered as a comment in the comment display area A23. Is possible. Therefore, for example, a comment inputted when the ward pharmacist performs the confirmation operation on the error item can be referred to by the dispensing pharmacist on the error detail screen P22. In addition, it becomes possible for the ward pharmacist to refer to the error detail screen P22 for the comment input when the dispensing pharmacist performs the confirmation operation for the error item. That is, the dispensing pharmacist and the ward drug can share information on the confirmation of the error item. Further, in the ward drug operation support system 10, the control unit 11 receives information on the confirmation required items when a predetermined operation is performed on the error list screen P21 or the error detail screen P22 by a dispensing pharmacist. It can be displayed. Specifically, the control unit 11 displays information such as the presence / absence of the confirmation required item corresponding to the prescription data and whether or not the confirmation required item has been confirmed according to the predetermined operation. It is possible. Thereby, for example, the dispensing pharmacist can determine whether or not to approve the error item with reference to the determination of the ward pharmacist familiar with the patient's condition.

  In addition, in the display area A21, a confirmation key K21 for inputting that the content of the error item has been confirmed, and a result of making a question inquiry to the doctor regarding the error item are scheduled to be input. A suspicion schedule key K22 for recording is displayed. In the error detail screen P22, “approval” is displayed on the confirmation key K21. The confirmation key K21 is an operation key for inputting confirmation.

  Further, in the display area A21, a question inquiry key K23 for inputting a result of a question inquiry to the doctor regarding the error item, and a drug for displaying a patient's drug history corresponding to the prescription data A history key K24 is displayed. The error detail screen P22 displays an operation key 25 for changing the display screen to the error list screen P21. The operation key 25 may be displayed only when the pharmacist operating the client terminal 2 is a dispensing pharmacist, that is, when the client terminal 2 is the dispensing room terminal 2A. Further, in the display area A21, when the pharmacist operating the client terminal 2 is a ward pharmacist, the contents of both the error item and the confirmation required item are displayed, and the client terminal 2 is operated. If the current pharmacist is a dispensing pharmacist, only the contents of the error item are displayed. As another embodiment, both the error item and the confirmation required item are displayed on the error detail screen P22 regardless of whether the pharmacist operating the client terminal 2 is a ward pharmacist or a dispensing pharmacist. It may be displayed. Furthermore, in the initial setting process of the ward drug operation support system 10 and the like, the control unit 11 displays only the error item on the error detail screen P22, and a mode for displaying the error item and the confirmation item to be confirmed. May be arbitrarily selected in accordance with a user operation.

  When the confirmation key K21 is operated, the control unit 11 confirms that the error item has been confirmed, the identification information (name or ID, etc.) of the pharmacist who has confirmed the error item, and the confirmation is performed. Confirmation history information such as the date and time received is recorded in the information storage unit 123 in association with the check result. Further, after the operation of the confirmation key K21, the control unit 11 displays that confirmation has been performed instead of the confirmation key K21 corresponding to the error item on the error detail screen P22. Thereby, the pharmacist can grasp | ascertain whether it has confirmed about the said error item by seeing the said error detail screen P22.

  In addition, when the question plan key K22 is operated, the control unit 11 displays the question plan information indicating that the plan is to input the result of the question inquiry to the doctor regarding the error item. Is recorded in the information storage unit 123 in association with the information. In other words, at this time, a question inquiry is performed, but the result of the question inquiry is not input.

  In addition, when the question inquiry key K23 is operated, the control unit 11 displays a question inquiry input screen for inputting question inquiry information regarding a result of a question inquiry to the doctor regarding the error item. The control unit 11 receives input of the question inquiry information including a comment from a doctor in accordance with the display of the question inquiry input screen, and records the input question inquiry information in the information storage unit 123. Moreover, the said control part 11 displays the comment from a doctor on the said comment display area A22 of the said error detail screen P22 based on the said question inquiry information.

  Moreover, the said control part 11 will display the said medical history screen P23 which displays the medical history of the patient corresponding to the said prescription data on the said display device 24, if the said medical history key K24 is operated.

  FIG. 8 shows an example of the medicine history screen P23. As shown in FIG. 8, the medicine history screen P23 displays the medicine history of the patient corresponding to the prescription data. The medicine history screen P23 displays an operation key K231 for changing the display screen to the error list screen P21 and an operation key K232 for changing the display screen to the error details screen P22. Then, the control unit 11 displays the error list screen P21 according to the operation of the operation key K231, and displays the error details screen P22 according to the operation of the operation key K232. In addition, the control unit 11 specifies the drug name corresponding to the error item and the confirmation required item included in the prescription data on the medicine history screen P23 corresponding to the priority classification of the error item and the confirmation required item. It is also possible to display the error details screen P22 corresponding to the selected item when the error item or the confirmation required item is selected by displaying in color.

  Further, when the operation key K25 shown in FIG. 7 is operated, the control unit 11 displays the error list screen P21 on the display device 24. The control unit 11 also displays the display screen of the display device 24 when an operation for closing the error detail screen P22 is performed or when an operation for returning the screen transition is performed. Transition to the error list screen P21.

  Thus, in the ward drug business support system 10, the dispensing pharmacist can arbitrarily switch the error list screen P21, the error detail screen P22, and the drug history screen P23 to be displayed on the display device 24. Is possible. Therefore, the dispensing pharmacist refers to the error list screen P21, the error details screen P22, and the medicine history screen P23, and approves the error of the check result of the prescription data and executes the dispensing work on the prescription data. It is possible to determine whether or not.

  The control unit 11 displays the medicine history of the patient corresponding to the prescription data selected by the selection operation when the prescription data selection operation is performed on the error list screen P21. Displaying the screen P23 is also conceivable as another embodiment. In this case, the control unit 11 may close the medicine history screen P23 and display the error detail screen P22 when a predetermined operation for proceeding with the process is performed on the medicine history screen P23. That is, it is conceivable that the control unit 11 interposes the display of the drug history screen P23 when displaying the error detail screen P22 from the error list screen P21. Thereby, the dispensing pharmacist is prompted to determine whether or not there is a confirmation operation for the first confirmation item after referring to the medicine history of the patient on the medicine history screen P23. In this case, operation keys for arbitrarily switching each of the error list screen P21, the error details screen P22, and the medicine history screen P23 may be displayed, but may be omitted.

<Step S14>
As shown in FIG. 5, in step S <b> 14, the control unit 11 determines whether a confirmation operation has been performed on the error item. Specifically, when the confirmation key K21 has already been operated on the error detail screen P22, it is determined that the confirmation operation has been performed. If it is determined that the confirmation operation has already been performed (S14: Yes side), the process proceeds to step S111, and if it is determined that the confirmation operation has not yet been performed (S14: No side), the dispensing start process ends.

[Ward pharmacy work support processing]
Next, a ward drug business support process executed by the control unit 11 of the server 1 will be described with reference to FIG. By the way, the present invention may be understood as an invention of a ward drug operation support method for supporting a medication instruction operation of a ward pharmacist by executing the ward drug operation support process.

<Step S21>
First, the said control part 11 transfers a process to step S22, when predetermined work start operation is performed using the said ward terminal 2B by the ward pharmacist (Yes side of S21). Note that until the operation start operation is performed (No side in S21), the process waits in step S21.

  The business start operation is a login operation for inputting identification information such as a pharmacist's name or ID and a password preset for each pharmacist. The operation start operation may be performed by a card reader (not shown) connected to the ward drug operation support system 10 such as a magnetic card or an IC card possessed by each pharmacist.

  Specifically, in the server 1, since the authority information of each pharmacist is stored in the pharmacist master as described above, the pharmacist who performed the operation start operation by the control unit 11 is a dispensing pharmacist and a ward pharmacist. It is conceivable to determine which one is based on the pharmacist master. The control unit 11 may execute different processes depending on whether the pharmacist who performed the operation start operation is a ward pharmacist or a dispensing pharmacist. Specifically, when the pharmacist who performed the operation start operation is a ward pharmacist, the control unit 11 shifts the process to step S22, and when the pharmacist is a dispensing pharmacist, the error list screen P21 (see FIG. 5). ) May be displayed. That is, the ward pharmacist support process may be a process dedicated to the ward pharmacist for supporting the ward pharmacist's work. As another embodiment, it is conceivable that the ward drug operation support process is similarly executed when the pharmacist who performed the operation start operation is a dispensing pharmacist.

  Further, before the step S21, the control unit 11 causes the client terminal 2 to display a mode selection screen that can arbitrarily select the first mode corresponding to the dispensing pharmacist and the second mode corresponding to the ward pharmacist. When the second mode is selected according to the mode selection operation on the mode selection screen, it may be determined that the operation start operation by the ward pharmacist has been performed. When the first mode is selected, it is conceivable that the control unit 11 determines that a business start operation has been performed by the dispensing pharmacist and displays the error list screen P21 and the like.

<Step S22>
In step S22, the control unit 11 causes the display device 24 to display a task management screen P1 corresponding to the pharmacist who performed the task start operation in step S21. When the pharmacist who performed the operation start operation is a ward pharmacist, necessary information is extracted and displayed on the operation management screen P1 among the information regarding the patient who is admitted to the ward in charge of the ward pharmacist. Specifically, the control unit 11 includes an error item in the first confirmation item as a check result of the prescription check acquired by the acquisition processing unit 111 for a patient admitted to the ward of the ward pharmacist. And when the second confirmation item includes a confirmation required item as a check result of the condition check acquired by the acquisition processing unit 111, information corresponding to the patient is extracted and displayed on the task management screen P1. Display.

  FIG. 10 shows an example of the business management screen P1. As shown in FIG. 10, the task management screen P1 includes a condition display area A11 and a task display area A12. Note that a schedule display key K11 and a master setting key K12 are also displayed on the job management screen P1.

  In the condition display area A11, it is possible to input a narrowing condition for narrowing down patient information to be displayed on the task management screen P1. Specifically, in the condition display area A11, information displayed on the work management screen P1 is set with narrowing conditions such as a ward, a department, a pharmacist, contraindications, cautions, information provision, and unapproved / unconfirmed only. Is possible. In the business management screen P1, “approval” is displayed for confirmation of the first confirmation item, and “confirmation” is displayed for confirmation of the second confirmation item. This indicates that all have been confirmed. The control unit 11 extracts information to be displayed on the job management screen P1 from the information storage unit according to the narrowing conditions.

  In the business display area A12, a basic display area A121, a first display area A122, and a second display area A123 are displayed. In the basic display area A121, basic information such as the patient ID, name, ward, ward, ward, department, doctor, pharmacist, hospitalization date, and the like is displayed. In the first display area A122, the determination result of one or more first confirmation items set in advance among the first confirmation items is displayed. In the second display area A123, whether or not to confirm one or more second confirmation items set in advance among the second confirmation items is displayed.

  The control unit 11 displays the item name of the first confirmation item displayed in the first display area A122 in a first division color such as orange, and displays the item name in the second display area A123. The item name of the second confirmation item is displayed in a second division color such as light blue. As described above, since the item names of the first confirmation item and the second confirmation item are displayed in different display colors on the business management screen P1, the pharmacist can display the first confirmation item and the second confirmation item. It is possible to grasp at a glance which one corresponds.

  Further, the control unit 11 divides each display field A13 of the first display area A122 into upper and lower parts, a first divided area A131 that displays a priority division of confirmation, and a second divided area A132 that displays whether or not confirmation is made. Is displayed. Similarly, the control unit 11 divides each display field A14 of the second display area A123 into upper and lower parts, a first divided area A141 that displays a priority section for confirmation, and a second divided area A142 that displays the presence or absence of confirmation. Is displayed.

  Specifically, when the error item is not included in the check result of the prescription check, the control unit 11 displays a blank in the first divided area A131 of the display field A13 corresponding to each of the first confirmation items. Let Thereby, the ward pharmacist can grasp that the confirmation is unnecessary for each of the first confirmation items by looking at the first divided area A131.

  On the other hand, when the error item is included in the check result of the prescription check, the control unit 11 includes the first divided area A131 and the first divided area A131 of the display field A13 corresponding to the first confirmation item that is the error item. The priority division of confirmation and the presence / absence of confirmation are displayed in the two-divided area A132. That is, in the display column A13, only the first divided region A131 and the second divided region A132 in the display column corresponding to the error item determined to be inappropriate by the prescription check are the priority classification and confirmation of confirmation. The presence / absence is displayed. Note that information regarding the presence / absence of confirmation displayed in the second divided area A132 is stored in the information storage unit 123 and is appropriately updated by the control unit 11.

  For example, as shown in FIG. 10, when the “dose” of the first confirmation item is the error item and the error content is “contraindication (high)”, as shown in FIG. In the first divided area A131 of the display column A13 of “amount”, a mark “×” indicating “contraindication (high)” which is a priority classification of confirmation is red corresponding to “contraindication (high)” in advance. Are displayed together with the background of the first specific color M1. In addition, when the “interaction” of the first confirmation items is the error item and the error content is “caution (medium)”, the control unit 11 displays the display field A13 of the “interaction”. In the first divided area A131, a “△” mark indicating “Caution (Medium)”, which is a priority classification of confirmation, is displayed in the second specific color M2 such as yellow, which is previously associated with “Caution (Medium)”. Display with background. That is, the control unit 11 displays the first divided area A131 of the first confirmation item in a display mode set in advance according to the priority classification (priority) of confirmation of the first confirmation item. The display mode includes, for example, the character color, background color, design, and blinking of the display of the first divided area A131.

  Further, when the error item has not been confirmed, the control unit 11 displays a blank for indicating that in the second divided area A132, and the error item has been confirmed. Displays a message of “approved” to that effect in the second divided area A132, and a specific color such as white associated with the background color of the first divided area A131 in advance. Change to In addition, the display mode which shows the priority classification of confirmation of the said 1st confirmation item, and the presence or absence of confirmation is not restricted to these. That is, the control unit 11 displays the first divided area A131 of the first confirmation item that has been confirmed in a display mode that is set in advance corresponding to the confirmation of the first confirmation item. The display mode includes, for example, the character color, background color, design, and blinking of the display of the first divided area A131.

  Further, the control unit 11 displays a blank in the first divided area A141 of the display field A14 corresponding to each of the second confirmation items when the check result is not included in the check result of the condition check. Let Thereby, the ward pharmacist can grasp that the confirmation is unnecessary for each of the second confirmation items by looking at the second divided area A141.

  On the other hand, when the required check item is included in the check result of the condition check, the control unit 11 includes the first divided area of the display field A14 corresponding to the second check item that is the required check item. The priority division of confirmation and the presence / absence of confirmation are displayed in A141 and the second divided area A142. That is, in the display column A14, priority is given only to the first divided region A141 and the second divided region A142 in the display column corresponding to the confirmation required item determined to be confirmed by the condition check. The classification and presence / absence of confirmation are displayed. Note that the information regarding the presence / absence of confirmation displayed in the second divided area A 142 is stored in the information storage unit 123 and is appropriately updated by the control unit 11.

  For example, as shown in FIG. 10, the control unit 11 determines that “pre-operative withdrawal drug” is the required confirmation item among the second confirmation items, and the confirmation content is “information provision (low)”. In the first divided area A141 of the display column A14 of the “discontinued drug before surgery”, a mark “◯” indicating “information provision (low)” which is a priority classification of confirmation is indicated by “information provision (low)”. "And the background of the third specific color M3 such as blue, which is associated in advance. That is, the control unit 11 displays the first divided area A141 of the second confirmation item that has been confirmed in advance according to the priority classification (priority) of the confirmation of the second confirmation item. To display. The display mode includes, for example, the character color, the background color, the design, and the blinking of the display of the first divided area A141.

  In addition, when the confirmation required item is not confirmed, the control unit 11 displays a blank for indicating that in the second divided area A142, and the confirmation required item is confirmed. In such a case, a “confirmed” message for indicating this is displayed on the second divided area A 142, and the background color of the first divided area A 141 is confirmed in advance, for example, white Change to a specific color. In addition, the aspect which shows the priority classification of confirmation of the said 1st confirmation item, and the presence or absence of confirmation is not restricted to these. That is, the control unit 11 displays the first divided area A141 of the second confirmation item that has been confirmed in a display mode set in advance corresponding to the confirmation of the second confirmation item. The display mode includes, for example, the character color, the background color, the design, and the blinking of the display of the first divided area A141.

  In the work management screen P1, information on the patient in which the first confirmation item and the second confirmation item that need to be confirmed exist is preferentially given in the order of priorities of the past, the current day, and the future, that is, the timing is early. Displayed at the top. For information having the same time, information on a patient having a high priority classification for the confirmation of the first confirmation item and the second confirmation item is displayed preferentially. Thereby, the pharmacist can grasp | ascertain easily the information of the patient which should be confirmed preferentially.

  Further, when various item names are selected on the task management screen P1, the control unit 11 can rearrange and display the item names. The item name is selected by, for example, a mouse click operation of the operation device 25 or a touch operation of the touch panel of the operation device 25. By the way, when all items cannot be displayed simultaneously on the task management screen P1, the control unit 11 can display all items sequentially by scrolling the display in the horizontal direction according to a predetermined scroll operation in the horizontal direction. Is possible. The control unit 11 can arbitrarily set the type and display order of items to be displayed on the task management screen P1 as the patient information in accordance with a user operation by an initial setting process that can be executed in advance. It is. Further, the control unit 11 has an item setting function for setting the types of the first confirmation item and the second confirmation item displayed on the business management screen P1 according to a user operation. Will be described later.

  Further, in the business management screen P1, a cursor indicating the operation position exists in the display column A13 or the display column A14 in which the priority division for confirmation is displayed in the first divided region A131 or the first divided region A141. For example, when a mouse-over operation is performed, the control unit 11 pops up detailed information regarding the confirmation status of the first confirmation item or the second confirmation item corresponding to the display field A13 or the display field A14. Display. For example, for the first confirmation item or the second confirmation item, the control unit 11 may include specific error contents of the error item, specific confirmation contents of the confirmation required item, confirmation date and time, confirmation person, etc. Detailed confirmation information is recorded in the information storage unit 123, and the detailed confirmation information corresponding to the first confirmation item or the second confirmation item may be read from the information storage unit 123 and displayed in the pop-up. .

  Further, the control unit 11 changes the background color of the first divided area A131 to a specific color such as white when confirmation is made for the first confirmation item that needs to be confirmed. Display is continued for the priority classification (A, Δ, X, etc.) of the confirmation in A131. Thereby, the pharmacist can easily grasp that the confirmation has already been performed, although the error item is originally the error item among the first confirmation items. Similarly, the control unit 11 changes the background color of the first divided area A141 to a specific color such as white when confirmation is made for the second confirmation item that needs to be confirmed. The display of the confirmation priority categories (A, Δ, X, etc.) in A141 is continued. As a result, the pharmacist can easily grasp that the confirmation has already been performed, although the original confirmation is an item among the second confirmation items.

  On the other hand, the control unit 11 displays the display mode of the first divided area A131 of each of the first confirmation items with a pharmacist who has performed the confirmation operation of the first confirmation item and other pharmacists who have not performed the confirmation operation. It is possible to change between. Similarly, the control unit 11 displays the display mode of the first divided area A141 of each of the second confirmation items with a pharmacist who has performed the confirmation operation of the second confirmation item and other pharmacists who have not performed the confirmation operation. It is possible to change between. Specifically, the control unit 11 displays the first confirmation item that has been confirmed by the pharmacist (logged-in pharmacist) who performed the task start operation when the task management screen P1 is displayed. The background color of the first division area A131 and the first division area A141 of the second confirmation item is changed to a specific color such as white, and the first division of the first confirmation item for which the confirmation operation has been performed by another pharmacist It is conceivable that the background colors of the area A131 and the first divided area A141 of the second confirmation item are not changed. Therefore, the background color of the first divided area A131 of the first confirmation item and the first divided area A141 of the second confirmation item confirmed by another pharmacist is the first color corresponding to the priority classification of the confirmation. One of the specific color M1, the second specific color M2, and the third specific color M3. Thereby, the pharmacist can grasp at a glance the item for which the pharmacist has performed the confirmation operation and the item for which the other pharmacist has performed the confirmation operation for each of the first confirmation item and the second confirmation item.

  The operation management screen P1 displays operation keys K151 for displaying the medicine history screen P23 on which the medicine history of the patient corresponding to the prescription data is displayed for each patient. And the said control part 11 displays the said medicine history screen P23 according to operation of the said operation key K151. Thereby, in the ward drug work support system 10, the ward pharmacist can arbitrarily switch and display the work management screen P1, the error detail screen P22, and the medicine history screen P23. Accordingly, whether the ward pharmacist approves the error of the check result of the prescription data with reference to the error list screen P21, the error details screen P22, and the drug history screen P23, and executes the dispensing operation regarding the prescription data? It is possible to determine whether or not.

<Step S23>
Next, in step S23, the control unit 11 performs the selection operation of the display column A13 or the display column A14 corresponding to the error item or the confirmation required item among the first confirmation item or the second confirmation item. If it is performed (Yes side of S23), the process proceeds to step S24. If the selection operation is not performed (No side in S23), the process proceeds to step S28.

  As another embodiment, when the control unit 11 performs the selection operation (Yes in S23), the patient corresponding to the display column A13 or the display column A14 selected by the selection operation It is also conceivable to display the medicine history screen P23 displaying the medicine history of In this case, the control unit 11 may close the medicine history screen P23 and display the error detail screen P22 when a predetermined operation for proceeding with the process is performed on the medicine history screen P23. That is, it is conceivable that the control unit 11 interposes the display of the medicine history screen P23 when displaying the error detail screen P22 from the business management screen P1. This prompts the ward pharmacist to determine whether or not there is a confirmation operation for each of the first confirmation item and the second confirmation item after referring to the patient's medication history on the medication history screen P23. In this case, operation keys for arbitrarily switching each of the task management screen P1, the error detail screen P22, and the medicine history screen P23 may be displayed, but may be omitted.

<Step S24>
In step S24, the control unit 11 displays the error detail screen P22 (see FIG. 7) that displays details of the first confirmation item or the second confirmation item on which the selection operation in step S23 has been performed, in the client terminal. 2 is displayed. That is, when the pharmacist operating the client terminal 2 is a ward pharmacist, the control unit 11 displays not only the first confirmation item but also the second confirmation item on the error detail screen P22. It is possible. The error detail screen P22 displays details of the error item or the confirmation required item in which the selection operation is performed among the first confirmation item or the second confirmation item, and the error item or The presence / absence of confirmation of the confirmation required item and the comment of the confirmer are displayed. Therefore, for example, the ward pharmacist determines whether or not to confirm that there is no problem with the error item or the confirmation required item based on the patient's condition, or when the pharmacist has already confirmed it. It is possible to determine the propriety of the prescription content by referring to the comments at the time of confirmation.

  In addition to the error item or the required confirmation item for which the selection operation has been performed, the error item or the required confirmation item may exist, but in step S24, the selection is performed by the selection operation. It is also conceivable to display only the error item or the confirmation required item. As another embodiment, the error item or the confirmation required item selected by the selection operation may be displayed at the top, and the other error item or the confirmation required item may be displayed at the same time. Further, the control unit 11 displays only the error item or the confirmation required item corresponding to the selection operation when the selection operation is performed in the initial setting process of the ward drug operation support system 10 or the like. And a mode for displaying all the error items or the confirmation required items may be arbitrarily selected according to a user operation.

<Step S25>
In step S25, the control unit 11 determines whether or not there is a confirmation operation on the error detail screen P22. For example, the ward pharmacist determines the suitability of the prescription content for the patient based on individual circumstances such as the patient's condition obtained by contacting the patient, and if there is no problem with the prescription content, performs the above confirmation operation, If there is a problem, the confirmation operation is not performed. Here, when the control unit 11 determines that the confirmation operation of the first confirmation item or the second confirmation item is performed by the operation of the confirmation key K21 (Yes side of S25), the process proceeds to step S26. . On the other hand, when the confirmation operation is not performed (No side of S25), for example, when a predetermined operation for closing the error detail screen P22 is performed, the control unit 11 displays the job management screen P1. In order to update to the latest state, the process proceeds to step S27. When the confirmation operation is not performed (No side in S25), the process may be returned to step S23.

<Step S26>
In step S <b> 26, the control unit 11 performs an information update process for storing in the information storage unit 123 information such as confirmation date, confirmation person, etc. that the first confirmation item or the second confirmation item has been confirmed. Run.

<Step S27>
Next, in step S27, the control unit 11 redisplays the task management screen P1. Thereby, when the confirmation operation is not performed on the error detail screen P22 (No side of S25), the confirmation state of the first confirmation item or the second confirmation item is not updated and the error detail screen is updated. P22 is closed and the business management screen P1 is displayed again. On the other hand, when the confirmation operation is performed on the error detail screen P22 (Yes side of S25), the information update in step S26 is reflected on the task management screen P1. That is, the control unit 11 displays the first confirmation item or the second confirmation item that has been confirmed to have been confirmed in step S25 in a confirmed state.

  On the error detail screen P22, an operation key K26 for changing the display screen to the business management screen P1 is displayed. The operation key 26 may be displayed only when the pharmacist operating the client terminal 2 is a ward pharmacist, that is, when the client terminal 2 is the ward terminal 2B. Then, when the operation key K26 is operated, the control unit 11 displays the job management screen P1 on the display device 24. The control unit 11 also displays the display screen of the display device 24 when an operation for closing the error detail screen P22 is performed or when an operation for returning the screen transition is performed. Transition to the business management screen P1.

<Step S28>
Thereafter, in step S28, the control unit 11 performs the process when the preset operation end operation such as an operation for closing the operation management screen P1 or a logout operation is not performed (No side in S28). Return to step S23. Further, when the operation end operation is performed (Yes side of S28), the control unit 11 executes a pharmacist logout process, and then returns the process to step S21. Similarly, when the operation end operation is performed during the ward drug operation support process, a logout process of a pharmacist is performed, and then the process returns to step S21.

  As described above, in the ward drug operation support system 10, the first confirmation item and the second confirmation item are confirmed for each patient by referring to the first display region A122 and the second display region A123. It is possible to easily grasp the priority of the information and the presence / absence of confirmation. Accordingly, for example, the ward pharmacist can efficiently perform the work with reference to the priority of confirmation of the first confirmation item and the second confirmation item, the presence or absence of confirmation, and the like.

  In addition, the control unit 11 changes the display colors of the first divided display area A131 and the first divided display area A141 in the first display area A122 and the second display area A123 according to the priority classification. . Therefore, the ward pharmacist can easily grasp the priorities of the first confirmation item and the second confirmation item.

[Schedule creation function]
The ward drug operation support system 10 has a schedule creation function for automatically creating a ward drug operation schedule performed by a ward pharmacist. Specifically, when the schedule display key K11 displayed on the work management screen P1 is operated as shown in FIG. 10, the control unit 11 performs the first confirmation item and the A schedule creation process for creating a confirmation schedule for the second confirmation item is executed according to the control program. By the way, the schedule display key K11 may be displayed only on the ward terminal 2B. The schedule creation processing is executed by the schedule creation processing unit 113 of the control unit 11.

  More specifically, in the schedule creation process, the control unit 11 requires the first confirmation item and the second confirmation to be confirmed for each patient admitted to the ward in charge of the currently logged-in ward pharmacist. An acquisition process for reading the content of the item from the information storage unit 123 is executed. Specifically, in the acquisition process, the check result of the prescription check performed on the prescription data of each patient and the check result of the condition check performed on the patient corresponding to the prescription data or the prescription data. Obtained from the information storage unit 123. Thereby, the control unit 11 can recognize the error item and the confirmation required item. The acquisition processing is executed by the acquisition processing unit 111.

  The control unit 11 reads the business basic information D21 and the schedule configuration information D22 from the information storage unit 123. Then, the control unit 11 can process the scheduled work time of the ward pharmacist based on the processing time corresponding to each item included in the business basic information D21 and the scheduled work time included in the schedule configuration information D22. In such a range, the error items that have not been confirmed at the present time and the necessary confirmation items are automatically assigned, and the confirmation schedule is created.

  Specifically, the control unit 11 selects the error items that have not been confirmed at this time and the confirmation items that need to be checked in order from the item with the highest priority category, according to the scheduled work time of the ward pharmacist and the processing time. assign. In particular, the control unit 11 creates the confirmation schedule based on the processing ability of the pharmacist included in the schedule configuration information D22. For example, when the processing time is “10 minutes” and the processing capacity is “0.5”, “5 minutes” is calculated as the individual processing time. And the said control part 11 allocates the said error item and the said required confirmation item which are not completed confirmation at present from the item with the said high priority classification based on the ward pharmacist's scheduled work time and the said individual processing time. .

  FIG. 11 is a diagram showing an example of a calendar display screen P3 on which the confirmation schedule is reflected. Specifically, as shown in FIG. 11, the calendar display screen P3 displays the contents of the error item or the confirmation required item that should be confirmed for each working day of the ward pharmacist. In addition, when the number of the error items and the confirmation required items that are not displayed at one time in the display column corresponding to the work day is assigned to any of the work days, the work day selection operation or the mouse over In response to the operation, a list screen of information on the error item and the confirmation required item on the work day is displayed by screen transition or pop-up display.

  Here, also in the calendar display screen P3, the display colors of the error item and the confirmation required item differ depending on the priority classification. For example, in the calendar display screen P3, in the display column “May 21”, the type “interaction” and the patient name “Patient Ichiro” corresponding to the priority classification “Contraindication (high)” are displayed. "Is displayed with the first specific color such as red as the background. In the calendar display screen P3, in the display column of “May 21”, the type of the first confirmation item “priority combination” and the patient name “Saburo patient” whose priority classification corresponds to “attention (medium)”. "Is displayed with the second specific color such as yellow as the background. Further, in the calendar display screen P3, in the display column of “May 22”, the type of the second confirmation item “pre-operative withdrawal drug” corresponding to the priority classification “information provision (low)” and the patient name “Patient Jiro” is displayed with the first specific color such as blue as a background.

  In addition, the control unit 11 indicates the completion status of the error item or the required confirmation item that has already been confirmed in the first confirmation item or the second confirmation item on the calendar display screen P3. It is displayed on the calendar display screen P3 together with character information, background color, or mark. Further, the control unit 11 can arbitrarily change the confirmation schedule according to a user operation of the client terminal 2. For example, when the confirmation item is dragged and dropped on the calendar display screen P3, the control unit 11 can move the confirmation item.

  As described above, the ward pharmacist support system 10 can automatically create the confirmation schedule for each ward pharmacist by the schedule creation function, thereby improving the efficiency of each ward pharmacist. Confirmation omissions can be suppressed.

[Master setting function]
The ward drug operation support system 10 has an item setting function for editing the first confirmation item and the second confirmation item displayed on the operation management screen P1. Specifically, when the master setting key K12 displayed on the job management screen P1 is operated, the control unit 11 sets a determination condition for determining whether the first confirmation item and the second confirmation item need to be confirmed. The item setting process to be set is executed according to the control program. The item setting process is executed by the item setting processing unit 114 of the control unit 11.

  In the item setting process, the control unit 11 causes the client terminal 2 to display an item setting screen P4 shown in FIG. On the item setting screen P4, input display areas A41 to A43 are displayed. Further, the control unit 11 can execute addition and deletion of the first setting item and the second setting item displayed on the task management screen P1 in response to a user operation on the item setting screen P4. It is.

  The input display area A41 is used for inputting information such as contents of items to be registered on the item setting screen P4, ward, medical department, and pharmacist. The input display area A42 is used for inputting the type (inhibition, caution, information provision) and category (administration dose change, test report, pain, etc.) of an item registered on the item setting screen P4. If the item type is “Contraindication” or “Caution”, it is registered as the first confirmation item. If the item type is “Information provision”, it is registered as the second confirmation item. It can be considered. Further, in the item setting process, a configuration in which only the second confirmation item can be edited and the first confirmation item cannot be edited is also considered as another embodiment.

  When the item content is registered on the item setting screen P4, a display column of the registered item is added to the first display region A122 or the second display region A123 of the business management screen P1, and the display column The category is displayed as the item name. The input display area A43 is used to input a determination condition for determining that an item registered on the item setting screen P4 needs to be confirmed by a pharmacist.

  For example, in the input display area A43, one or a plurality of determination conditions can be set, and in particular, a plurality of determination conditions can be combined by logical sum (OR) or logical product (AND). Specifically, in the example shown in FIG. 12, each of classification, item, condition, extraction condition, and extraction period can be set as the determination condition. In the display column of the classification, for example, medicine, medicinal effect, ingredient, examination, disease name, body weight, body surface area, age, BMI, sex, regimen, vital, renal dysfunction, liver dysfunction, and medicine master are displayed in a pull-down or list display. And can be arbitrarily selected. In the item display column, information that can be input changes in accordance with the content selected in the classification display column.

  Specifically, when “drug” is selected as the classification, “drug” can be designated as the item. When “medicine” is selected as the category, “medicine (87 categories)” can be designated as the item. When “component” is selected as the classification, “component” can be designated as the item. When “inspection” is selected as the classification, “inspection item” can be designated as the item. When “disease name” is selected as the classification, “disease name” can be designated as the item. When “weight”, “body surface area”, “BMI”, “age”, or “gender” is selected as the classification, the item is not specified (eg, grayed out). When “regimen” is selected as the classification, “regimen name” can be designated as the item. When “Vital” is selected as the classification, “Body temperature”, “Maximum blood pressure”, “Minimum blood pressure”, “Heart rate”, “Respiration rate”, and the like can be specified as the items. When “renal dysfunction” or “liver dysfunction” is selected as the classification, the item is not specified (eg, grayed out). When “medicine master” is selected as the classification, any medicine can be selected from all medicines including spares included in the medicine master as the item.

  In the condition display field, “value”, “range”, and “difference from previous time” can be input. Specifically, in “value”, conditions and numerical values such as “=”, “≦”, “<”, “≧”, “>” can be input. In “Range”, “Lower limit value” and “Upper limit value” can be input. In “Difference from previous time”, “increase”, “decrease”, and “increase / decrease” can be selected. In the item setting screen P4, operation keys K41, K42, and K43 for starting the setting of any of “value”, “range”, and “difference from the previous time” are displayed as the determination conditions. Yes. When the operation key K41, K42, or K43 is operated, the control unit 11 is used to input “value”, “range”, and “difference from the previous” as shown in FIG. The condition input screen P5 is displayed on the client terminal 2 by pop-up or the like. Accordingly, the user can input “value”, “range”, “difference from previous time”, and the like as the determination conditions of the item using the client terminal 2.

  Specifically, on the condition input screen P5 shown in FIG. 13, an input display area A51 for inputting “value”, an input display area A52 for inputting “difference from the previous time”, and “range” are input. An input display area A53 is displayed. In the input display area A51, conditions such as “=”, “≦”, “<”, “≧”, “>” are input to the input field A511, numerical values are input to the input field A512, and the input field A513 is input. “And” or “or” is input. In the input display area A52, “increase”, “decrease”, and “increase / decrease” are input to the input field A521, and numerical values are input to the input field A522.

  In the input display area A53, the numerical value of the lower limit value is input in the input field A531, and conditions such as “=”, “≦”, “<”, “≧”, “>” are input in the input field A532. Is done. In the input display area A53, conditions such as “=”, “≦”, “<”, “≧”, “>”, etc., are input to the input field A533, and the numerical value of the upper limit value is input to the input field A534. Entered. Furthermore, in the input display area A53, “and” or “or” is input to the input field A535.

  Further, as shown in FIG. 12, in the input display area A43, in the display column for the extraction condition, “today”, “past”, “future”, “past (including the current day)”, and “future (including the current day) ) ”Can be selected. In the extraction period display field, the extraction period can be specified by the number of days or the like. For example, the control unit 11 performs processing so as not to extract the information after the extraction period has elapsed since the information was first extracted.

  For example, in the item setting screen P4 shown in FIG. 12, the check type is “information provision” which is the second confirmation item, and the determination condition is set by the logical sum of “condition 1” and “condition 2”. Yes. Specifically, in “Condition 1”, “drug” is selected as the classification, and “durotep” is selected as the item. “Durotep” is an abbreviation for “Durotep MT patch 2.1 mg”. In “Condition 2”, “Vital” is selected as the classification, “Body temperature” is selected as the item, and “≧ 38” is input as the value. When the determination condition of the second confirmation item is registered in this state, the control unit 11 includes the case where “durotep” is included in the prescription data and the body temperature of the patient is “38 degrees or more”. It is determined that the “pain” added as the second confirmation item should be confirmed. In addition, when registration or deletion of the first confirmation item is performed, conditions for determining whether the prescription data is appropriate or need to be confirmed by a pharmacist in the prescription check and the condition check are changed. Become.

[Second Embodiment]
Hereinafter, the ward drug business support system 20 according to the second embodiment of the present invention will be described. In the ward drug operation support system 20, the same components as those in the ward drug operation support system 10 (see FIG. 1) described in the first embodiment are denoted by the same reference numerals, and the description thereof is omitted.

  As shown in FIG. 14, in the ward drug business support system 20, the control unit 11 performs the acquisition processing unit 111, inspection determination processing unit 115, issuance control processing unit 116, hold processing unit 117, hold display. A processing unit 118 and a batch dispensing processing unit 119 are included. Specifically, the control unit 11 executes various processes according to the control program, so that the control unit 11 performs the acquisition processing unit 111, the inspection determination processing unit 115, the issuance control processing unit 116, It functions as the hold processing unit 117, the hold display processing unit 118, and the batch dispensing processing unit 119.

  As described above, the acquisition processing unit 111 performs a prescription check (prescription inspection) for determining whether or not one or a plurality of the first confirmation items is appropriate for the prescription data based on the prescription check information D11. Execute and acquire the check result of the prescription check. The prescription check is performed by the control unit 11 when the server 1 acquires the prescription data from the host system 6, when dispensing is started for the prescription data, or when a prescription check is requested by a user. It is executed by the processing unit 111.

  The inspection determination processing unit 115 determines whether or not an inspection by a ward pharmacist who operates in a ward where a patient is hospitalized is necessary based on the prescription data and predetermined inspection determination conditions. Is possible. The issuance control processing unit 116 issues the prescription data determined to be inspected by the ward pharmacist by at least the inspection determination processing unit 115 as a dispensing target when the issuance operation by the ward pharmacist is performed. It is possible. For example, the issuance of the prescription data is to enable the dispensing of medicine based on the prescription data by the dispensing pharmacist or the dispensing device 3. The ward pharmacist performs an inspection operation for confirming whether or not the content of the prescription data is appropriate, and performs the issuing operation when determining that there is no problem in the prescription data.

  The holding processing unit 117 can hold the prescription data issued by the issuing control processing unit 116 in a state before starting dispensing according to a predetermined holding condition. When the prescription data held by the hold processing unit 117 is displayed as a list, the hold display processing unit 118 can display whether or not each of the prescription data was subject to inspection by the ward pharmacist. It is. The batch dispensing processing unit 119 can collectively start dispensing processing for a plurality of pre-selected prescription data among the prescription data held by the holding processing unit 117.

[Prescription data processing flow]
In the ward drug business support system 20, the prescription data is processed according to the processing flow shown in FIG. First, an outline of a processing flow of the prescription data in the ward service support system 20 according to the second embodiment will be described with reference to FIG. Various processes (see FIGS. 16 to 20) executed by the control unit 11 to realize the processing flow of the prescription data will be described later.

<Prescription reception process S1>
As shown in FIG. 15, when the prescription data is input from the host system 6 to the ward drug business support system 20, the prescription data becomes a processing target of the prescription receiving process S1. In the prescription reception process S1, the control unit 11 of the server 1 performs the prescription check on the prescription data, and determines whether the prescription data is a target for ward side inspection and dispensing side inspection. Is done. And if it determines with not being the object of the said ward side inspection and the said dispensing side inspection, the said prescription data will be issued as a dispensing object and will become the process target of dispensing suspension determination process S5. On the other hand, if it determines with being the object of the said ward side inspection, the said prescription data will become a process target of ward side inspection process S2 without being issued as a dispensing object. Moreover, also when it determines with it being the object of the said dispensing side inspection, the said prescription data becomes a process target of dispensing side inspection process S4, without being issued as a dispensing object.

<Ward side inspection process S2>
In the ward side inspection process S2, the process branches according to the inspection result of the prescription data input by the ward pharmacist using the ward terminal 2B. Here, when an issuing operation indicating that there is no problem in the inspection result is performed, the prescription data becomes a processing target of the dispensing suspension determination process S5. On the other hand, if there is a problem in the inspection result and an NG issuance operation is performed to the effect that the prescription data is corrected (reissued) by a questionable inquiry to the doctor, the prescription data is discarded to discard the prescription data It becomes the target of the process S3.

<Discard process S3>
In the discarding process S3, the prescription data is discarded. In the discarding process S3, the prescription data state is set to an invalid state in which the issuing operation cannot be performed without discarding the prescription data, and the prescription data after correction (after reissuance) is input, Data may be overwritten.

  In the ward side inspection process S2, when the prescription data issuance operation is performed, a dispensing side inspection transfer determination process for determining the necessity of the dispensing side inspection performed by the dispensing pharmacist may be executed. Other embodiments are possible. For example, when the ward pharmacist changes predetermined items such as whether or not the prescription data is packaged or whether or not the medicine is crushed, it is determined that the inspection by the dispensing pharmacist is necessary. In addition, it may be determined that the dispensing side inspection is necessary when the number of days remaining until the start date of taking in the prescription data is equal to or longer than a predetermined period. In the ward drug operation support system 20, various items related to the dispensing method can be individually changed for the prescription data according to the operation of the ward pharmacist, and various items related to the dispensing method are set for each patient. It is also possible to do. In the dispensing side inspection transfer determination process, when it is determined that the prescription data needs to be inspected by the dispensing pharmacist, the prescription data becomes a processing target of the dispensing side inspection process S4. On the other hand, when it is determined that the inspection by the dispensing pharmacist is not necessary for the prescription data, the prescription data is issued as a dispensing target and becomes a processing target of the dispensing hold determination processing S5.

<Dispensing side inspection process S4>
In the said dispensing side inspection process S4, a process branches according to the inspection result of the said prescription data input using the said dispensing room terminal 2A by the said dispensing pharmacist. Here, when an issuing operation indicating that there is no problem in the inspection result is performed, the prescription data is issued as a dispensing target and becomes a processing target of the dispensing hold determination process S5. On the other hand, when an NG issuance operation indicating that there is a problem in the inspection result is performed, the prescription data becomes a processing target of the discarding process S3 that discards the prescription data without being issued as a dispensing target.

<Dispensing hold determination process S5>
In the dispensing hold determination process S5, the prescription data is held in a state before the start of dispensing according to the hold condition. For example, the holding condition is that the prescription classification (regular, temporary, outpatient, etc.) of the prescription data is “periodic”, or that the ward side inspection is performed. Here, when the holding condition is satisfied, the prescription data is held in a state before the start of dispensing and becomes a processing target of the tightening management process S6. Moreover, when the said reservation conditions are not satisfied, the said prescription data will become the process target of the said dispensing process S7.

<Tightening management process S6>
In the tightening management process S6, the presence or absence of the start of dispensing for the prescription data suspended in the dispensing suspension determination process S5 is managed. Specifically, when an issuing operation is performed on the prescription data, or when a pre-set issuing time has arrived for the prescription data, the prescription data becomes a processing target of the dispensing process S7.

<Dispensing treatment S7>
In the dispensing process S7, dispensing data for dispensing medicine is generated based on the prescription data and stored in the shared data folder of the storage unit 12. Thus, each of the dispensing devices 3 acquires the dispensing data from the shared data folder, and dispenses a medicine based on the dispensing data. The dispensing by each dispensing device 3 may be started by inputting the dispensing data from the server 1 to each dispensing device 3.

  By the way, a configuration in which the ward drug business support system 20 can switch between the validity and invalidity of a holding function for temporarily holding the issuance of the prescription data, or a structure not having the holding function is also conceivable. Specifically, when the ward drug business support system 20 has the hold function disabled or does not have the hold function, the dispensing hold determination process S5 and the closing management process S6 are omitted, The prescription data issued as the dispensing target is the processing target of the dispensing process S7. That is, when it is determined that the inspection is unnecessary in the prescription receiving process S1, when the issuing operation is performed in the ward side inspection process S2, or when the issuing operation is performed in the dispensing side inspection process S4. It is conceivable that the dispensing device 3 starts dispensing the prescription data. Specifically, the issuing of the prescription data is a process for causing the dispensing device 3 used for dispensing a medicine to start dispensing based on the prescription data. For example, in the ward drug business support system 20, when the control unit 11 issues the prescription data as a target for dispensing, a dispensing instruction including the dispensing data for starting dispensing based on the prescription data is issued. Transmission to the dispensing device 3 is conceivable. Note that such processing is executed by, for example, the issue control processing unit 116 of the control unit 11. Thereby, for example, the tablet packaging process based on the dispensing data is started by the tablet packaging machine included in the dispensing device 3.

  Subsequently, various processes executed by the control unit 11 in order to realize the processing flow of the prescription data will be described with reference to FIGS. FIGS. 21 to 30 are diagrams illustrating examples of various operation screens displayed on the client terminal 2 by the control unit 11 of the server 1. Note that the control unit 11 causes the client terminal 2 to display various operation screens by transmitting the operation screen data configured using a page description language such as HTML to the client terminal 2. Here, each of the operation screens is, for example, a 1920 × 1080 dot full high-definition screen, and the display device 24 of the client terminal 2 on which each of the operation screens is displayed is a full high-definition display device. .

[Prescription reception processing]
First, the prescription receiving process executed by the control unit 11 will be described with reference to FIG. The prescription receiving process is an example of a processing procedure for realizing the prescription receiving process S1. The prescription receiving process is executed for each prescription data by the control unit 11 when the control unit 11 acquires the prescription data from the host system 6, for example.

<Step S31>
In step 31, the control unit 11 needs to be examined (ward side inspection) by a ward pharmacist who performs work in the ward where the patient is hospitalized based on the prescription data and predetermined ward inspection conditions. It is determined whether or not. Here, the process of step S31 is executed by the inspection determination processing unit 115. If it is determined that the ward side inspection is necessary (S31: Yes), the process proceeds to step S311. If it is determined that the ward side inspection is not necessary (S31: No), the process is stepped. The process proceeds to S32.

  For example, the ward inspection condition is that any one of the following conditions C1 to C7 is satisfied. Condition C1: A predetermined error is included in the check result. Condition C2: The prescription category of the prescription data is a predetermined category. Condition C3: The hospital ward of the patient corresponding to the prescription data is a predetermined ward. Condition C4: The department of the patient corresponding to the prescription data is a predetermined department. Condition C5: Prescription medicine is included in the prescription data. Condition C6: The patient corresponding to the prescription data is a predetermined patient. Condition C7: The patient's disease corresponding to the prescription data is a predetermined disease (disease name). The patient's disease is included in the prescription data or can be acquired from the host system 6. The condition C1 may not be included in the ward inspection conditions.

  In addition, the ward inspection condition may be that a combination of any of the conditions C1 to C7 is satisfied. For example, the ward inspection condition is that either the condition C3 condition or the condition C4 is satisfied and the condition C2 is satisfied. Specifically, when the prescription classification of the prescription data is “periodic” indicating that the prescription is a prescription for an inpatient, and the inpatient ward corresponding to the prescription data is “A”, the ward It can be considered that the inspection conditions are satisfied.

  In addition, either the condition C3 or the condition C4 is satisfied and the condition C2 is satisfied as the ward inspection condition, and either of the condition C1 or the condition C5 It may be considered that the condition is satisfied as the ward inspection condition. Specifically, the prescription classification of the prescription data is “periodic”, the inpatient ward of the patient corresponding to the prescription data is “A ridge”, and a combined contraindication predetermined in the check result, etc. If the error is included, it may be determined that the ward inspection condition is satisfied.

<Step S311>
In step S <b> 311, the control unit 11 does not issue the prescription data as a dispensing target, and gives ward side inspection information indicating that the ward side inspection is necessary to the prescription data. For example, the provision of the ward side inspection information is performed by changing the ward side inspection flag included in the prescription data from 0 to 1. Thereby, in the ward side inspection process (see FIG. 17), which will be described later, it is possible to determine whether each of the prescription data is an object of the ward side inspection based on whether or not the ward side inspection information is given. It becomes.

<Step S32>
In step S <b> 32, the control unit 11 needs to perform inspection (dispensing side inspection) by a dispensing pharmacist in charge of dispensing the prescription data based on the prescription data and preset dispensing side inspection conditions. Determine whether. If it is determined that the dispensing side inspection is necessary (S32: Yes), the process proceeds to step S33, and if it is determined that the dispensing side inspection is not necessary (S32: No), the process is performed. The process proceeds to S321.

  For example, the dispensing side inspection condition is that a master code error indicating that the contents corresponding to various code information included in the prescription data is not stored as master information of the storage unit 12 has occurred. Or the prescription data is a deleted prescription.

<Step S321>
In step S321, the control unit 11 issues the prescription data as a dispensing target, and executes a prescription data issuance process (see FIG. 19) described later for the prescription data. In the prescription data issuance process, dispensing is started for the prescription data, or the dispensing of the prescription data is suspended.

<Step S33>
On the other hand, in step S <b> 33, the control unit 11 does not issue the prescription data as a target for dispensing, and gives dispensing side inspection information indicating that the dispensing side inspection is necessary for the prescription data. For example, the dispensing side inspection information is given by changing the dispensing side inspection flag included in the prescription data from 0 to 1. Thereby, in the below-mentioned dispensing side inspection process (see FIG. 18), it is possible to determine whether or not each of the prescription data is an object of the dispensing side inspection based on whether or not the dispensing side inspection information is given. It becomes.

[Ward side inspection process]
Next, the ward inspection process executed by the control unit 11 will be described with reference to FIG. The ward side inspection process is an example of a processing procedure for realizing the ward side inspection process S2 and the discarding process S3.

<Step S41>
In step S41, as in step S21 (see FIG. 9), the control unit 11 performs a predetermined job start operation by the ward pharmacist using the ward terminal 2B (Yes in S41). Side) The process proceeds to step S42. Further, until the operation start operation is performed (No side in S41), the process waits in step S41. Specifically, the operation start operation is a login operation for inputting identification information such as a name or ID of a ward pharmacist and a password set in advance for each ward pharmacist.

<Step S42>
In step S42, the control unit 11 displays a patient list screen P6 on the ward terminal 2B. In the patient list screen P6, among the patients in charge of the logged-in ward pharmacist who is determined to have performed the operation start operation in the step S41, the ward pharmacist is prescription data to be examined and is in an unexamined state ( A list of patients corresponding to prescription data that is not yet issued is displayed. Specifically, the control unit 11 includes prescription data in which the ward-side inspection information is assigned to the prescription data corresponding to the patient in charge of the ward pharmacist, and the prescription data in the unchecked state is the ward pharmacist. Is determined to be prescription data to be examined.

  That is, when the ward side inspection is performed by the ward pharmacist, the control unit 11 displays the information to be inspected for each patient corresponding to the prescription data to be inspected (step S42), and the dispensing pharmacist When dispensing side inspection is performed, information to be inspected is displayed in units of prescription data (step S62 described later). Thereby, since the screen suitable for each situation where the ward side inspection capable of examining the patient at the time of examination and the dispensing side examination without examining the patient at the time of examination is displayed, the ward pharmacist and Efficient inspection work by the dispensing pharmacist is supported. For example, when the dispensing side inspection is performed, it is conceivable that the prescription data that is the object of the dispensing side inspection is displayed in a list in order of issue date or order or prescription order number. On the other hand, in the patient list screen P6 displayed when the ward-side inspection is performed, for example, a list of patients corresponding to the prescription data that is the object of the ward-side inspection is displayed, and any of the patients is selected. When selected, it is conceivable that one or a plurality of prescription data to be subjected to the ward side inspection among prescription data corresponding to the selected patient is displayed. Further, the control unit 11 does not display a list of patients as in the patient list screen P6, but in a patient unit corresponding to the prescription data that is the subject of the ward side inspection, for example, as in a detail screen P7 described later. It is also possible to display a separate individual inspection screen and display the individual inspection screen for each patient in accordance with a switching operation such as a predetermined flick operation. In this case, on the individual inspection screen, one or a plurality of prescription data that is a target of the ward side inspection among prescription data corresponding to the patient is displayed. As a result, when there are a plurality of prescription data to be inspected for one patient, the ward pharmacist can simultaneously inspect the plurality of prescription data, so that the work efficiency is increased.

  FIG. 21 is a diagram showing an example of the patient list screen P6. As shown in FIG. 21, the patient list screen P6 includes patient list area A61, search area A62, and operation keys K61 to K64 along with identification information such as a name or ID for identifying the currently logged-in ward pharmacist. Etc. are displayed.

  In the patient list area A61, a list of patients corresponding to prescription data in which the ward side inspection information is given and is not inspected among the patients in charge of the currently logged in ward pharmacist is displayed. Is done. In the patient list area A61, one or a plurality of prescription data corresponding to each patient is individually displayed, but each prescription data is displayed so as to be continuous in units of the patient. For example, in the patient list screen P6 shown in FIG. 21, two unexamined prescription data corresponding to the patient “Ichiro Yuyama” are displayed in succession, and the data corresponding to the patient “Jiro Yuyama” is not displayed. Two prescription data in the inspection state are also displayed continuously. The patient list area A61 displays an operation unit for selecting one or more prescription data corresponding to one or more patients displayed in the patient list area A61 according to a user operation. The selected area A621 is displayed. The selection area A621 is displayed for each unexamined prescription data corresponding to the patient for each patient, and the ward pharmacist performs an operation for individually selecting the prescription data using the selection area A621. Is possible. In the patient list area A61, only a list of patients with prescription data in the unexamined state is displayed, and information on each of the prescription data is not displayed as another embodiment.

  In the search area A62, an operation unit for inputting a search condition for narrowing down a list of patients displayed in the patient list area A61 is displayed. For example, the search conditions include prescription data inspection status (impossible, unexamined, inspected), ward, department, prescription classification, doctor in charge, pharmacist in charge, patient, start date of taking, prescription number, prescription order, etc. Is included. Each item of the search condition displays the number of cases when narrowing down is performed for that item. And when the said search conditions are input in the said search area | region A62 and search start operation is performed, the said control part 11 will be only one or several prescription data corresponding to the one or several patients who satisfy | fill the said search conditions. Is extracted and displayed in the patient list area A61.

  The operation key K61 is an operation key operated to issue prescription data selected in the selection area A621 among the patient prescription data displayed in the patient list area A61. The operation key K62 is an operation key operated to issue NG the prescription data selected in the selection area A621 among the patient prescription data displayed in the patient list area A61.

  The operation key K63 is displayed on the upper end of the patient list area A61, and is an operation key for expanding and reducing the display area of the patient list area A61 in the vertical direction. The operation key K64 is an operation key that is displayed at the boundary between the patient list area A61 and the search area A62, and expands and contracts the display area of the patient list area A61 in the left-right direction.

  Specifically, each time the operation key K63 is operated, the control unit 11 hides the operation key K61 and the operation key K62 and expands the display area of the patient list area A61 in the vertical direction. And the state in which the operation key K61 and the operation key K62 are displayed by reducing the display area of the patient list area A61 in the vertical direction.

  Similarly, each time the operation key K64 is operated, the control unit 11 hides the search area A62 and expands the display area of the patient list area A61 in the left-right direction, and the patient list area A61. The display area is reduced in the horizontal direction to switch to the state where the search area A62 is displayed.

  FIG. 21 shows an initial display state in which the display area of the patient list area A61 is reduced vertically and horizontally, and FIG. 22 shows the display area of the patient list area A61 vertically and horizontally. The expanded state is shown in.

<Step S43>
In step S43, the control unit 11 determines whether or not a detail display operation for displaying details of patients on the patient list screen P6 has been performed. For example, the detailed display operation is a selection operation of the name of the patient displayed in the patient list area A61. If it is determined that the detail display operation has been performed (S43: Yes), the process proceeds to step S44. If it is determined that the detail display operation has not been performed (S43: No), the process is performed. Proceeds to step S45.

<Step S44>
In step S44, the control unit 11 displays a patient detail screen P7 for displaying details of the patient who is the object of the detail display operation among the patients displayed in the patient list area A61. Specifically, the control unit 11 determines that the patient whose name is selected in step S43 among the patients displayed in the patient list area A61 is the target of the detailed display operation.

  FIG. 23 is a diagram showing an example of the patient details screen P7. As shown in FIG. 23, the patient details screen P7 displays a current prescription data area A71, a past prescription data area A72, a related data area A73, operation keys K71 to K78, and the like. In particular, the control unit 11 displays the current prescription data region A71 on the left side of the screen and the past prescription data region A72 on the right side of the screen on the patient detail screen P7. The patient details screen P7 includes identification information such as a name or ID for identifying the currently logged-in ward pharmacist, and the name, ID, gender, age, and the like of the patient who is the object of the detailed display operation. Basic patient information such as height, weight, and hospital ward is also displayed.

  The current prescription data area A71 displays the contents of the current prescription data that is one or a plurality of unissued prescription data among the prescription data corresponding to the patient and is the current candidate for dispensing. For example, when there are a plurality of the current prescription data, the current prescription data are displayed side by side in the vertical direction in the current prescription data area A71. The prescription data area A71 also displays basic prescription information such as prescription date, taking start date, order number, department, ward, and prescription category (regular, temporary, outpatient, etc.).

  In the current prescription data area A71, an operation unit A711 such as a check box for receiving an operation for selecting the current prescription data displayed in the current prescription data area A71 is displayed for each prescription data. Is done. When the patient detail screen P7 is closed in a state where the current prescription data is selected by the operation of the operation unit A711, the control unit 11 stores the selection state of the current prescription data and stores the patient list. In the area A61, the selection area A621 corresponding to the current prescription data is displayed in a selected state.

  In addition, in the current prescription data area A71, a check result area A712 in which a check result of the prescription check is displayed and a comment display area in which a prescription comment of the prescription data is displayed corresponding to each of the current prescription data. A713 is displayed. Thereby, the said ward pharmacist can grasp | ascertain easily the check result of the said prescription check, and the content of the said prescription comment.

  Further, in the current prescription data area A71, a detail area A714 is displayed corresponding to each current prescription data. The control unit 11 switches the display of the details of the current prescription data in accordance with the operation of the detail region A714. FIG. 23 shows a state where the details of the prescription data are displayed. In the specification area A714, information such as Rp number, drug name / usage name, daily dose / two numbers, unit, PTN, and remarks is displayed as the details of the current prescription data. Further, in the specification area A714, the control unit 11 prescribes each medicine in the current prescription data displayed in the specification area A714 and each medicine in the past prescription data that is past prescription data of the patient. The previous comparison area A715 where the amount comparison result is displayed is displayed. Specifically, the control unit 11 determines the prescription amount between the medicines of the past prescription data when the medicine was most recently prescribed for each medicine of the current prescription data displayed in the specification area A714. Compare. In other words, there are cases where the comparison target of each medicine included in the current prescription data is different past prescription data. Then, as shown in FIG. 23, for example, when the prescription amount of the medicine has increased compared to the previous time, the control unit 11 has an up arrow, when the prescription amount has decreased compared to the previous time, a down arrow, If they are the same, an equal sign is displayed in the previous comparison area A715. Thereby, the ward pharmacist can easily grasp the comparison result between the current prescription data and the past prescription data, and can efficiently perform a prescription inspection for determining the suitability of the current prescription data. it can.

  On the other hand, in the past prescription data area A72, a list of past prescription data regarding past prescriptions for the patient is displayed. Specifically, the past prescription data is one or more issued prescription data among prescription data corresponding to the patient. Thus, in the ward drug business support system 20, the control unit 11 displays one or a plurality of the current prescription data in order to display prescription data corresponding to the patient in the patient unit screen on the patient detail screen P7. And one or a plurality of the patient's past prescription data can be displayed simultaneously.

  In the past prescription data area A72, for example, prescription basic information such as prescription date, taking start date, order number, department, ward, and prescription category (regular, temporary, outpatient, etc.) is displayed. In the past prescription data area A72, a switching operation for switching whether to display details of the past prescription data displayed in the past prescription data area A72 is possible. Specifically, each time the past prescription data selection operation is performed in the past prescription data area A72, the control unit 11 switches whether to display details of the past prescription data for which the selection operation has been performed. . Here, FIG. 23 shows a state where details of each of the past prescription data are closed, and FIG. 24 shows a state of the past prescription data area A72 in a state where the details of each of the past prescription data are opened. It is a partial enlarged view.

  In the related data area A73, the detailed item areas A731 to A735 are displayed. The control unit 11 switches the presence / absence of display of the patient's prescription history according to the operation of the detailed item region A731, and switches the presence / absence of display of the patient's examination value according to the operation of the detailed item region A732. FIG. 26 is a partially enlarged view showing an example of a state in which the detailed item area A731 is expanded and the patient's prescription history is displayed, and FIG. 27 is an enlarged view of the detailed item area A732 and the patient's prescription history is displayed. It is the elements on larger scale which show an example of the state where the test value was displayed.

  Further, the control unit 11 switches the display of the patient's disease name according to the operation of the detailed item area A733, and switches the display of the patient's allergy according to the operation of the detailed item area A734. Here, FIG. 28 is a partially enlarged view showing an example of a state in which the detailed item area A733 is expanded and the patient's disease name is displayed, and FIG. 29 is an expanded view of the detailed item area A734 and allergies of the patient are displayed. It is the elements on larger scale which show an example of the state where is displayed. Further, the control unit 11 switches the presence / absence of display of a patient comment registered in advance for each patient according to the operation of the detailed item area A735. FIG. 30 is a partially enlarged view showing an example of a state in which the detailed item region A735 is expanded and the patient comment of the patient is displayed.

  Thus, on the patient detail screen P7, the contents of the prescription data to be examined are displayed for each patient, and patient-specific information such as the prescription history, test value, disease name, allergy, and patient comment of the patient is displayed. Can be displayed. Therefore, the ward pharmacist can efficiently determine the suitability of one or more prescription data of the patient based on the patient-specific information when performing the ward side examination.

  The operation key K71 is an operation key operated to issue the current prescription data displayed in the current prescription data area A71. The operation key K72 is an operation key operated to issue the current prescription data displayed in the current prescription data area A71 as NG. Further, the operation key K73 is an operation key for displaying the medicine history of the patient, the operation key K74 is an operation key for displaying a record of medication instruction for the patient, and the operation key K75. Is an operation key for displaying the patient master. For example, when any one of the operation keys K73 to K75 is operated, the control unit 11 activates software for realizing a function of a medication management system that manages a medication history of the patient, and the medication management Information such as the patient's medication history, medication instruction, or patient master managed by the system is displayed. Further, when the server 1 is configured to be able to cooperate with the medication management system provided separately from the server 1, the control unit 11 performs the medication according to the operation of the operation keys K73 to K75. It is also possible to read out and display information such as the patient's medication history, medication instruction, or patient master from the management system. In addition, when the said control part 11 does not have the function of the said medication management system, or when not cooperating with the said medication management system, the said control part 11 gray-outs the said operation keys K73-K74, for example It is conceivable that the operation cannot be performed by a display or the like. Further, when the server 1 does not have the function of the medication management system and the patient master is not stored in the storage unit 12, or the server 1 cooperates with the medication management system. If not, the control unit 11 may be in a state where the operation key K75 cannot be operated by, for example, grayout display.

  The operation key K76 and the operation key K77 are represented at the upper and lower ends of the current prescription data area A71 and the past prescription data area A72, and move up and down the display areas of the current prescription data area A71 and the past prescription data area A72. Operation keys for expanding and contracting in the direction. The operation key K78 is displayed on the boundary between the current prescription data area A71 and the past prescription data area A72, and is an operation key for expanding and reducing the display area of the current prescription data area A71 in the horizontal direction. is there.

  Specifically, each time the operation key K76 is operated, the control unit 11 hides the operation keys K71 to K75 and moves the display areas of the current prescription data area A71 and the past prescription data area A72 up and down. The operation keys K71 to K75 together with the current prescription data area A71 and the past prescription data area A72 by reducing the display area of the current prescription data area A71 and the past prescription data area A72 in the vertical direction. Switch to the state where is displayed.

  Further, each time the operation key K77 is operated, the control unit 11 hides the related data area A73 and expands the display area of the current prescription data area A71 and the past prescription data area A72 in the vertical direction. A state where the display area of the current prescription data area A71 and the past prescription data area A72 is vertically reduced and the related data area A73 is displayed together with the current prescription data area A71 and the past prescription data area A72. Switch between and.

  Further, each time the operation key K78 is operated, the control unit 11 hides the past prescription data area A72 and expands the display area of the current prescription data area A71 in the left-right direction, and the current time The display area of the prescription data area A71 is reduced in the horizontal direction to switch between the current prescription data area A71 and the past prescription data area A72.

  FIG. 23 shows an initial display state where the current prescription data area A71 is reduced vertically and horizontally, and FIG. 24 shows the display area of the current prescription data area A71 vertically and horizontally. The expanded state is shown.

<Step S45>
Next, in step S45, the control unit 11 determines whether or not an operation for issuing the prescription data has been performed. If it is determined that the issuing operation has been performed (S45: Yes), the process proceeds to step S46. If it is determined that the issuing operation has not been performed (S45: No), the process is performed in step S46. The process proceeds to S47.

  Specifically, the controller 11 issues the prescription data issuing operation when the operation key K61 is operated on the patient list screen P6 and when the operation key K71 is operated on the patient detail screen P7. Is determined to have been performed. More specifically, when the operation key K61 is operated, the control unit 11 performs a batch issuing operation on one or a plurality of prescription data of one or a plurality of patients selected on the patient list screen P6. Judge that it was done. In other words, the control unit 11 can issue one or a plurality of prescription data of one or a plurality of patients selected on the patient list screen P6 in batches and issue a ward side inspection as a dispensing target. It is. When the operation key K71 is operated on the patient detail screen P7, the control unit 11 selects the selection area A711 in the current prescription data displayed on the patient detail screen P7. It is determined that the issuing operation was performed only for the current prescription data. In other words, the control unit 11 can collectively issue the ward-side inspection for one or a plurality of prescription data of one patient selected on the patient detail screen P7 and issue it as a dispensing target. is there.

<Step S46>
In step S46, the control unit 11 executes a prescription data issuing process (see FIG. 19) to be described later for the prescription data that has been the object of the issuing operation in step S45. In the prescription data issuance process, dispensing is started for the prescription data, or the dispensing of the prescription data is suspended. As described above, the control unit 11 issues the prescription data determined to be inspected by the ward pharmacist as a subject to be dispensed when the ward pharmacist is inspected. Here, the process is executed by the issue control processing unit 116. Thereby, for the prescription data determined to require the ward side inspection, dispensing for the prescription data is started after inspection by a ward pharmacist who examines a patient corresponding to the prescription data in the ward. Will be.

  By the way, as mentioned above, it is also conceivable that the control unit 11 executes the dispensing side inspection transfer determination process. In this case, the control unit 11 determines whether or not the dispensing side inspection is necessary in order for one or a plurality of the prescription data that is the object of the issuing operation in the previous stage of the step S46. For example, the control unit 11 can add a prescription comment set in advance for the prescription data in response to a user operation on the patient detail screen P7. And the said control part 11 determines the propriety of the chemical | medical agent accommodated in the same medicine package at the time of dispensing based on the content instruct | indicated by the said prescription comment according to the dispensing side inspection transfer conditions set beforehand. Specifically, as the prescription comment, a packing instruction, a heat instruction, a crushing / pulverizing instruction, a powder unwinding instruction, a simple suspension process, a mixing (MIX) instruction, a tablet powder mixing instruction, a complete vertical instruction, a single instruction It is conceivable that a medicine information output instruction, a notebook label output instruction, and the like can be selected. Further, in the prescription comment associated with the prescription data, input person information for identifying which one of the dispensing pharmacist and the ward pharmacist is input is added, and when the prescription data is displayed, or the prescription data When the prescription corresponding to is printed, the input person information may be displayed. In addition, the control part 11 can also consider the structure which can register the patient comment matched with every said patient into the said patient master separately from the prescription comment matched with the said prescription data. Thereby, the said control part 11 can change automatically the dispensing method of the said prescription data about the said patient based on the said registered said patient comment.

  For example, in the dispensing side inspection transfer determination process, the control unit 11 includes medicines of components that are not preferably packaged in the same medicine package, and the prescription data includes instructions for packaging those medicines. When it is selected as a prescription comment, it can be considered that the prescription data needs to be examined by the dispensing side. And when the said control part 11 judges that the said dispensing side inspection is required in the said dispensing side inspection transfer determination process, without issuing the said prescription data as a dispensing object (without performing S46), The dispensing side inspection information is assigned to the prescription data, and the process proceeds to step S51. Thereby, in the dispensing side inspection process described later, the prescription data is determined as prescription data that requires the dispensing side inspection. In addition, the said control part 11 makes a process transfer to said step S46, when it judges that the said dispensing side inspection is unnecessary in the said dispensing side inspection transfer determination process.

<Step S47>
In step S47, the control unit 11 determines whether an NG issuing operation for the prescription data has been performed. If it is determined that the NG issuing operation has been performed (S47: Yes), the process proceeds to step S48. If it is determined that the NG issuing operation has not been performed (S47: No), the process is performed. Proceeds to step S49.

  Specifically, the control unit 11 issues the NG of the prescription data when the operation key K62 is operated on the patient list screen P6 and when the operation key K72 is operated on the patient detail screen P7. It is determined that the operation has been performed. More specifically, when the operation key K62 is operated, the control unit 11 performs an NG issuing operation on one or a plurality of prescription data of one or a plurality of patients selected on the patient list screen P6. Is determined to have been performed. In addition, when the operation key K72 is operated on the patient detail screen P7, the control unit 11 causes the control unit 11 to select the selection area A711 among the current prescription data displayed on the patient detail screen P7. It is determined that the NG issue operation was performed only for the current prescription data that is selected

<Step S48>
In step S <b> 48, the control unit 11 executes a discard process for discarding one or a plurality of the prescription data that is a target of the NG issue operation. In this case, the dispensing for the prescription data is not executed. Thus, the control unit 11 can collectively issue a plurality of the prescription data determined to be inspected by the ward pharmacist.

<Step S49>
In step S49, the control unit 11 determines whether or not the previous comparison area A715 has been selected in the detail area A714 of the current prescription data area A71. Specifically, when the previous comparison area A715 has been selected (S49: Yes), the process proceeds to step S50, and when the previous comparison area A715 has not been selected (S49: No), the process proceeds to step S51. Transition.

<Step S50>
In step S50, the control unit 11 may automatically expand and display details of the past prescription data to be compared corresponding to the selected previous comparison area A715 in the past prescription data area A72. Conceivable. Thereby, the work efficiency of the prescription inspection about the current prescription data of the ward pharmacist can be improved. For example, when the details of the past prescription data to be compared corresponding to the selected previous comparison area A715 are not displayed in the past prescription data area A72, the control unit 11 displays the details of the past prescription data. It may be possible to display at the top of the past prescription data area A72. Note that the past prescription data to be compared corresponding to the previous comparison area A715 may be separately displayed on a pop-up screen or the like.

<Step S51>
Thereafter, in step S51, the control unit 11 performs the process when a preset operation end operation such as an operation for closing the patient list screen P6 or a logout operation is not performed (No side in S51). Return to step S43. If the operation end operation is performed (Yes in S51), the control unit 11 executes a pharmacist logout process and then returns the process to step S41.

[Dispensing side inspection process]
Next, the dispensing side inspection process executed by the control unit 11 will be described with reference to FIG. The dispensing side inspection process is an example of a processing procedure for realizing the dispensing side inspection process S4 and the discarding process S3.

<Step S61>
In step S61, the control unit 11 performs a predetermined job start operation using the dispensing room terminal 2A by the dispensing pharmacist, as in step S21 (see FIG. 9) (Yes in S61). Side), the process proceeds to step S62. Also, until the operation start operation is performed (No side in S61), the process waits in step S61. Specifically, the operation start operation is a login operation for inputting identification information such as the name or ID of the dispensing pharmacist and a password set in advance for each dispensing pharmacist.

<Step S62>
In step S62, the control unit 11 displays a prescription data list screen that displays a list of prescription data that the prescription data that the dispensing pharmacist should check and is in an unchecked state. Specifically, the control unit 11 is prescription data to which the dispensation side inspection information is to be inspected, which is prescription data to which the dispensation side inspection information is given and is in an uninspected state. Is determined. The prescription data list screen is the same as, for example, the error list screen P21 (see FIG. 6), and the description thereof is omitted here.

<Step S63>
In step S63, the control unit 11 determines whether or not an operation for issuing the prescription data has been performed. Specifically, the control unit 11 is configured to store the prescription data when a predetermined operation key (not shown) is operated in a state where one or a plurality of prescription data is selected on the prescription data list screen. It is determined that the issuing operation has been performed. Here, if it is determined that the issuing operation has been performed (S63: Yes), the process proceeds to step S631, and if it is determined that the issuing operation has not been performed (S63: No), the process is step. The process proceeds to S64.

<Step S631>
In step S631, the control unit 11 executes a prescription data issuing process (see FIG. 19) to be described later for the prescription data that is the object of the issuing operation. In the prescription data issuance process, dispensing is started for the prescription data, or the dispensing of the prescription data is suspended.

<Step S64>
In step S64, the control unit 11 determines whether an NG issuing operation for the prescription data has been performed. Specifically, the control unit 11 is configured to store the prescription data when a predetermined operation key (not shown) is operated in a state where one or a plurality of prescription data is selected on the prescription data list screen. It is determined that an NG issue operation has been performed. If it is determined that the NG issuing operation has been performed (S64: Yes), the process proceeds to step S65. If it is determined that the issuing operation has not been performed (S64: No), the process is performed. Control goes to step S66.

<Step S65>
In step S65, the control unit 11 executes a process of discarding one or a plurality of the prescription data that is a target of the NG issuing operation. In this case, the dispensing for the prescription data is not executed.

<Step S66>
Thereafter, in step S66, the control unit 11 performs the process when a preset operation end operation such as an operation of closing the prescription data list screen or a logout operation is not performed (No side of S66). Return to step S62. When the operation end operation is performed (Yes in S66), the control unit 11 returns the process to step S61 after executing a pharmacist logout process or the like.

[Prescription data issuance processing]
Next, the prescription data issuing process executed by the control unit 11 will be described with reference to FIG. The prescription data issuance process is an example of a process procedure for realizing the dispensing suspension determination process S5. As described above, the prescription data issuance process is executed as necessary in the prescription reception process (see FIG. 16), the ward side inspection process (see FIG. 17), and the dispensing side inspection process (see FIG. 18). Is done.

<Step S71>
In step S71, the control unit 11 determines, based on the prescription data, whether or not the prescription data is a holding target according to the holding condition set in advance. Here, if it is determined that the prescription data is a hold target (S71: Yes), the process proceeds to step S72, and if it is determined that the prescription data is not a hold target (S71: No), the process is performed. Control goes to step S73.

  The hold condition can be arbitrarily set by the control unit 11 according to a user operation in the initial setting of the server 1 or the like. For example, the holding condition is that the prescription classification of the prescription data is “periodic”, or the prescription data is a subject of the ward side inspection (the ward side inspection information is given to the prescription data) Any one or a combination of the above is satisfied.

<Step S72>
In step S72, the control unit 11 starts a dispensing process for the prescription data. Specifically, the control unit 11 generates dispensing data for dispensing medicine based on the prescription data, and executes processing for storing the data in the shared data folder of the storage unit 12. Thus, each of the dispensing devices 3 acquires the dispensing data from the shared data folder, and executes the dispensing of the medicine based on the dispensing data. It is also conceivable that the dispensing pharmacist manually dispenses a medicine (picking or the like) using the dispensing device 3.

<Step S73>
On the other hand, in step S <b> 73, the control unit 11 stores the prescription data in the storage unit 12 in such a manner that it can be identified that the prescription data is in a pending state before the start of dispensing without starting the dispensing of the prescription data. Thus, the process for holding the prescription data in accordance with the hold condition is executed by the hold processing unit 117.

  Note that, as described above, the dispensing suspension determination process S5 and the tightening management process S6 may be omitted, and the prescription data issued as the dispensing target may be the processing target of the dispensing process S7. In this case, the issuance control processing unit 116 of the control unit 11 omits the steps S71 and S73 in the prescription data issuance processing, and performs the prescription reception processing (see FIG. 16) and the ward side inspection processing (see FIG. 17), and when the prescription data is issued in the dispensing side inspection process (see FIG. 18), it is conceivable to execute step S72.

[Tightening management processing]
Next, the tightening management process executed by the control unit 11 will be described with reference to FIG. The tightening management process is an example of a processing procedure for realizing the tightening management process S6 and the dispensing process S7. The tightening management process is executed when a predetermined tightening management start operation is performed by the dispensing pharmacist using the dispensing room terminal 2A. The tightening management start operation is, for example, a user operation of a tightening management start key (not shown) displayed on the prescription data list screen (not shown) or the menu screen (not shown).

<Step S81>
In step S81, the control unit 11 displays the tightening management screen P8 on which a list of the prescription data held in the state before the start of dispensing is obtained after being acquired from the host system 6. FIG. 31 is a diagram showing an example of the tightening management screen P8. Specifically, among the prescription data stored in the storage unit 12, the control unit 11 displays, on the tightening management screen P8, a list of prescription data suspended in the state before the start of dispensing by the step S73. Let Note that prescription data in which dispensing has already started among the prescription data is not displayed on the closing management screen P8. In the closing management screen P8, the number area A81 for displaying the number of the prescription data on hold for each ward or department, and the details for displaying details of the number of the prescription data displayed in the number area A81. Area A82 is displayed. The number of the prescription data is displayed in units such as a start date of taking, a prescription issuance date, a prescription date, or a prescription date included in the prescription data.

  Here, the control unit 11 displays an area A821 in which the inspection location of each of the prescription data is displayed in the detailed area A82 of the tightening management screen P8. Specifically, in the area A821, “prefect inspection” is displayed when inspection of each of the prescription data is performed on the ward side, and “dispensation inspection” is displayed when inspection is performed on the dispensing room side. In the closing management screen P8, an operation key A83 and an operation key A84 for specifying conditions for narrowing down the prescription data displayed in the number area A81 and the detailed area A82 are displayed. And when the control part 11 has a check mark in the display area of the operation key A83 according to the operation of the operation key A83, the prescription data that has been subject to the dispensing side inspection is stored in the prescription data. The number area A81 and the detailed area A82 are displayed. In addition, the control unit 11, when a check mark is attached to the display area of the operation key A83 according to the operation of the operation key A84, the prescription data that was the subject of the ward side inspection is the The number area A81 and the detailed area A82 are displayed. Thereby, the said dispensing pharmacist can select easily only the prescription data which was the object of the said ward side inspection. This display process is executed by the hold display processing unit 118. The dispensing pharmacist can easily select only the prescription data that was the subject of the dispensing side inspection. Further, when an operation (for example, a double click) operation for selecting any display area of the prescription data displayed in the detailed area A82 of the tightening management screen P8 is performed, the control unit 11 A detail screen P9 for displaying details of the selected prescription data is displayed. FIG. 32 is a diagram showing an example of the detailed screen P9. In the example shown in FIG. 32, the patient ID, patient name, order number, ward, taking date, and prescription content are displayed on the detail screen P9. In addition, in the detailed screen P9, an area A91 for displaying an inspection type such as “ward inspection” or “dispensing inspection” is displayed as in the area A821. Moreover, the said control part 11 displays the identification information (name or ID etc.) of the pharmacist who performed the said ward side inspection or the said dispensing side inspection, and inspection date (issue date) on the said detailed area A82 or the said detailed screen P9. It is possible to make it.

<Step S82>
In step S82, the control unit 11 performs an extraction operation on the tightening management screen to narrow down the prescription data displayed on the tightening management screen to the prescription data that was the subject of the ward side inspection. It is determined whether or not. If it is determined that the extraction operation has been performed (S82: Yes), the process proceeds to step S83. If the extraction operation has not been performed (S82: No), the process proceeds to step S84. .

<Step S83>
In step S <b> 83, the control unit 11 extracts the prescription data that is the subject of the ward side inspection from the prescription data held in a state before the start of dispensing and displays the prescription data on the tightening management screen. Specifically, the said control part 11 extracts the said prescription data to which the said ward side inspection information was provided from the said prescription data withheld in the state before the dispensing start.

<Step S84>
In step S84, the control unit 11 determines whether or not a dispensing start operation for starting dispensing of one or a plurality of the prescription data has been performed on the tightening management screen. If it is determined that the dispensing start operation has been performed (S84: Yes), the process proceeds to step S85. If the dispensing start operation has not been performed (S84: No), the process proceeds to step S82. Return.

<Step S85>
In step S85, the control unit 11 starts the dispensing process for the prescription data. Specifically, the control unit 11 generates dispensing data for dispensing medicine based on the prescription data, and executes processing for storing the data in the shared data folder of the storage unit 12. Thus, each of the dispensing devices 3 acquires the dispensing data from the shared data folder, and executes the dispensing of the medicine based on the dispensing data.

  In particular, when the dispensing start operation is performed in a state where a plurality of prescription data is selected in advance in the tightening management screen, the control unit 11 performs a dispensing process for the plurality of preselected prescription data collectively. Run. This processing is executed by the batch dispensing processing unit 119. Thereby, since the dispensing process can be started collectively for arbitrary prescription data, it is possible to increase the work efficiency of the final audit performed by the pharmacist after the dispensing, for example.

  As described above, in the ward drug operation support system 20, the necessity of the ward side inspection or the dispensing side inspection is automatically determined for the prescription data, and the ward pharmacist or the dispensing pharmacist performs inspection work. Can be automatically distributed and executed. Further, in the ward pharmacist support system 20, the ward pharmacist can efficiently perform an inspection operation using the patient list screen P6 and the patient detail screen P7 having high operability. Business is supported.

  The control unit 11 appropriately combines a part or all of the processes executed in the ward drug business support system 10 according to the first embodiment and the ward drug business support system 20 according to the second embodiment. It is also possible to execute it.

1: Server 11: Control unit 12: Storage unit 13: Communication I / F
14: Operation device 15: Display device 16: Drive device 2: Client terminal 21: Control unit 22: Storage unit 23: Communication I / F
24: Operating device 25: Display device 26: Drive device 3: Dispensing device 4: Printer 5: Communication network 6: Higher system 10: Ward drug operation support system 20: Ward drug operation support system

Claims (22)

An acquisition processing unit for acquiring a check result of a prescription check for determining whether one or more first confirmation items are appropriate for the prescription data;
A display control unit for displaying, for each patient, a first display area for displaying a determination result of one or more of the first confirmation items based on a check result of the prescription check;
With
The display control unit divides a display field corresponding to each of the first confirmation items in the first display area, and displays a first divided area for displaying the priority of confirmation and a second divided area for displaying the presence or absence of confirmation. Ward drug business support system that displays. Whether the acquisition processing unit satisfies the confirmation condition of one or a plurality of second confirmation items predetermined separately from the first confirmation item for one or both of the prescription data and the patient corresponding to the prescription data Get further check results of the condition check to determine whether or not
The display control unit displays, for each patient, a second display area that displays a determination result of one or a plurality of the second confirmation items based on a check result of the condition check, and the second display area includes the second display area. 2. The ward drug business support system according to claim 1, wherein a display field for each of the two confirmation items is divided to display the first divided region and the second divided region.   The first division of the display field corresponding to the first confirmation item determined to be inappropriate by the prescription check and the second confirmation item determined to satisfy the confirmation condition by the condition check The ward drug business support system according to claim 2, wherein priority of confirmation and presence / absence of confirmation are displayed only in the region and the second divided region.   The ward drug business support system according to claim 2 or 3, wherein the display control unit displays the first divided area in a display mode predetermined according to the priority. Including one or a plurality of first client terminals having an operation unit for receiving a confirmation operation of the first confirmation item and the second confirmation item;
5. The display control unit according to claim 2, wherein the display control unit displays that the first confirmation item and the second confirmation item have been confirmed in the second divided region according to the confirmation operation on the operation unit. Ward drug operation support system described in 1.   The ward drug business support system according to claim 5, wherein the first client terminal is a terminal operated by a ward pharmacist who performs business in a ward in which a patient is hospitalized. Comprising one or a plurality of second client terminals operated by a dispensing pharmacist performing business in a dispensing room where dispensing work based on the prescription data is performed;
The ward medicine service according to claim 5 or 6, wherein the display control unit displays on the second client terminal whether or not the first confirmation item and the second confirmation item are confirmed by the first client terminal. Support system.   The said display control part displays the said 1st division area of the said 1st confirmation item and the said 2nd confirmation item with which the said confirmation operation was performed by the display aspect predetermined according to confirmed. The ward drug business support system according to any one of 7 above.   The display control unit displays a display mode of the first divided area of the first confirmation item and the second confirmation item, a pharmacist who performed the confirmation operation of the first confirmation item and the second confirmation item, and another The ward drug duties support system according to claim 8 changed between pharmacists. An information storage unit for storing a processing time required for confirmation of each item included in the first confirmation item and the second confirmation item and a scheduled work time corresponding to each ward pharmacist;
A schedule creation processing unit for creating a confirmation schedule for each of the first confirmation item and the second confirmation item for each ward pharmacist based on the processing time and the scheduled work time;
A ward drug business support system according to any one of claims 2 to 9. In the information storage unit, processing capacity for each ward pharmacist of each item included in the first confirmation item and the second confirmation item is stored,
The ward drug business support system according to claim 10, wherein the schedule creation processing unit creates the confirmation schedule for each ward pharmacist based on the processing capability, the processing time, and the scheduled work time.   The schedule creation processing unit calculates an individual processing time corresponding to each ward pharmacist based on the processing time and the processing capacity, and creates the confirmation schedule based on the individual processing time and the scheduled work time. Item 13. A ward drug business support system according to Item 11.   The ward drug business support according to any one of claims 2 to 12, further comprising a setting processing unit capable of arbitrarily setting a determination condition for determining whether each of the first confirmation item and the second confirmation item is necessary according to an operation input. system.   The ward drug business support system according to claim 13, wherein the setting processing unit is capable of adding and deleting items included in one or both of the first confirmation item and the second confirmation item. Check result of prescription check for determining whether one or a plurality of first check items for prescription data is appropriate, and the first check for one or both of the prescription data and the patient corresponding to the prescription data An acquisition processing unit for acquiring a check result of a condition check for determining whether or not a confirmation condition of one or a plurality of second confirmation items set in advance separately from the item is satisfied;
An information storage unit for storing a processing time required for confirmation of each item included in the first confirmation item and the second confirmation item and a scheduled work time corresponding to each ward pharmacist;
A schedule creation processing unit for creating a confirmation schedule for each of the first confirmation item and the second confirmation item for each ward pharmacist based on the processing time and the scheduled work time;
Ward drug business support system equipped with. Based on prescription data and predetermined ward inspection conditions, an inspection determination processing unit that determines whether or not an inspection by a ward pharmacist performing work in a ward where a patient is hospitalized is necessary,
An issuance control processing unit that issues the dispensing data when the issuance operation by the ward pharmacist is performed by the ward pharmacist when the prescription data determined to be inspected by the ward pharmacist by the inspection determination processing unit;
Ward drug business support system equipped with.   The ward inspection condition is that the prescription category of the prescription data is a predetermined category, the inpatient ward of the patient corresponding to the prescription data is a predetermined ward, and the patient corresponding to the prescription data The clinical department is a predetermined clinical department, the patient corresponding to the prescription data is a predetermined patient, the patient's disease corresponding to the prescription data is a predetermined disease, and The ward drug business support system according to claim 16, wherein any one or a plurality of combinations of a predetermined drug included in the prescription data is satisfied. Further comprising an acquisition processing unit for acquiring a check result of a prescription check for determining whether or not the prescription data is appropriate;
The ward inspection condition is that a predetermined error is included in the check result, a prescription category of the prescription data is a predetermined category, and an inpatient ward of a patient corresponding to the prescription data is predetermined. Corresponding to the prescription data, that the patient's department corresponding to the prescription data is a predetermined department, the patient corresponding to the prescription data is a predetermined patient, The ward drug according to claim 16, wherein any one or a combination of a patient's disease is a predetermined disease and a predetermined drug is included in the prescription data is satisfied. Business support system.   The said issue control processing part can issue collectively the said some prescription data determined that the inspection by the said ward pharmacist is required by the said inspection determination process part. Ward drug business support system. A holding processing unit for holding the prescription data issued by the issuing control processing unit in a state before starting dispensing according to a predetermined holding condition;
When the prescription data held by the hold processing unit is displayed as a list, a hold display processing unit that displays whether each of the prescription data was subject to inspection by the ward pharmacist,
The ward drug business support system according to any one of claims 16 to 19, further comprising:   21. The ward drug business support system according to claim 20, further comprising a batch dispensing processing unit that collectively starts dispensing processing for a plurality of preselected preselected data among the prescription data held by the holding processing unit.   The issuance of the prescription data by the issuance control processing unit is a process for causing a dispensing device used for dispensing a medicine to start dispensing based on the prescription data. Support system.