Information processing method, computer program, and information processing system

The information processing method and system streamline medication dispensing by enabling remote auditing and secure drug delivery, addressing inefficiencies and improving pharmacist and patient outcomes.

JP2025071595AInactive Publication Date: 2025-05-08TSUBAKIMOTO CHAIN CO
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2023181896
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-10-23
Publication Date
2025-05-08
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Existing systems for dispensing medications lack efficiency and accuracy, placing a heavy burden on pharmacists and not fully leveraging technology to improve patient health and employment environments.

Method used

An information processing method and system that acquires prescription data, images of picked drugs, and patient attributes, and facilitates remote auditing by external pharmacists, enabling automated data transmission, audit result analysis, and secure drug delivery mechanisms.

Benefits of technology

This solution enhances the accuracy and speed of medication dispensing, reduces pharmacist workload, improves patient health outcomes, and optimizes the employment environment for medical and pharmaceutical services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025071595000001_ABST
    Figure 2025071595000001_ABST
Patent Text Reader

Abstract

To provide an information processing method, a computer program, and an information processing system that contribute to improvement of health of a patient, a medical service provider, and a pharmacist as a whole and an employment environment.SOLUTION: A computer executes processing of: acquiring prescription data including identification data of a patient and a prescription for the patient; acquiring an image obtained by imaging medicine picked based on the prescription data; acquiring attribute data of the patient obtained from the identification data of the patient included in the prescription data; outputting an audit request based on the acquired prescription data, the image, and the attribute data; transmitting the prescription data, the image, and the attribute data to an auditor according to the audit request; receiving audit results from the auditor; and outputting whether or not the medicine can be received / delivered from / to the patient based on the audit results.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an information processing method, a computer program, and an information processing system. [Background technology]

[0002] Proposals have been made using image analysis technology and robot technology to automatically package medicines and to confirm whether prescribed medicines are as prescribed. Patent Document 1 proposes a device that takes an image of packaged medicines, compares the taken image with a master image, and automatically judges whether the medicines are as prescribed, so that pharmacies can accurately and quickly prescribe medicines to patients based on prescriptions and reduce the burden on pharmacists. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2017-192651 A Summary of the Invention [Problem to be solved by the invention]

[0004] It is expected that not only will it reduce the burden on pharmacists by improving the accuracy and speed of prescriptions, but it will also level out the time and space of their busy schedules, optimizing the content of their work. Where possible, it is necessary to use picking robots based on image analysis technology and robotics technology to narrow down tasks that pharmacists themselves should perform, such as interpersonal tasks, while contributing to improving the health and employment environment of patients, medical businesses, and pharmacists as a whole in relation to the provision of medicines to patients.

[0005] There are also hopes for technology that will enable the safe operation of a dispensing consignment system, where regional dispensing centers that receive drugs from pharmaceutical companies can receive drugs correctly from dispensing pharmacies and then deliver them to patients correctly, without the need to distribute the drugs to each pharmacy.

[0006] The present invention aims to provide an information processing method, a computer program, and an information processing system that contribute to improving the health of patients and the employment environment of businesses involved in dispensing, including medical businesses, pharmacists, and drug businesses. [Means for solving the problem]

[0007] In an information processing method of one embodiment of the present disclosure, a computer executes a process of acquiring prescription data including a patient's identification data and a prescription for the patient, acquiring images of medication picked based on the prescription data, acquiring attribute data of the patient obtained from the patient's identification data included in the prescription data, outputting an audit request based on the acquired prescription data, image, and attribute data, transmitting the prescription data, image, and attribute data to an auditor who responds to the audit request, accepting an audit result from the auditor, and outputting whether or not the medication can be handed over to the patient based on the audit result.

[0008] In the information processing method disclosed herein, the work of auditing the pharmacy can be outsourced to an external pharmacist who is capable of the work. The pharmacist stationed at the pharmacy can leave the picking to a picking staff member or an automatic picking device, and can secure time to explain the medicine to the patient when providing the medicine.

[0009] In an information processing method according to an embodiment of the present disclosure, the computer may execute a process of outputting data for inquiry into a doubt if the audit results received from the auditor include doubts.

[0010] In the information processing method disclosed herein, if an external pharmacist has doubts about a prescribed drug, the information can be automatically output to the pharmacy where the drug was picked. It is also possible to automatically output a question inquiry to the drug's issuer, which is expected to improve the accuracy of prescriptions.

[0011] In an information processing method according to an embodiment of the present disclosure, the computer may execute a process of storing the prescription data, images, and attribute data, as well as audit results for an audit request based on the prescription data, images, and attribute data, sorted according to whether or not there is any doubt about the audit results.

[0012] In the information processing method disclosed herein, prescription data issued by a medical institution, images of medicines picked based on the prescription, and audit results of audit requests are stored together with whether or not there are any doubts. The pharmacist's determination of whether or not there are any doubts is stored in association with the prescription data, making it possible to analyze it later.

[0013] In an information processing method of one embodiment of the present disclosure, the computer may execute a process of storing at least one of audio data, video data, and operation data related to communication between the pharmacist and the patient when the medication is handed over, in correspondence with the prescription data.

[0014] In the information processing method of the present disclosure, data on the communication between the pharmacist and the patient when the drug prescribed based on the prescription data is handed over is stored in association with the prescription data. The fact that communication took place when the drug was prescribed is stored and can be referenced later.

[0015] In an information processing method according to one embodiment of the present disclosure, the computer may execute a process of deriving data indicating a correspondence between at least one parameter of gender, age, medical history, and medication history contained in the attribute data and the prescription contents stored as questionable, based on the stored prescription data, image, and attribute data, and outputting the derived data.

[0016] In the information processing method disclosed herein, prescription data, attributes, and the presence or absence of doubts are stored in correspondence with each other, so that the correspondence between prescription contents judged to be questionable and patient attributes (proportion of doubts by attribute, correlation, etc.) can be derived after the fact.

[0017] In an information processing method according to an embodiment of the present disclosure, the computer may acquire data on the effects of a drug prescribed based on the prescription data on a patient, store the acquired data on the effects in association with the prescription data, and, upon acquiring new prescription data, calculate a suitability index for the drug included in the prescription data based on attribute data of the patient included in the new prescription data, and execute a process of outputting the suitability index together with the prescription data, image, and attribute data to an auditor responding to the audit request.

[0018] In the information processing method disclosed herein, data on the effect of a drug prescribed based on prescription data on a patient is collected in association with the prescription data. This makes it possible to analyze whether the prescribed drug was appropriate for a patient with that attribute. For a specific attribute, information that the drug is not effective can be fed back, which is expected to lead to the optimization of subsequent prescriptions.

[0019] In an information processing method according to one embodiment of the present disclosure, when the calculated numerical value indicating the suitability index is equal to or less than a predetermined value, the computer may execute a process of outputting data for inquiries regarding the prescription data, with the suitability index attached.

[0020] In the information processing method disclosed herein, if the index value showing the effectiveness of a drug by patient attribute is significantly low, it is possible to automatically output that there is a doubt about the drug at the pharmacy. It is also possible to automatically output a doubt inquiry to the drug's manufacturer, which is expected to improve the optimization of prescriptions.

[0021] In an information processing method according to one embodiment of the present disclosure, the computer may connect to a lock control unit of a locked storage unit that contains the medication picked based on the prescription data, and if the audit result corresponding to the audit request for the prescription data is available for delivery and the authentication result based on the patient identification data included in the prescription data is successful, the computer may execute a process of outputting an unlock signal to the lock control unit.

[0022] In the information processing method disclosed herein, whether or not a drug can be handed over to a patient or a patient's drug manager can be mechanically controlled using a locked container. Even when a pharmacist is not present at the pharmacy, the drug can be handed over based on the audit results from an external pharmacist.

[0023] In an information processing method of one embodiment of the present disclosure, a computer executes processes to acquire prescription data including a patient identification data and a prescription for the patient, acquire from the pharmacy outsourcing party an image of a drug picked at the pharmacy outsourcing party based on the prescription data, acquire attribute data of the patient obtained from the patient identification data included in the prescription data, output an audit request based on the acquired prescription data, image, and attribute data, transmit the prescription data, image, and attribute data to an auditor in response to the audit request, accept an audit result from the auditor, and output to the pharmacy outsourcing party a decision as to whether or not the drug can be shipped to the patient based on the audit result.

[0024] In the information processing method disclosed herein, the auditing work can be outsourced to a remote pharmacist. Since it is possible for the regional dispensing centers that receive drugs from pharmaceutical companies to remotely audit drugs, it is possible to realize a dispensing outsourcing system in which drug picking and delivery to patients are centrally performed.

[0025] A computer program according to one embodiment of the present disclosure causes a computer to execute processes to acquire prescription data including a patient's identification data and a prescription for the patient, acquire images of medication picked based on the prescription data, acquire attribute data of the patient obtained from the patient's identification data included in the prescription data, output an audit request based on the acquired prescription data, images, and attribute data, transmit the prescription data, images, and attribute data to an auditor who responds to the audit request, accept an audit result from the auditor, and output whether or not the medication can be handed over to the patient based on the audit result.

[0026] In an information processing system of one embodiment of the present disclosure, a first device acquires images captured by an imaging device that captures the picking results of drugs to be used in a pharmacy, acquires prescription data including a patient's identification data and a prescription for the patient from a medical institution, acquires images of the drugs picked based on the prescription data from the imaging device, acquires attribute data of the patient obtained from the patient's identification data included in the prescription data, and transmits an audit request based on the acquired prescription data, images, and attribute data to a second device, and the second device accepts a response from an auditor's third device each time it acquires the audit request from the second device, transmits the prescription data, images, and attribute data to the auditor who responded to the audit request, accepts audit results from the auditor, and transmits the audit results and whether or not the drugs can be handed over to the patient based on the audit results to the first device. Effect of the Invention

[0027] This disclosure contributes to improving the health of patients and the employment environment for pharmacists and pharmaceutical business operators. It also makes it possible to remotely conduct audits and medication instructions when outsourcing dispensing to improve the efficiency of dispensing operations. [Brief description of the drawings]

[0028] [Figure 1] FIG. 1 is a schematic diagram of a pharmacy information processing system. [Diagram 2] FIG. 2 is a block diagram showing a configuration of a first device. [Diagram 3] FIG. 2 is a schematic perspective view of an inspection support device. [Figure 4] 1 is a block diagram showing a configuration of an audit support device. [Diagram 5] FIG. 2 is a diagram showing an example of the contents of a prescription history stored in the first device. [Figure 6] FIG. 2 is a block diagram showing a configuration of a second device. [Figure 7] FIG. 13 is a block diagram showing a configuration of a third device. [Figure 8]11 is a flowchart showing an example of a processing procedure from prescription issuance to drug delivery in a pharmacy information processing system. [Figure 9] 11 is a flowchart showing an example of a processing procedure from prescription issuance to drug delivery in a pharmacy information processing system. [Figure 10] 13 is a flowchart showing an example of a processing procedure from prescription issuance to drug delivery in a pharmacy information processing system. [Figure 11] FIG. 13 is a diagram showing an example of an inspection screen displayed on the third device. [Figure 12] FIG. 13 is a diagram showing another example of the inspection screen displayed on the third device. [Figure 13] FIG. 11 is a schematic diagram of a pharmacy information processing system according to a second embodiment. [Figure 14] FIG. 13 is a block diagram showing the configuration of a delivery locker. [Figure 15] 13 is a flowchart showing an example of a process at the time of delivery in the pharmacy information processing system of the second embodiment. [Figure 16] 13 is a flowchart showing an example of a process at the time of delivery in the pharmacy information processing system of the second embodiment. [Figure 17] 13 is a flowchart showing an example of a process at the time of delivery in the pharmacy information processing system of the second embodiment. [Figure 18] FIG. 11 is a diagram showing an example of the contents of a prescription history stored in the first device of the second embodiment. [Figure 19] 13 is a flowchart showing an example of an analysis process procedure executed by a second device in the pharmacy information processing system of the third embodiment. [Figure 20] 13 is a flowchart showing an example of a processing procedure of a second device in the pharmacy information processing system of the third embodiment. [Figure 21] FIG. 13 is a schematic diagram of a pharmacy information processing system according to a fourth embodiment. [Figure 22] 13 is a flowchart showing an example of a processing procedure executed by a second device of the pharmacy information processing system of the fourth embodiment. [Figure 23]13 is a flowchart showing an example of a processing procedure executed by a second device of the pharmacy information processing system of the fourth embodiment. [Figure 24] 13 is a flowchart showing an example of a processing procedure of a second device in the pharmacy information processing system of the fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0029] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present disclosure will be specifically described with reference to the drawings showing embodiments thereof. In the following embodiments, a pharmacy information processing system to which the information processing method of the present disclosure is applied will be described.

[0030] (First embodiment) FIG. 1 is a schematic diagram of a pharmacy information processing system 100. The pharmacy information processing system 100 is installed in a pharmacy and includes a first device 1 that manages information processing in the pharmacy, a second device 2 that receives prescription data, and a third device 3 that is used by a pharmacist. The first device 1, the second device 2, and the third device 3 can transmit and receive data to each other via a network N with the second device 2 as a hub. The pharmacy information processing system 100 may use one or more first devices 1 at a dispensing contractor that receives drugs from a pharmaceutical company, dispenses drugs in a centralized manner for each area, and ships the dispensed drugs to patients, instead of at a pharmacy.

[0031] The network N includes a public communication network N1, which is the so-called Internet, a carrier network N2, and each local network N3. The network N may include a dedicated line between the second device 2 that handles prescription data and a medical institution. The local network N3 is a wired and / or wireless network installed in each pharmacy or home.

[0032] When a patient is prescribed medicine at a medical institution, the patient goes to a pharmacy inside or outside the hospital to pick up the prescribed medicine. The patient may request that the medicine be shipped. At the medical institution, for example, an electronic medical record system creates prescription data indicating the contents of the prescription issued by the doctor. The prescription data includes a patient ID for individually identifying the patient and a medicine ID for specifying the prescribed medicine. The patient ID may be data for identifying the patient issued by the pharmacy information processing system 100, or may be an insurer number, a My Number, a citizen ID, etc. The second device 2 is capable of communicating with a device that stores prescription data at the medical institution, and can acquire the prescription data.

[0033] When a patient visits the pharmacy, the first device 1 accepts the patient ID and obtains prescription data for the patient identified by the patient ID from the second device 2. When the dispensing contractor accepts a request to arrange prescription drugs from a patient in its area along with the patient ID, it similarly obtains the prescription data from the second device 2. The first device 1 outputs the contents of the drugs to be prescribed based on the acquired prescription data via a monitor, printer, or communication. A pharmacist, picking operator, or picking device who understands the output contents of the drugs to be prescribed picks the drugs to be prescribed from a group of drugs stocked in the pharmacy and places them in a designated container such as a tray or bag.

[0034] An inspection support device 4 is installed in the pharmacy or the dispensing contractor. The inspection support device 4 is connected to the first device 1 via a local network N3 or a signal line installed in the pharmacy or the dispensing contractor. The inspection support device 4 includes a camera and a lighting device, and transmits to the first device 1 an image of the medicine contained in the container and data for identifying the prescription data linked to the imaged subject (patient ID, prescription ID, etc.).

[0035] When the first device 1 obtains captured images of the medicine picked based on the prescription data from the inspection support device 4, it outputs the corresponding prescription data and patient data obtained from the patient ID included in the prescription data as an inspection request to the second device 2. The inspection request is issued from the second device 2, and an available pharmacist, including a pharmacist stationed at the pharmacy that prescribes the medicine, responds to the inspection request using the third device 3. The pharmacist checks the captured images, prescription data, and patient data included in the inspection request on the third device 3, inspects whether the medicine has been prescribed according to the prescription and is appropriate for the patient and his / her medical condition, and transmits the inspection results to the first device 1.

[0036] The first device 1, which has acquired the audit results, allows the drug to be handed over to the patient if the audit results are acceptable. If handing over of the drug is permitted, staff from the pharmacy or the dispensing contractor, or a resident pharmacist, communicates with the patient based on the audit results, such as explaining the prescribed drug, and hands over the drug to the patient. At the dispensing contractor, communication may be carried out online, as described below, and the drug may be shipped to the patient or pharmacy. If the drug is unacceptable, an inquiry is sent to the medical institution via the second device 2, and the second device 2 supports a second consultation between the doctor and pharmacist regarding the prescription data.

[0037] The pharmacy information processing system 100 allows an external pharmacist to perform the work of auditing a pharmacy. This allows a pharmacist stationed at a pharmacy to leave picking to a picking staff member and delegate auditing to others during busy times, thereby securing time to explain to patients when providing them with medicine. It is expected that the pharmacist will be able to focus on the interpersonal work unique to pharmacists, such as explaining to patients, and feel rewarded. Since the audit can be requested online from a pharmacist stationed at another pharmacy, it is possible to shorten the waiting time for patients even if the pharmacy is short of staff during busy periods. The shortened waiting time is not only beneficial to patients, but also brings the benefit of reducing the burden on pharmacists and pharmacy staff. Since the audit can be requested online from a pharmacist stationed at another pharmacy, it is possible to level out the peaks in the provision of medicines over time or at certain times, reducing the burden on staff and pharmacists at the pharmacy, and it is expected that the geographical difference between other pharmacies that are far away and empty can be leveled out. The pharmacy information processing system 100 makes it possible to remotely perform audits and medication instructions in dispensing consignments to improve the efficiency of dispensing operations. Since audit work can be performed remotely, medical safety in dispensing consignments can be guaranteed. With the pharmacy information processing system 100, picking and shipping are performed by the dispensing consignee, so pharmacists only need to perform person-to-person tasks such as medication instructions without performing object-related tasks, improving the efficiency of dispensing.

[0038] The configuration and processing of each device that realizes the above-mentioned pharmacy information processing system 100 will be described in detail below.

[0039] 2 is a block diagram showing the configuration of the first device 1. As described above, the first device 1 is installed in each pharmacy and controls information processing in the pharmacy and information processing of dispensing at the dispensing contractor. The first device 1 is a computer such as a server computer or a personal computer.

[0040] The first device 1 includes a processing unit 10, a storage unit 11, a first communication unit 12, a second communication unit 13, a display unit 14, and an operation unit 15.

[0041] The processing unit 10 is a processor using a CPU (Central Processing Unit) and / or a GPU (Graphics Processing Unit). The processing unit 10 uses built-in memories such as a ROM (Read Only Memory) and a RAM (Random Access Memory) to control each component and execute processing. The processing unit 10 may be configured as a single piece of hardware (SoC: System On a Chip) that integrates a processor, memory, communication devices, etc. The processing unit 10 exchanges data with the audit support device 4, the second device 2, and the third device 3 based on a program stored in the storage unit 11, and outputs information to the display unit 14.

[0042] The storage unit 11 uses a non-volatile storage medium such as an SSD (Solid State Drive) or a hard disk, and stores programs and data referenced by the processing unit 10. The storage unit 11 stores a first program (program product) P1. The first program P1 stored in the storage unit 11 may be a program that the processing unit 10 reads out, copies, and installs a first program P9 stored in a storage medium 9. The first program P1 may be a program that the processing unit 10 downloads from a program server (not shown), stores in the storage unit 11, and installs.

[0043] The first communication unit 12 is a communication device that realizes communication with the second device 2 via the network N. The first communication unit 12 uses a network card for wired communication, a wireless communication device for carrier communication, or a wireless LAN device. The first communication unit 12 can be communicatively connected to the network N via a local network N3 installed in the pharmacy. The processing unit 10 can be communicatively connected to the second device 2 via the network N by the first communication unit 12. The processing unit 10 can also be communicatively connected to a printing device connected to the local network N3 by the first communication unit 12.

[0044] The second communication unit 13 is a communication device that realizes data transmission and reception with the audit support device 4 via a communication line or a signal line. The second communication unit 13 is a communication device that conforms to a serial communication protocol. For example, the second communication unit 13 is a communication device compatible with RS232.

[0045] The display unit 14 uses a display such as a liquid crystal display or an organic EL (Electro Luminescence) display. The display unit 14 displays information such as the audit results by processing based on the first program P1 of the processing unit 10. The display unit 14 may be a display with a built-in touch panel or a display without a built-in touch panel.

[0046] The operation unit 15 is a user interface such as a keyboard and a pointing device capable of inputting and outputting data to and from the processing unit 10, or a voice input unit. The operation unit 15 may use a touch panel of the display unit 14, or physical buttons provided on the housing. The operation unit 15 may recognize instructions from voice using a voice input unit. The operation unit 15 notifies the processing unit 10 of operation information.

[0047] Display unit 14 and operation unit 15 are not essential, and third device 3, which will be described later, may function as a device that outputs the results of processing by first device 1.

[0048] FIG. 3 is a schematic perspective view of the inspection support device 4, and FIG. 4 is a block diagram showing the configuration of the inspection support device 4. As shown in FIG. 3, the inspection support device 4 includes a placement table 42 on which a tray is placed and an illumination device 43 for illuminating the top of the placement table 42, in a box body 41 having a hollow interior. At least a part of the placement table 42 is made of transparent or semi-transparent resin, and transmits the light irradiated from the illumination device 43 placed below. The tray T is also made of transparent or semi-transparent resin, and further transmits the light that has passed through the placement table 42, and irradiates the medicine placed on the tray T from below. The illumination device 43 is provided so as to irradiate light diagonally downward from a corner of the top surface of the box body 41, and illuminates the medicine placed on the tray T. A camera 44 is provided facing downward at approximately the center of the inside of the top surface of the box body 41, and includes the medicine placed on the tray T in its imaging range.

[0049] The camera 44 is connected to the control unit 40. The control unit 40 uses a programmable logic controller. The control unit 40 uses a microcontroller and a communication unit for serial communication, and executes the control described below based on a control program stored in a built-in memory, and transmits an image captured by the camera 44 from the communication unit to the first device 1.

[0050] The control unit 40 of the inspection support device 4 outputs image data of the captured image in association with the prescription ID of the prescription data on which the drug in the captured image is based. The association may be achieved by capturing an image of the drug placed on the tray T together with a paper medium on which the prescription ID is printed. The association may be achieved by the control unit 40 acquiring an identification number of the tray T separately attached to the tray T by capturing an image of the tray T or by reading the identification number from a tag by short-range wireless communication, and outputting the identification number of the tray T together with the captured image to the first device 1. The identification number of the tray T and the prescription ID are associated by the first device 1 when a picking instruction is issued, and the association is possible if the first device 1 can acquire the identification number of the tray T and the captured image and acquire the corresponding prescription ID.

[0051] The first device 1 associates the image data of the captured image transmitted from the inspection support device 4 with the prescription ID, and stores the image data and the prescription ID in the storage unit 11 as a prescription history at the pharmacy in association with time information. FIG. 5 is a diagram showing an example of the contents of the prescription history stored in the first device 1. As shown in FIG. 5, the prescription history is data in which the prescription ID, the patient ID, the drug ID, the image data, the inspection result, and whether or not the prescription has been delivered are associated with each other. In FIG. 5, for example, the patient ID "123456789012" of the patient for whom the issued prescription is issued is associated with the prescription ID "23080100012345". In the prescription history stored in the first device 1, the contents of the prescription data, at least the drug ID "876543210123" and the number are stored in association with the prescription ID, and the drug ID and information such as the drug name, manufacturer name, and package insert stored separately in an external server or in the storage unit 11 can be collated. For the prescription ID "00012345," it is stored that image data has not been obtained, an audit has not been conducted, and the prescription has not yet been handed over to the patient.

[0052] In Figure 5, the past prescription history shows that the same drug was prescribed to a patient with the same patient ID "123456789012." Image data acquired in the past prescription, audit results, and data recording explanations from the pharmacist at the time of delivery are stored in association with each other. Data recording explanations from the pharmacist is data recording communication between the pharmacist and the patient regarding the drug.

[0053] 5 shows that the history of different prescriptions for other patients is also stored. For example, in association with the prescription ID "23080100006982," the patient ID "123876456789," the medicine ID, image data of the picked medicine, the audit result (OK), and explanation data at the time of delivery are stored. The explanation data may be document data including images and text used at the time of explanation, audio data at the time of explanation, recorded video data, or operation data indicating that an explanation was given by the pharmacist or the patient.

[0054] The processing unit 10 of the first device 1 stores a prescription history as shown in Fig. 5 in the storage unit 11, and can determine (audit) whether the prescription data matches the medicine shown in the captured image of the picked medicine. The processing unit 10 can link the captured image of the actually picked medicine with the prescription ID of the prescription for the captured medicine, and record it as data. The processing unit 10 can obtain data on medicines prescribed for the target patient from other pharmacies or hospitals and medicines prescribed in the past, from the patient ID included in the prescription data, via the second device 2. Details of the processing by the processing unit 10 will be described later.

[0055] 6 is a block diagram showing the configuration of the second device 2. In the following description, the second device 2 will be described as a single server computer, but may be configured to be distributed among multiple computers according to processing content, function, etc. The second device 2 includes a processing unit 20, a storage unit 21, and a communication unit 22.

[0056] The processing unit 20 is a processor using a CPU and / or a GPU. The processing unit 20 uses built-in memories such as a ROM and a RAM to control each component and execute processing. The processing unit 20 may be configured as a single piece of hardware (SoC: System On a Chip) that integrates a processor, a memory, and a communication unit 22 described later. The processing unit 20 executes processing described later based on a program stored in the storage unit 21.

[0057] The storage unit 21 uses a non-volatile storage medium such as an SSD or a hard disk, and stores programs and data referenced by the processing unit 20. The storage unit 21 stores a second program (program product) P2. The second program P2 stored in the storage unit 21 may be obtained by the processing unit 20 reading out the second program P8 stored in the storage medium 8, duplicating it, and installing it. The second program P2 may be obtained by the second device 2 downloading it from a program server (not shown), storing it in the storage unit 21, and installing it.

[0058] A prescription data database (hereinafter, prescription DB) 211 is constructed in the storage unit 21. The prescription DB 211 stores prescription data acquired by the second device 2. The prescription DB 211 may be a part of an external prescription management service. The storage unit 21 stores patient attribute data (gender, age, medical history) in association with a patient ID. The patient attribute data corresponding to the patient ID may be acquired from an externally stored data. Although not described in detail in the following description of the processing procedure, when recording data in the prescription DB 211 or when transferring data to and from an external prescription management service, the authenticity is authenticated using an electronic signature or the like.

[0059] The communication unit 22 is a communication device that realizes communication via the network N. The communication unit 22 is, for example, a network card compatible with the network N. The communication unit 22 may realize wireless communication. The processing unit 20 can acquire prescription data from a medical institution's system or an external prescription management service via the communication unit 22. The processing unit 20 functions as a Web server via the communication unit 22 and can accept access from a medical institution, an access from the first device 1, and an access from the third device 3. The processing unit 20 can exchange data with the first device 1 via the communication unit 22. The processing unit 20 can exchange data with the third device 3 via the communication unit 22.

[0060] The second device 2 thus configured directly receives prescription data issued by a medical institution and accumulates the received prescription data in the prescription DB 211. The second device 2 may be a device that acquires prescription data via an external prescription management service that acquires prescription data from a medical institution and registers the results of prescription in the prescription management service. The second device 2 transmits and receives data to and receives data from the first device 1 and the third device 3 in the pharmacy information processing system 100, and performs a process of recording prescription history and functions as a hub to perform a process of auditing the prescription of medicines based on a prescription between different pharmacies or at a dispensing contractor. The process by the second device 2 will be described in detail later.

[0061] 7 is a block diagram showing the configuration of the third device 3. The third device 3 used by a pharmacist is a laptop or desktop personal computer. The third device 3 may also be a smartphone or a tablet terminal.

[0062] The third device 3 includes a processing unit 30, a storage unit 31, a communication unit 32, a display unit 33, an operation unit , an audio input / output unit 35, and a camera .

[0063] The processing unit 30 is a processor using a CPU and / or a GPU. The processing unit 30 uses built-in memories such as ROM and RAM to control each component and execute processing. The processing unit 30 may be configured as a single piece of hardware (SoC) that integrates a processor, memory, and a communication unit 32 described below. The processing unit 30 transmits and receives data to and from the second device 2 based on a program stored in the storage unit 31, and accepts operations from a pharmacist. Details will be described later.

[0064] The storage unit 31 uses a non-volatile memory such as a hard disk, a flash memory, or an SSD. The storage unit 31 stores programs and data referenced by the processing unit 30. The storage unit 31 stores a third program (program product) P3. The third program P3 is a Web browser program and may be a Web application program provided by the second device 2. The third program P3 may be an agent program incorporated in a Web browser. The third program P3 stored in the storage unit 31 may be read out by the processing unit 30 from the third program P7 stored in the storage medium 7, copied, and installed. The third program P3 may be downloaded by the third device 3 from a program server (not shown), stored in the storage unit 31, and installed.

[0065] The communication unit 32 is a communication device that realizes communication via the network N. The communication unit 32 is, for example, a network card compatible with the network N. The communication unit 32 may realize wireless communication. The processing unit 30 can transmit and receive data to and from the second device 2 via the communication unit 32.

[0066] The display unit 33 is a display such as a liquid crystal display, an organic EL (Electro Luminescence) display, etc. The display unit 33 displays a GUI (Graphical User Interface) based on the third program P3.

[0067] The operation unit 34 is a user interface such as a keyboard and a mouse capable of inputting and outputting data to and from the processing unit 30. The operation unit 34 may be a touch panel built into the display unit 33. The operation unit 34 may be a physical button, or the operation unit 34 may be a voice input / output unit 35 including a microphone.

[0068] The audio input / output unit 35 uses a speaker and a microphone. The audio input / output unit 35 outputs audio based on the audio signal output from the processing unit 30. The audio input / output unit 35 outputs the input audio signal to the processing unit 30. The processing unit 30 can perform A / D conversion of the input audio signal to create audio data.

[0069] A visible light camera is used as the camera 36. The camera 36 captures an image of the pharmacist using the third device 3. The processing unit 30 can acquire a monitor image signal being captured by the camera 36.

[0070] The first device 1, second device 2, third device 3, and inspection support device 4 configured in this manner send and receive data between each other, and the pharmacy information processing system 100 audits the results of drug picking based on prescription data and records prescription history.

[0071] 8 to 10 are flowcharts showing an example of a processing procedure from prescription issuance to drug delivery in the pharmacy information processing system 100. In FIG.

[0072] The first device 1 accepts a prescription request from a patient (step S101). In a first example, the prescription request is accepted by accepting a patient's visit at a pharmacy, a pharmacy staff member receives the prescription, and inputs a patient ID. In a second example, the pharmacy accepts a patient's visit, the patient registers the prescription ID and the patient ID, and the first device 1 accepts this. The operation unit 15 of the first device 1 may accept it, or it may be acquired by short-range wireless communication with an information terminal such as a smartphone of the patient. In a third example, a drug delivery request to the pharmacy is accepted together with the prescription ID and the patient ID by remote communication from an information terminal such as a smartphone of the patient. In a fourth example, the pharmacy accepts a patient's visit, the patient registers the prescription ID and the patient ID, and the pharmacy transmits the prescription ID and the patient to a dispensing contractor, and the first device 1 of the dispensing contractor accepts this. In a fifth example, a drug delivery request to a dispensing contractor may be accepted together with the prescription ID and the patient ID by communication from an information terminal such as a smartphone of the patient. The drug delivery request in the third or fourth example from an information terminal such as a patient's smartphone, or the drug shipping request in the fifth example may be received from the second device 2, a web page provided by the pharmacy service, a My Number Portal app, or a medicine notebook app. Various methods other than the first to fourth examples may be considered as a method of acquiring the prescription ID and the patient ID.

[0073] The processing unit 10 of the first device 1 transmits a prescription data reference request including a prescription ID and a patient ID corresponding to the accepted prescription request to the second device 2 (step S102). In step S102, the processing unit 10 adds identification data (pharmacy ID) for identifying the pharmacy (contracted drug dispensing provider) to the reference request and transmits it.

[0074] When the processing unit 20 of the second device 2 receives a prescription data reference request (step S201), it acquires prescription data based on the prescription ID and the patient ID of the patient for whom the prescription is to be prescribed, included in the reference request (step S202). The prescription data acquired in step S202 includes drug identification data for identifying the prescribed drug, the prescription amount, the patient ID of the patient for whom the prescription is to be prescribed, and information for identifying the medical institution and doctor who prescribed the drug. In step S202, the processing unit 20 may acquire prescription data by specifying the prescription ID and the patient ID from an external prescription management service or medical institution, or may read out prescription data issued in advance by a medical institution and stored from the prescription DB 211.

[0075] At this point, the processing unit 20 may record, in association with the prescription ID, the state in which the acquired prescription data has received a prescription request from the patient, i.e., the state in which the patient is about to receive the prescribed medication.

[0076] The processing unit 20 stores the acquired prescription data and the pharmacy ID corresponding to the first device 1 that originated the request in the prescription DB 211 in association with the prescription ID (step S203), and transmits the acquired prescription data to the first device 1 that originated the request (step S204).

[0077] The processing unit 10 of the first device 1 receives the prescription data (step S103), stores the received prescription data, and stores the prescription ID in the storage unit 11 as shown in Fig. 5 in a state in which image data and audit results are not registered (step S104). Detailed information that can be referenced later by the prescription ID or patient ID, such as the patient ID, drug identification data, and other information except for the prescribed amount, contained in the prescription data, may be temporarily stored for output from the display unit 14 or a printer.

[0078] The processing unit 10 outputs information such as the drug identification data and name of the drug to be picked to the display unit 14 based on the prescribed drug identification data included in the prescription data (step S105). If the drug is picked by a picking device, the processing unit 10 outputs a picking address stored in association with the drug identification data in step S105. In step S105, the processing unit 10 may output the drug information to a printing device. The processing unit 10 waits until image data is output from the inspection support device 4.

[0079] A picking staff member, a pharmacist, or a picking device at the pharmacy picks the medicine based on the outputted information on the medicine. A picking staff member, a pharmacist, or a picking device at the pharmacy or the outsourced dispensing company places the medicine and the paper medium on which the prescription ID is printed on a tray T, and places the tray T on the placement table 42 of the inspection support device 4. The control unit 40 may be able to acquire the identification number of the tray T according to the rules of the pharmacy. When the tray T is placed on the placement table 42, the control unit 40 of the inspection support device 4 automatically detects this, or starts capturing an image upon receiving an operation from an operation unit (not shown). The control unit 40 of the inspection support device 4 outputs image data of the captured image to the first device 1 in association with time information of the image capture time.

[0080] The processing unit 10 acquires the image data output from the inspection support device 4 (step S106). The processing unit 10 determines the prescription ID corresponding to the acquired image data (step S107). In step S107, the processing unit 10 may acquire the prescription ID printed on the paper medium captured in the image of the acquired image data by character recognition, or may acquire the prescription ID by capturing an image of a two-dimensional code of the prescription ID and decoding it. In step S107, the processing unit 10 may acquire the prescription ID that has been registered in advance by a picking device or a picking staff in association with the identification number of the tray T from the identification number of the tray T acquired together with the image data.

[0081] The processing unit 10 adds the acquired image data to the prescription data stored in the storage unit 11 in step S104 by using the determined prescription ID (step S108).

[0082] The processing unit 10 specifies the patient ID associated with the prescription ID, and transmits a patient information reference request to the second device 2, including attribute data of the target patient and other prescription data for the same patient (step S109).

[0083] The processing unit 20 of the second device 2 receives the patient information reference request (step S205) and reads the patient's attribute data (gender, age, medical history) and other prescription data from the memory unit 21, prescription DB 211, or an external database based on the patient ID included in the reference request (step S206). In step S206, the processing unit 20 acquires the other prescription data from an external prescription management service. If the patient's medical history can be referenced, the processing unit 20 may also acquire this. The processing unit 20 transmits the read attribute data and other prescription data to the first device 1 that made the request (step S207). If the medical history data can be referenced, the processing unit 20 may also transmit this.

[0084] The processing unit 10 of the first device 1 receives (acquires) the patient attribute data and other prescription data (step S110). The processes of steps S109-S110 and steps S205-S207 may be performed simultaneously in parallel with the process of step S102.

[0085] The processing unit 10 creates an audit request using the received attribute data and other prescription data, the image data acquired in step S106, and the prescription data (step S111). The audit request is data requesting the pharmacist to confirm whether the medicine shown in the captured image is as prescribed for the patient, and whether the prescription is appropriate based on the patient's attributes, and to transmit the audit results. The processing unit 10 transmits the created audit request to the second device 2 (step S112).

[0086] The processor 20 of the second device 2 receives the audit request (step S208), assigns an ID for identifying each of the received audit requests, and stores the request in a list (step S209). The processor 20 may store in the prescription DB 211 that an audit request is being made in association with the prescription ID.

[0087] The processing unit 20 transmits the list of stored audit requests to the third device 3 (step S210). In step S210, the processing unit 20 displays the list of audit requests in a selectable manner in a Web service that can be viewed only from the third device 3. In step S210, the processing unit 20 may select and transmit the third device 3 used by a pharmacist at a pharmacy corresponding to the first device 1 that is the request source of the audit request, or may automatically select and transmit the third device 3 of a pharmacist that is in an auditable state based on the pharmacist's state information.

[0088] The processing unit 20 transmits the contents of the audit request of the ID selected by the pharmacist from the list of audit requests to the third device 3 and accepts the audit results (step S211). The audit results include the pharmacist ID that identifies the pharmacist who performed the audit and the OK / NG result of the audit. In step S211, when "Audit audit request" is selected on a Web service viewable by the pharmacist, the processing unit 20 may associate a flag indicating that an audit is in progress with the list of audit requests to prevent other pharmacists from selecting the request.

[0089] The processing unit 20 transmits the inspection result received in step S211 to the first device 1 that originated the request (step S212).

[0090] The processing unit 10 of the first device 1 receives the audit result (step S113) and adds the received audit result to the prescription data in the storage unit 11 (FIG. 5) (step S114). The processing unit 10 judges whether the audit result is OK or not (step S115). If the processing unit 10 judges that the audit result is OK (S115: YES), it judges that the drug can be handed over to the patient and outputs "handover OK" together with the prescription ID and the audit result to the display unit 14 (step S116). In this case, the pharmacist of the pharmacy hands over the drug stored in the tray T corresponding to the prescription ID output as "handover OK" to the patient while explaining the situation. If the drug is dispensed at the dispensing entrusted destination, the entrusting pharmacy explains the situation to the patient and confirms the situation. The pharmacist who performed the audit may explain the situation to the patient online via the third device 3 and confirm whether the drug may be sent directly from the dispensing entrusted destination to the patient or to the corresponding pharmacy. In the case of a dispensing contractor, the output of "delivery possible" in step S116 may be an output of "shipment possible" to the patient.

[0091] The pharmacist may store data such as audio and video data during the explanation and instructions for the medicine used in the explanation, using the operation unit 15 of the first device 1. The processing unit 10 of the first device 1 accepts registration of the completion of delivery at the operation unit 15 (step S117), adds the delivery date and time to the prescription data, and transmits the prescription data after addition to the data to the second device 2 (step S118). In step S118, the delivery date and time data shown in FIG. 5 is added, and the prescription history for one prescription ID is completed.

[0092] In step S118, when the processing unit 10 receives a drug delivery request from an information terminal such as the patient's smartphone via the second device 2, a web page provided by the pharmacy service, or a My Number Portal app medicine notebook app, the processing unit 10 may send data such as drug instructions to the patient's information terminal.

[0093] The processing unit 20 of the second device 2 receives the added prescription data transmitted from the first device 1 (step S213), stores it in the prescription DB 211 (step S214), and ends the process. As a result, the prescription DB 211 collects, in association with the prescription ID, the audit result, image data of the medicine at the time of picking, data on the date and time of delivery, and even the details of the treatment by the pharmacist at the pharmacy before the delivery of the medicine.

[0094] If the first device 1 judges that the audit result is NG (S115: NO), the processing unit 10 judges that the medicine cannot be handed over to the patient and outputs the prescription ID and the message "cannot be handed over" to the display unit 14 (step S119). The processing unit 10 judges whether the medicine is an error (step S120), and if it is judged that the medicine is an error (S120: YES), the processing returns to step S106 and the subsequent processing is resumed. If it is judged that the medicine is an error (S120: YES), there is a possibility that the picking staff or the picking device made a picking mistake. In this case, the processing unit 10 may temporarily output the operation history of the picking device and the recorded contents of various processes to the display unit 14 or another device. This allows the operator of the picking device to grasp the cause of the error and the upper control device to recognize the situation based on the output contents.

[0095] If it is determined that the medicine is not an error (S120: NO), the processing unit 10 determines that there is a doubt about the prescription content, outputs that there is a doubt on the display unit 14 (step S121), adds a note to the prescription data (FIG. 5), and transmits it to the second device 2 (step S122). The prescription history data transmitted in step S122 is stored in the prescription DB 211 of the second device 2. In this case, the pharmacist at the pharmacy handles the matter by contacting the medical institution that issued the prescription to inquire about the doubt, etc.

[0096] FIG. 11 is a diagram showing an example of an audit screen 330 displayed on the third device 3. The audit screen 330 in FIG. 11 shows an example of a list of audit requests output from the second device 2. The audit screen 330 in FIG. 11 displays a pharmacist ID for identifying a pharmacist who uses the third device 3. The audit request includes an ID for identifying each request and a prescription ID. As shown in FIG. 11, the audit request may display a pharmacy ID or a pharmacy name for identifying the pharmacy that made the request. The list of audit requests displayed may include all audit requests received by the second device 2, but may also extract audit requests from pharmacies in the area in which the pharmacist is in charge and in neighboring areas, taking into account drugs that differ depending on the area. Each audit request is associated with a button 331 for selecting it. When the pharmacist selects one of the buttons 331, the third device 3 notifies the second device 2 of the ID of the selected audit request, and the processing unit 20 of the second device 2 can accept the selection.

[0097] FIG. 12 is a diagram showing another example of the inspection screen 330 displayed on the third device 3. The inspection screen 330 in FIG. 12 shows an example displayed after any of the inspection requests is selected on the inspection screen 330 shown in FIG. 11. The inspection screen 330 in FIG. 12 includes a field 332 showing data on the medicine of the prescription corresponding to the selected inspection request, a captured image 333 capturing an image of the picked medicine, and a field 334 showing attribute data of the patient for whom the prescription is to be made. In the inspection screen 330 in FIG. 12, a button 335 for displaying details for referring to other prescription data and medical history is displayed next to the field 334 showing the attribute data of the patient for whom the prescription is to be made.

[0098] The inspection screen 330 shown in FIG. 12 includes buttons 336 and 337 for inputting the inspection result, and an input field 338 for inputting a comment regarding the inspection result. The button 336 is a button that is selected when the inspection result is NG, and the button 337 is a button that is selected when the inspection result is OK. When either the button 336 or 337 is selected, a confirmation screen is displayed again, and transmission is not possible without confirmation. After confirmation on the confirmation screen, the third device 3 transmits the ID of the inspection request, the pharmacist ID, the inspection result (OK or NG), and the input comment data to the second device 2. The second device 2 accepts these data from the third device 3 in step S211.

[0099] The pharmacy information processing system 100 of the first embodiment allows an external pharmacist to perform the work of auditing at a pharmacy. As a result, a pharmacist stationed at a pharmacy can leave picking to a picking staff member and delegate auditing to others during busy times, thereby securing time to explain to patients when providing them with medicine. It is expected that the pharmacist will be able to focus on interpersonal tasks unique to pharmacists, such as explaining to patients, and feel rewarded. Since the audit can be requested online from a pharmacist stationed at another pharmacy, it is possible to shorten the waiting time of patients even if the number of staff at the pharmacy is insufficient during busy periods. The shortening of the waiting time is not only beneficial to patients, but also brings the benefit of reducing the burden on pharmacists and pharmacy staff. Since the audit can be requested online from a pharmacist stationed at another pharmacy, it is possible to level out the peaks in the provision of medicines over time or at certain times, reducing the burden on staff and pharmacists at the pharmacy, and it is expected that the geographical difference between other pharmacies will be leveled out. In the pharmacy information processing system 100, picking and shipping are performed by the dispensing contractor, so that pharmacists can focus on person-to-person tasks such as medication instructions without having to perform material-related tasks, thereby improving the efficiency of dispensing.

[0100] Second embodiment In the second embodiment, the delivery of the medicine to the patient is performed using a delivery locker. In the case of outsourcing of dispensing, the medicine may be delivered to the patient from the outsourced dispensing party using a delivery locker. As the delivery locker described below, a storage space such as a locker used for delivery may be used. FIG. 13 is a schematic diagram of a pharmacy information processing system 100 of the second embodiment. Except for the use of a delivery locker, the hardware configurations of the first device 1, the second device 2, and the third device 3 and the configuration of the network N are the same as those of the pharmacy information processing system 100 of the first embodiment. Therefore, among the configurations of the pharmacy information processing system 100 of the second embodiment, the configurations common to the configuration of the pharmacy information processing system 100 of the first embodiment are denoted by the same reference numerals and detailed description thereof is omitted.

[0101] In the second embodiment, as shown in FIG. 13, a delivery locker 5 is connected to a local network N3 of a pharmacy. The delivery locker 5 includes at least one storage unit 51 with a key, and a display unit 52, a voice input / output unit 53, an operation unit 54, and a camera 55 for realizing communication between a patient and a pharmacist. The lock of each storage unit 51 is controlled to be locked and unlocked by the control unit 50 (see FIG. 14). The delivery locker 5 unlocks the storage unit 51 and allows the drug to be taken out only when the delivery locker 5 can communicate with the first device 1, the audit result in the first device 1 is OK, and authentication of the patient who has come to receive the drug for the prescription data of the prescription ID determined to be transferable is successful.

[0102] 14 is a block diagram showing the configuration of the delivery locker 5. The control unit 50 is connected to the locking units of the storage units 51. The control unit 50 is connected to the display unit 52, the voice input / output unit 53, the operation unit 54, and the camera 55 via signal lines. The control unit 50 may be equipped with a reading unit that uses short-range wireless communication.

[0103] The control unit 50 uses a programmable logic controller. The control unit 50 executes the processes described below (see FIG. 16) based on a control program stored in the built-in memory using a microcontroller. The control unit 50 stores and sequentially updates the storage state in association with the identification data of the storage unit 51. The storage state is data indicating "empty" or, if not empty, the prescription ID of the stored medicine or the identification number of the tray T of the medicine.

[0104] The control unit 50 can be communicatively connected to the second communication unit 13 of the first device 1 by serial communication, and can recognize whether or not delivery is possible for each of the storage units 51 based on communication data output from the first device 1. For this reason, in the second embodiment, the second communication unit 13 of the first device 1 can be communicatively connected to the control unit 50 of the delivery locker 5.

[0105] The display unit 52 uses a display such as a liquid crystal display or an organic EL (Electro Luminescence) display. The display unit 52 may be a display with a built-in touch panel or a display without a built-in touch panel. The display unit 52 can display an image based on an image signal output from the control unit 50.

[0106] The audio input / output unit 53 uses a speaker and a microphone. The audio input / output unit 53 outputs audio based on an audio signal output from the control unit 50. The audio input / output unit 53 outputs the input audio signal to the control unit 50. The control unit 50 can perform A / D conversion of the input audio signal to create audio data.

[0107] The operation unit 54 uses a touch panel built into the display unit 52. The operation unit 54 may be a numeric keypad provided on the housing, or may be other physical buttons. The operation unit 54 may be a short-range wireless communication device. The operation unit 54 may recognize instructions from voice using a voice input unit.

[0108] The camera 55 is a visible light camera. The camera 55 captures an image of the two-dimensional code. The camera 55 may capture an image of the patient who comes to the delivery locker 5.

[0109] Control unit 50 can acquire image data of an image captured by camera 55, acquire audio data input by audio input / output unit 53, and transmit the image data and audio data to first device 1. Based on the data transmitted from first device 1, control unit 50 can output audio from audio input / output unit 53 while displaying an image on display unit 52.

[0110] The display unit 52, audio input / output unit 53, operation unit 54 and camera 55 may be those of an information terminal such as a smartphone of the patient or the patient's medication manager connected to the control unit 50 of the delivery locker 5.

[0111] The following describes the process of handing over medicines to patients in the pharmacy information processing system 100 of the second embodiment, which includes the handover locker 5. As for the process procedure of obtaining the audit result in the first device 1 and storing the data in the second device 2 in the second embodiment, the processes from step S101 to step S115 and S119 to S122 are the same as those in the first embodiment, and therefore the description will be omitted.

[0112] 15 to 17 are flowcharts showing an example of a process at the time of delivery in the pharmacy information processing system 100 of the second embodiment. In the second embodiment, even if a pharmacist is not present, delivery of medicines is possible by the following process.

[0113] In the second embodiment, the first device 1 is suitable for accepting a request for prescription of a drug in advance from an information terminal such as a smartphone of a patient or a patient's drug manager. When the processing unit 10 of the first device 1 accepts a request for prescription of a drug, the processing unit 10 transmits a request to and receives data transmitted in response to the request from the second device 2 based on the prescription ID and patient ID corresponding to the prescription request, and receives and stores the audit result (S101-S114). During this process, a pharmacist outside the pharmacy can perform an audit based on the image of the drug captured by the audit support device 4, and proceed with the procedure up until just before the drug is handed over to the patient.

[0114] When the processing unit 10 of the first device 1 determines that the audit result is OK (S115: YES), it instructs the display unit 14 or the picking device to store the drug in the storage unit 51 of the delivery locker 5 (step S131). As a result, the pharmacy staff or the picking device stores the drug stored in the corresponding tray T in the storage unit 51 and locks it. In the case of outsourcing of dispensing, the process of step S131 may be interpreted as an instruction to send the drug to the storage unit 51 of the delivery locker 5 located away from the dispensing contractor where the picking was performed.

[0115] The control unit 50 of the delivery locker 5 detects that the medicine has been stored in the storage unit 51 (step S501). In step S501, the control unit 50 detects this, for example, when a staff member inputs the identification number of the tray T or the prescription ID into the operation unit 54 to lock the locker. The control unit 50 may detect that the medicine has been stored by installing a camera for capturing an image of the inside of the storage unit 51 for each storage unit 51 and acquiring an image of the tray T, the medicine placed on the tray T, and the paper medium on which the prescription ID is printed from the camera. The prescription ID may also be acquired by capturing an image of the paper medium on which the two-dimensional code of the prescription ID is printed. The identification number of the tray T may be acquired by installing a reader for reading a tag attached to the tray T inside each storage unit 51.

[0116] The control unit 50 notifies the first apparatus 1 of the detection (step S502). The control unit 50 notifies the first apparatus 1 of the identification number of the tray T or the prescription ID obtained upon detection in step S501, and the storage unit identification data for identifying the storage unit 51.

[0117] The first device 1 receives a notification from the control unit 50 of the delivery locker 5 by the second communication unit 13 that the storage of the medicine has been detected (step S132). The processing unit 10 of the first device 1 identifies the prescription ID corresponding to the identification number of the tray T included in the notification, or the prescription ID included in the notification (step S133). The processing unit 10 reads out the prescription data of the identified prescription ID from the storage unit 11 (step S134), and notifies the patient's information terminal that the delivery is possible for the corresponding patient ID, and the storage unit identification data of the storage unit 51 included in the notification received in step S132 (step S135). The first device 1 waits until the patient or the patient's medicine manager arrives at the delivery locker 5.

[0118] The control unit 50 of the delivery locker 5 detects by the operation unit 54 or the camera 55 that the patient or the patient's medicine manager has come to pick up the medicine (step S503). In step S503, the control unit 50 detects that the patient ID and password have been entered into the operation unit 54, and that the camera 55 has captured an image of the patient ID, such as a My Number card held by the patient or manager.

[0119] The control unit 50 executes authentication of the patient or the administrator (step S504). In step S504, the control unit 50 may accept input of a password corresponding to the patient ID, or may execute authentication based on a code stored in a My Number card or other card. The authentication may be executed by the first device 1, or may be executed by the second device 2 via the first device 1.

[0120] The control unit 50 notifies the first device 1 of the arrival of the patient or the patient's medicine manager together with the data related to the authentication (step S505).

[0121] The processing unit 10 of the first device 1 receives a notification of the arrival of the patient or the patient's drug manager from the control unit 50 of the delivery locker 5 (step S136). The processing unit 10 determines whether or not authentication of the patient or the patient's drug manager has been successful (step S137).

[0122] If the processing unit 10 determines that the authentication is successful (S137: YES), it transmits a request to the third device 3 of the pharmacist who performed the audit or another pharmacist for the corresponding prescription ID to communicate with the patient to confirm the medicine (step S138). The processing unit 10 establishes a video call between the third device 3 of the pharmacist who responded to the request and the control unit 50 of the delivery locker 5, with the second device 2 acting as a server (step S139).

[0123] In step S139, the display unit 52, audio input / output unit 53, and camera 55 of the delivery locker 5, and the display unit 33, audio input / output unit 35, and camera 36 of the third device 3 are used to enable communication via video call between the patient or manager who has come to pick up the medication and the pharmacist.

[0124] After the video call ends, the processing unit 10 accepts an operation from the pharmacist on the third device 3, and determines whether the operation has been performed to allow the delivery as a result of the communication (step S140). If the processing unit 10 determines that the operation has been performed by the pharmacist to allow the delivery (S140: YES), it notifies the control unit 50 of the delivery locker 5 that the locker can be unlocked (step S141).

[0125] When the control unit 50 of the delivery locker 5 receives the notification that the lock can be released from the first device 1 (step S506), it outputs an unlock signal to unlock the corresponding storage unit 51 (step S507). The control unit 50 outputs from the display unit 52 and the voice input / output unit 53 that the delivery is possible (step S508). This allows the patient or the patient's drug manager to take out the drug from the storage unit 51.

[0126] The control unit 50 recognizes that the medicine has been removed (step S509). In step S509, the control unit 50 recognizes this by storing data indicating an empty state in association with the storage unit identification data of the stored storage unit 51. The control unit 50 notifies the first device 1 that the medicine has been handed over to the patient or manager (step S510).

[0127] When the processing unit 10 of the first device 1 receives the notification that the medicine has been delivered (step S142), it stores the delivery date and time and the data of the video call made in step S139 in the prescription history of the storage unit 11 (step S143), and ends the process. The prescription history data stored in step S143 is transmitted to the prescription DB 211 of the second device 2 and updated. The data stored in step S142 may be audio data containing only audio instead of the video call data, or may be video data recorded from the video call, or operation data in a chat format instead of the video call.

[0128] If it is determined in step S137 that the authentication has not been successful (S137: NO), the processing unit 10 notifies the control unit 50 of the transfer locker 5 that the locker cannot be unlocked (step S144).

[0129] When the control unit 50 of the delivery locker 5 receives a notification from the first device 1 that release is not possible after authentication (step S511), it outputs from the display unit 52 and the voice input / output unit 53 that authentication of the patient or the patient's manager has failed (step S512), and ends the process. In step S512, the control unit 50 prompts the patient or the patient's drug manager to output a message urging them to start the process again when they come to pick up the drugs.

[0130] In step S140, when the processing unit 10 determines that the operation to allow delivery has not been performed (S140: NO), the processing unit 10 of the first device 1 stores in the prescription history that delivery is not possible, the comment from the pharmacist, that there are doubts, and the data of the video call made in step S139 (step S145). The processing unit 10 transmits the prescription history data stored in step S145 to the second device 2 (step S146). As a result, the prescription history data, including the presence or absence of doubts from the pharmacist, is stored in the prescription DB 211 of the second device 2 in association with the prescription ID. The processing unit 10 notifies the control unit 50 of the delivery locker 5 that the locker cannot be unlocked (step S147).

[0131] When the control unit 50 of the delivery locker 5 receives a notice from the first device 1 that the call cannot be cancelled after the video call (step S513), it outputs from the display unit 52 and the voice input / output unit 53 that the delivery is not possible and that the patient should wait (step S514), and ends the process. In step S514, a message may be output to the patient or the patient's drug manager requesting that the patient wait at the pharmacy or return, in order to make an inquiry to the medical institution.

[0132] When delivery is not possible, there may be cases where a consultation is necessary. For example, when a patient wishes to change to a generic drug as a result of communication with the patient, or when the pharmacist obtains information that the patient was not able to fully convey to the doctor, there may be cases where a request should be made to reconsider the prescribed drug. In this case, in step S140, the first device 1 is enabled to accept an operation of "delivery possible" or "make a consultation" on the third device 3, and when the operation of "make a consultation" is performed, the first device 1 executes a consultation on the drug via the second device 2.

[0133] When the medical institution, pharmacist, and patient confirm again through the processing procedures in Figures 8-10 and 15-17 that the appropriate medication has been prescribed, including any changes to the medication, the medication is given to the patient. In the pharmacy information processing system 100, the data after the change or confirmation is updated in the prescription history, linked to the original prescription ID, and the prescription DB 211 is updated.

[0134] FIG. 18 is a diagram showing an example of the contents of the prescription history stored in the first device 1 of the second embodiment. The example of the contents of FIG. 18 corresponds to the contents of the prescription history shown in FIG. 5 of the first embodiment. FIG. 18 is different from the prescription history shown in FIG. 5 in that the presence or absence of a question inquiry is stored and that video call data between the patient and the pharmacist is stored instead of explanation data. In the example shown in FIG. 18, the patient ID "123876456789", the drug ID, image data of the picked drug, the audit result (OK), and the video call data are stored in association with the prescription ID "23080100006982", and the fact that there is a question and the drug cannot be handed over is stored. In the example shown in Figure 18, the prescription with prescription ID "23080100006982" was deemed questionable and undeliverable by the pharmacist, so the prescription data with some of the medication corrected for the same patient is stored in association with the prescription ID "23080100006995" that was reissued after an inquiry into the prescription. The prescription ID that was deemed questionable and associated with the prescription ID is also stored in the audit results section.

[0135] In this way, the pharmacy information processing system 100 using the delivery locker 5 allows the patient or the patient's drug manager to receive the drug based on the prescription even during the time when the pharmacist is not at the pharmacy. In addition to the benefit of reducing the patient's waiting time, it is also possible to diversify the way pharmacists work. Even when working online, pharmacists can be expected to focus on their unique interpersonal work and feel rewarded. Since prescription data is stored according to whether or not there was a question, it is possible to analyze the prescription content for which a question was asked after the fact. Storing prescription data according to whether or not there was a question can be done in the same way by accepting operations at the first device 1 or the third device 3 even when the drug is handed over face-to-face without using the delivery locker 5.

[0136] In the second embodiment, an example is shown in which a delivery locker 5 is used. In the case of outsourcing of dispensing, the medicine may be delivered to a delivery locker 5 independent of the pharmacy, or it may be handed over directly to the patient or the patient's medicine manager via a delivery company. In this case, the first device 1 of the pharmacy information processing system 100 executes the same processing as the processing procedures shown in Figs. 15 to 17, but the processing of the delivery locker 5 is executed by the terminal of the delivery company or the patient's information terminal device.

[0137] For example, the process of step S131 of the first device 1 in FIG. 15-FIG. 17 is replaced with a shipping instruction to the delivery company. At this time, the first device 1 may acquire the address or residence of the patient or the patient's drug manager. In response to this, the processing unit 10 of the first device 1 may receive, in step S132, a receipt notification received by the delivery company, not from the control unit 50 of the delivery locker 5, together with the delivery number, and in step S135, notify the delivery number of the delivery company to the patient in place of the storage unit identification data. In step S136, the processing unit 10 may receive a notification from the delivery company's terminal notifying that the address or residence of the patient or the patient's drug manager has been reached. If the video call in step S139 has been performed in advance between the third device 3 and the patient's information terminal, and there is a record of this, the processing unit 10 notifies the delivery company's terminal device of "delivery possible" instead of "unlock possible" in step S141. Also in step S142, the processing unit 10 may receive a notification that the medicine has been handed over from the delivery company to the patient or the patient's medicine manager.

[0138] Third embodiment In the third embodiment, the second device 2 automatically determines whether or not there is a question about the medicine, makes a question about the medicine to the medical institution, and continues to store the question in the prescription DB 211. In the third embodiment, similar to the aspect shown in the second embodiment, when a pharmacist judges that there is a question about a medicine once picked based on prescription data, the question is sequentially stored in the prescription history and also stored in the prescription DB 211.

[0139] The configuration of the pharmacy information processing system 100 of the third embodiment is similar to that of the pharmacy information processing system 100 of the first embodiment, except that the presence or absence of an inquiry is stored in the prescription data and that an analysis process described below is performed. Therefore, among the configurations of the pharmacy information processing system 100 of the third embodiment, the configurations common to the configurations of the pharmacy information processing system 100 of the first embodiment are denoted by the same reference numerals and detailed description thereof is omitted.

[0140] 19 is a flowchart showing an example of an analysis process procedure executed by the second device 2 in the pharmacy information processing system 100 of the third embodiment. The processing unit 20 of the second device 2 executes the following process at any timing based on the prescription data including the presence or absence of doubt stored in the prescription DB 211. The processing unit 20 may execute the following process at a specified cycle of a certain period, for example, once a week, once a month, once every three months, once a year, etc., or may execute the following process every time an analysis request is received via the third device 3.

[0141] The processing unit 20 extracts and reads out prescription data for which a specific drug is prescribed from among prescription data for a recent predetermined period stored in the prescription DB 211 (step S221). Based on the patient ID included in the extracted prescription data, the processing unit 20 classifies the read out prescription data by attribute data indicating the attributes of the patient identified by the patient ID (step S222).

[0142] The processing unit 20 calculates the proportion of prescriptions determined by the pharmacist to be suspicious by attribute (step S223). In step S223, the processing unit 20 classifies the prescription data into, for example, "1: male in teens," "2: female in teens," "3: male in twenties," "4: female in twenties," "5: male in thirties," "6: female in thirties," ... and calculates the proportion of prescriptions determined to be suspicious when a specific drug is prescribed. In step S223, the processing unit 20 may classify the prescription data into, for example, "1: allergy," "2: history of diabetes," "3: history of cancer," ... and calculate the proportion of prescriptions determined to be suspicious when a specific drug is prescribed by medical history. Similarly, the processing unit 20 may classify the prescription data into, for example, co-taking drugs, and calculate the proportion of prescriptions determined to be suspicious when a specific drug is prescribed.

[0143] The processing unit 20 stores the proportion of the attributes that are determined to be suspicious, calculated in step S223, in the storage unit 21 (step S224), and ends the analysis. In step S224, the processing unit 20 may store only attributes that are a predetermined proportion or more out of the proportions of the attributes that are determined to be suspicious.

[0144] In step S223, the processing unit 20 may calculate data indicating a correspondence relationship between a parameter indicating an attribute and a possibility of being judged as suspicious other than the proportion of the attribute-based suspicious judgment. For example, the processing unit 20 may derive a correlation coefficient between age and the proportion of the suspicious judgment.

[0145] The proportion of drugs that are determined to be suspicious for each attribute, for each parameter indicating the attribute derived by the processing of the flowchart shown in FIG. 19, is output from the second device 2 to the first device 1 or the third device 3 so that the pharmacist can check it together with the target prescription data. For example, in the flowcharts shown in FIG. 8 to FIG. 10, the processing unit 20 outputs the proportion of drugs that are determined to be suspicious for each attribute, calculated for the drugs included in the prescription, in the audit request sent from the second device 2 to the third device 3 in step S210. Also, in the flowcharts shown in FIG. 15 to FIG. 17, the processing unit 20 may output the proportion of drugs that are determined to be suspicious for each attribute in the request sent from the second device 2 to the third device 3 in step S138.

[0146] The proportion of cases where doubts are determined by attribute may be used to automatically output doubts to the medical institution that issued the prescription when the second device 2 acquires the prescription data from the medical institution. Fig. 20 is a flowchart showing an example of a processing procedure of the second device 2 in the pharmacy information processing system 100 of the third embodiment.

[0147] When the processing unit 20 of the second device 2 directly or indirectly acquires prescription data issued by a medical institution (step S231), it reads out patient attribute data from the memory unit 21 or acquires it from an external source based on the patient ID included in the acquired prescription data (step S232).

[0148] The processing unit 20 reads out from the storage unit 21 a proportion of the drugs identified from the drug IDs included in the acquired prescription data that are determined to be suspicious by attribute, the proportion corresponding to the patient's attributes (step S233). The processing unit 20 determines whether the read proportion is equal to or greater than a predetermined proportion (step S234).

[0149] If it is determined that the read ratio is equal to or greater than a predetermined ratio (S234: YES), the processing unit 20 outputs data regarding the inquiry to the issuer of the prescription data (step S235), and ends the processing.

[0150] If it is determined that the read ratio is less than the predetermined ratio (S234: NO), the processing unit 20 determines that there is little possibility of suspicion and ends the process.

[0151] In the pharmacy information processing system 100 of the third embodiment, the presence or absence of doubt is also collected in the second device 2 in association with the prescription data, the audit result, and the result of delivery. By analyzing the prescription DB 211 that stores the collected prescription data including the presence or absence of doubt, data indicating the correspondence between the audit result, the presence or absence of doubt, and the attributes of the patient can be derived and output to the pharmacist or medical institution that utilizes the prescription data. The data indicating the correspondence may be a learning model that has been trained to output the audit result, the likelihood of the presence or absence of doubt, etc. when the prescription data and the attributes of the patient are input by machine learning. The input may be the ID of the pharmacy (store), the region, or the identification data of the hospital, not limited to the prescription data and the attributes of the patient. In this case, it is also possible to cause the learning model to output the likelihood of doubt according to the tendency of prescriptions that differ depending on the pharmacy (store), the region, and the hospital, and the contents of the prescription that differ depending on the pharmacy and the patient can be output to the medical institution or the pharmacist as reference information. In this way, a system that allows audits to be requested online from pharmacists stationed at other pharmacies makes it possible to reduce waiting times for patients, standardize the workload of pharmacists, and make use of the data that can be collected.

[0152] (Fourth embodiment) As shown in the third embodiment, the system allows an audit to be requested online from a pharmacist stationed at another pharmacy, and the prescription data is collected in the prescription DB 211, making it possible to utilize the data. In the fourth embodiment, the pharmacy information processing system 100 acquires the effects of a drug on a patient after prescription, stores the acquired effects on the patient in association with each other, and calculates an index for evaluating the suitability of the drug for the patient.

[0153] In the pharmacy information processing system 100 of the fourth embodiment, as described in the first and second embodiments, the first device 1 receives an audit result from the third device 3 using image data obtained by the audit support device 4 for the acquired prescription data, and outputs whether or not the drug can be handed over. In the fourth embodiment, the audit work at the pharmacy can also be performed by an external pharmacist. In the fourth embodiment, the prescription data when the drug is handed over and the effects of the drug on the patient after the drug is prescribed are further stored in the second device 2 and utilized. The second device 2 acquires the effects of the drug on the patient after the drug is prescribed, for example, via an application program installed in an information terminal used by the patient or the patient's drug manager. The acquisition of the effects of the drug on the patient after the drug is prescribed may be realized by a pharmacist's interview at the pharmacy, rather than by this application program, and may be input via the third device 3.

[0154] FIG. 21 is a schematic diagram of a pharmacy information processing system 100 of the fourth embodiment. In the fourth embodiment, the pharmacy information processing system 100 includes an information terminal 6 used by a patient. Except for the use of the information terminal 6 and the processing procedure by the second device 2 described below, the hardware configurations of the first device 1, the second device 2, and the third device 3 and the configuration of the network N in the pharmacy information processing system 100 of the fourth embodiment are similar to those of the pharmacy information processing system 100 of the first embodiment. Therefore, among the configurations of the pharmacy information processing system 100 of the fourth embodiment, the configurations common to the configuration of the pharmacy information processing system 100 of the first embodiment are denoted by the same reference numerals and detailed description thereof will be omitted.

[0155] The information terminal 6 is used by the patient or the patient's drug manager. As described above, an application program is installed in the information terminal 6, which accepts input of whether or not the patient has taken the drug after the prescription and the patient's condition. The condition is data that directly indicates the effect of whether the patient has improved, worsened, or maintained the current condition. The condition may not be the patient's subjective opinion of improvement / worsening / maintaining the current condition, but may be vital data such as body temperature, blood pressure, pulse, and arterial oxygen saturation. The application program may be a My Number Portal application or a medicine notebook application. The data input via the application program of the information terminal 6 is linked to the patient ID and collected in the second device 2 via the network N. Since whether or not the patient has taken the drug is collected via the application program, the remaining number of drugs when the patient is cured may be calculated. Since whether or not the patient has taken the drug is collected via the application program, the total number of drugs remaining may be tallied not only for the patient but also for the pharmacy (the system).

[0156] 22 is a flowchart showing an example of a processing procedure executed by the second device 2 of the pharmacy information processing system 100 of the fourth embodiment. The processing unit 20 of the second device 2 executes the following processing every time an input of a state is received by the application program of the information terminal 6.

[0157] The processing unit 20 acquires the input state data together with the patient ID corresponding to the information terminal 6 from which the data was input, and stores the data together with time information in association with the patient ID (step S241). The processing unit 20 reads out the prescription data associated with the patient ID from the prescription DB 211 (step S242).

[0158] The processing unit 20 identifies the effect of the drug prescribed for the patient based on the read prescription data (step S243). In step S243, if the input condition data is data that directly indicates the effect, the processing unit 20 identifies it as it is. If the input condition data is vital data, the processing unit 20 identifies the effect of improvement / worsening / maintenance based on a comparison with past condition data.

[0159] The processing unit 20 stores the identified effect together with attribute data indicating the attributes of the patient in association with the drug ID (step S244), and ends the process.

[0160] By repeating the process procedure shown in FIG. 22, the effects of the medicine prescribed by the pharmacy information processing system 100 are collected in the second device 2.

[0161] 23 is a flowchart showing an example of a processing procedure executed by the second device 2 of the pharmacy information processing system 100 of the fourth embodiment. The processing unit 20 of the second device 2 executes the following processing for each drug at any timing based on the effect of each drug on the patient stored in the prescription DB 211. The processing unit 20 may execute the following processing at a specified cycle of a certain period, for example, once a week, once a month, once every three months, once a year, etc., or may execute the following processing every time a request specifying a drug is received from the third device 3.

[0162] The processing unit 20 reads out effect data stored for the target drug (step S251). The processing unit 20 classifies the read out effect data according to attributes associated with each of them (step S252). Examples of attributes are "1: male in his teens", "2: female in his teens", "3: male in his twenties", "4: female in her twenties", "5: male in his thirties", "6: female in her thirties", etc. The attributes may also be medical history or other drugs being taken.

[0163] The processing unit 20 calculates a numerical value indicating the suitability index of the target drug for each attribute (step S253). In step S253, the processing unit 20 may calculate the average of the aggregated points set as +1 if the effect is improved, -1 if the effect is worsened, and +0 (zero) if the effect is maintained, as a value indicating the suitability index. In step S253, the processing unit 20 may calculate the median or mode of the points assigned to each effect.

[0164] The processing unit 20 stores the calculated numerical values ​​indicating the aptitude indexes by attribute in the storage unit 21 (step S254), and ends the calculation process.

[0165] In this way, the calculated aptitude index for each attribute of the drug is stored in the second device 2 based on the effect on the patient. The aptitude index for each attribute of the drug stored by the processing procedure shown in FIG. 22 and FIG. 23 is output from the second device 2 to the first device 1 or the third device 3 so that the pharmacist can confirm it together with the target prescription data. For example, in the flowcharts shown in FIG. 8 to FIG. 10, the processing unit 20 outputs the audit request sent from the second device 2 to the third device in step S210, including the aptitude index for each attribute calculated for the drug included in the prescription. Also, in the flowcharts shown in FIG. 15 to FIG. 17, the processing unit 20 may output the request sent from the second device 2 to the third device in step S138, including the aptitude index for each attribute.

[0166] The attribute-specific suitability index may be used to automatically output a question to the medical institution that issued the prescription when the second device 2 acquires the prescription data from the medical institution. Fig. 24 is a flowchart showing an example of a processing procedure of the second device 2 in the pharmacy information processing system 100 of the fourth embodiment.

[0167] When the processing unit 20 of the second device 2 directly or indirectly acquires prescription data issued by a medical institution (step S261), it reads out patient attribute data from the memory unit 21 or acquires it from an external source based on the patient ID included in the acquired prescription data (step S262).

[0168] The processing unit 20 reads out from the storage unit 21 a numerical value indicating an aptitude index corresponding to the attribute of the patient among numerical values ​​indicating aptitude indexes by attribute for the drug identified from the drug ID included in the acquired prescription data (step S263). The processing unit 20 determines whether the numerical value indicating the read index value is equal to or smaller than a predetermined value (step S264).

[0169] If it is determined that the numerical value indicating the read suitability index is equal to or less than a predetermined value (S264: YES), the processing unit 20 outputs data regarding the inquiry to the issuer of the prescription data (step S265) and terminates the processing.

[0170] If it is determined that the read ratio exceeds the predetermined value (S264: NO), the processing unit 20 determines that there is little possibility of suspicion and ends the process.

[0171] In the pharmacy information processing system 100 of the fourth embodiment, the effects of the prescribed medicine on the patient are acquired and are collected in the second device 2 in association with the prescription data, the audit results, and the results of delivery. By processing the prescription DB 211 that stores the collected prescription data including the effects of the medicine on the patient, it is possible to derive data showing the correspondence between the effects of the medicine on the patient and output it to the pharmacist or medical institution that uses the prescription data. In this way, a system that can request an audit online from a pharmacist stationed at another pharmacy makes it possible to shorten waiting times for patients, level out the work of pharmacists, and utilize the collected data for appropriate prescription of medicines.

[0172] The embodiments disclosed above are illustrative in all respects and are not restrictive. The scope of the present invention is defined by the claims, and includes all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0173] 100 Pharmacy Information Processing System 1 1st device 10 Processing section 14 Display section P1 1st Program 2 Second device 20 Processing section 22 Communications Department P2 2nd Program 3 Third device 30 Processing section 33 Display section P3 3rd Program 4. Audit Support Device 44 Camera T-Tray

Claims

1. The computer obtaining prescription data including identification data of a patient and a prescription for said patient; Acquire an image of the medicine picked based on the prescription data; Obtaining attribute data of the patient obtained from patient identification data included in the prescription data; Outputting an audit request based on the acquired prescription data, image and attribute data; Transmitting the prescription data, the image, and the attribute data to an auditor who responded to the audit request; receiving audit results from the auditor; Based on the audit result, output is made as to whether the drug can be handed over to the patient. An information processing method for performing a process.

2. The computer, If the audit results received from the auditor contain any doubts, output data for inquiry into the doubts. The information processing method according to claim 1 , further comprising the step of:

3. The computer, The prescription data, the image and the attribute data, and the audit result for the audit request based on the prescription data, the image and the attribute data are stored while being classified into whether or not there is a doubt about the audit result. The information processing method according to claim 1 , further comprising the step of:

4. The computer, At least one of voice data, video data, and operation data relating to communication between the pharmacist and the patient when the medicine is handed over is stored in association with the prescription data. The information processing method according to claim 1 , further comprising the step of:

5. The computer includes: The stored prescription data is classified according to at least one parameter of gender, age, medical history, and medication history included in attribute data corresponding to the prescription data; Calculate the number or percentage of prescription data that is determined to be suspicious for each parameter, Output the calculated number or percentage of suspected cases 5. The information processing method according to claim 3, further comprising the step of: executing a process.

6. The computer, Obtaining data on the effects of a prescribed drug on a patient based on the prescription data; storing the acquired effect data in association with the prescription data; The effect data is classified according to the drug included in the prescription data and according to the corresponding patient attributes; calculating a suitability index for each drug for patients having the attributes by aggregating the effect data for each of the patient attributes; An aptitude index corresponding to the attributes of the patient included in the new prescription data is output to an auditor who responded to the audit request for the new prescription data, together with the prescription data, image, and attribute data.

5. The information processing method according to claim 3, further comprising the step of: executing a process.

7. The computer, If the calculated value indicating the suitability index is equal to or less than a predetermined value, the suitability index is attached to output data for inquiry regarding the prescription data. The information processing method according to claim 6, further comprising the step of:

8. The computer, A lock control unit is connected to a lock control unit of a lockable storage unit that stores the medicine picked based on the prescription data, If the audit result corresponding to the audit request for the prescription data is transferable and the authentication result based on the patient identification data included in the prescription data is successful, an unlock signal is output to the lock control unit. The information processing method according to claim 1 , further comprising the step of:

9. The computer obtaining prescription data including identification data of a patient and a prescription for said patient; Acquiring an image of the medicine picked up at a dispensing contractor from the dispensing contractor based on the prescription data; Obtaining attribute data of the patient obtained from patient identification data included in the prescription data; Outputting an audit request based on the acquired prescription data, image and attribute data; Transmitting the prescription data, the image, and the attribute data to an auditor who responded to the audit request; receiving audit results from the auditor; Based on the audit results, a decision as to whether or not the drug can be delivered to the patient is output to the dispensing contractor. An information processing method for performing a process.

10. On the computer, obtaining prescription data including identification data of a patient and a prescription for said patient; Acquire an image of the medicine picked based on the prescription data; Obtaining attribute data of the patient obtained from patient identification data included in the prescription data; Outputting an audit request based on the acquired prescription data, image and attribute data; Transmitting the prescription data, the image, and the attribute data to an auditor who responded to the audit request; receiving audit results from the auditor; Based on the audit result, output is made as to whether the drug can be handed over to the patient. A computer program that executes a process.

11. A first device for acquiring an image captured by an imaging device that captures an image of a picking result of a medicine to be used in a pharmacy, Obtaining prescription data from a medical institution, the prescription data including patient identification data and a prescription for the patient; An image of the medicine picked based on the prescription data is acquired from the imaging device; Obtaining attribute data of the patient obtained from patient identification data included in the prescription data; Transmitting an audit request to a second device based on the acquired prescription data, image, and attribute data; The second device is receiving a response from an auditor's third device each time the audit request is received from the second device; Transmitting the prescription data, the image, and the attribute data to an auditor who responded to the audit request; receiving audit results from the auditor; The inspection result and whether or not the medicine can be handed over to the patient based on the inspection result are transmitted to the first device. Information processing system.

Citation Information

Patent Citations

  • Method and apparatus for picking medicine

    JP2007289536A

  • Medicine preparation support system, control method, control program and device

    JP2023107632A

  • Dispensing support system, dispensing support method, and dispensing support program

    JP2023110914A

  • Video-based medication instruction system

    JP7186943B1

  • Audit support method and audit support apparatus

    JP2017192651A