JP7727535B2 - Prescription drug order management system, prescription drug order management program, and prescription drug order management method - Google Patents

Description

The present invention relates to a prescription drug order management system, a prescription drug order management program, and a prescription drug order management method.

In recent years, there has been a growing need for both patients and pharmacies to purchase prescription drugs online instead of traditional face-to-face dispensing, due to the expansion of online medical consultations via networks, the elimination of waiting times at pharmacies, and the improvement of operational efficiency within pharmacies. For this reason, development is underway on systems that can handle the entire process of prescription drug purchases, from application to delivery, online.
For example, Patent Document 1 discloses that when providing medicine to patients online using electronic prescriptions and electronic commerce, the patient listed on the prescription is matched with the purchaser of the medicine, and then the medicine is delivered to the purchaser.

Patent No. 5801015

When providing prescription drugs at pharmacies, pharmacists meet with patients to provide medication instructions, explaining how to take the drugs and how to store them, before providing the drugs to the patients. Medication instructions are an important step for ensuring the safety of patients when taking and storing their medications.
Therefore, when prescription drugs are provided online through e-commerce, etc., pharmacists are required to provide patients with medication instructions via two-way communication (remote medication instructions).However, conventional systems were not adequately equipped to handle remote medication instructions.
In addition to traditional dispensing tasks, pharmacies will now need to handle online purchase requests, such as shipping medicines, and there were concerns that their workload would increase.

The present invention was made in consideration of these points, and aims to provide a prescription drug order management system, prescription drug order management program, and prescription drug order management method that supports remote medication instructions and reduces the workload of pharmacies.

To solve the above problem, one aspect of the present invention provides a prescription drug order management system that manages operations within a pharmacy related to the receipt of prescription drug purchase orders. The system includes: a data acquisition unit that acquires prescription data indicating the contents of a prescription, and order data including application data regarding the prescription drug purchase order indicated by the prescription data and patient data for the patient for whom the prescription is to be issued; a storage unit that stores the prescription data and order data; an order data management unit that generates order data based on the prescription data and the order data, associates the order data with the prescription data and stores it in the storage unit, and manages the progress of the purchase order based on the order data; a medication instruction management unit that generates medication instruction data including the date and time of remote medication instruction via two-way communication for the patient corresponding to the order data, and manages the implementation status of the remote medication instruction based on the medication instruction data; a delivery management unit that generates delivery data regarding the delivery of the prescription drug included in the prescription data corresponding to the order data; and a data output unit that outputs the delivery data to an external server.

A prescription drug order management program according to one aspect of the present invention is a prescription drug order management program that manages operations within a pharmacy related to the receipt of prescription drug purchase orders, and operates a computer as a data acquisition unit that acquires prescription data indicating the contents of a prescription and order data including application data related to the prescription drug purchase order indicated by the prescription data and patient data for the patient for whom the prescription is to be issued; a storage unit that stores the prescription data and order data; an order management unit that generates order data including the order data, associates the order data with the prescription data and stores it in the storage unit, and manages the progress of the purchase order based on the order data; a medication instruction management unit that generates medication instruction data including the date and time that remote medication instruction was provided to the patient via two-way communication corresponding to the order data, and manages the implementation status of the remote medication instruction based on the medication instruction data; and a delivery management unit that generates delivery data related to the delivery of the prescription drug included in the prescription data corresponding to the order data, and outputs the delivery data to an external server.

A prescription drug order management method according to one aspect of the present invention acquires prescription data indicating the contents of a prescription, and order data including application data regarding a prescription drug purchase application indicated by the prescription data and patient data for the patient to whom the prescription is to be issued; stores the prescription data and order data; generates order data based on the prescription data and the order data; stores the order data in association with the prescription data; manages the progress of the purchase order based on the order data; generates medication instruction data including the date and time of remote medication instruction via two-way communication for the patient corresponding to the order data; manages the implementation status of the remote medication instruction based on the medication instruction data; generates delivery data regarding delivery of the prescription drug included in the prescription data corresponding to the order data; and outputs the delivery data to an external server.

According to one aspect of the present invention described above, it is possible to provide a prescription drug order management system, prescription drug order management program, and prescription drug order management method that support remote medication instructions and reduce the workload of pharmacies.

1 is a diagram illustrating an overview of a prescription drug order management system according to an embodiment of the present invention. FIG. 1 is a diagram illustrating an example of a hardware configuration of a computer system according to an embodiment of the present invention. 1 is a schematic functional block diagram showing an example of the functional configuration of a prescription drug order management system according to an embodiment of the present invention. 1 is a diagram showing an example of a data configuration in an order management data storage unit of a prescription drug order management system according to an embodiment of the present invention. FIG. 3 is a schematic diagram showing an example of order data stored in an order management data storage unit in one embodiment of the present invention. FIG. 1 is a flowchart illustrating a prescription drug order management method executed by a prescription drug order management system according to an embodiment of the present invention. 10 is a flowchart illustrating an example of a medication instruction implementation data generation process in the prescription drug order management method according to one embodiment of the present invention. FIG. 10 is a diagram showing an example of a medication instruction date data input screen in the prescription drug order management system according to one embodiment of the present invention. 10 is a flowchart illustrating an example of a delivery data generation process in the prescription drug order management method according to one embodiment of the present invention.

Embodiments of the present invention will be described below with reference to the drawings. However, the embodiments described below are merely examples, and are not intended to exclude various modifications or technological applications not explicitly stated below. This disclosure can be implemented in various modifications (such as combining various embodiments) without departing from the spirit of the disclosure. Furthermore, in the following description of the drawings, identical or similar parts are denoted by identical or similar reference numerals.

The following prescription drug order management system is realized through the cooperation of hardware, which is an information processing device such as a general-purpose computer, and software, which is a computer program. The computer program is readable by one or more processors provided in the computer system that realizes the prescription drug order management system, and when installed on a hard disk, the processor functions as each part of the prescription drug order management system.

The following describes a prescription drug order management system according to one embodiment of the present invention (hereinafter referred to as "this embodiment"), as well as a prescription drug order management method and prescription drug order management program executed by the prescription drug order management system, with reference to Figures 1 to 9.

1. Overview of the Prescription Drug Order Management System The prescription drug order management system 1 according to this embodiment is used as a system for managing operations (order processing) within a pharmacy related to the receipt of prescription drug purchase orders. Here, "prescription drugs" refers to medical drugs that are prescribed for administration to patients in a prescription issued by a medical institution based on a doctor's examination. As will be described in detail later, upon receiving data related to a prescription drug purchase order from the terminal device of the purchase order applicant, the prescription drug order management system 1 generates data for managing operations related to the order processing based on the data, manages the progress of the prescription purchase order based on the data, and performs various processes associated with this management.

FIG. 1 is a diagram showing an overview of a prescription drug order management system 1, and shows the relationship between the prescription drug order management system 1 and a group of devices with which data is shared.
The order management server 3 is a so-called server device, and the prescription drug order management system 1 is realized by the cooperation of hardware that is the server device and software that executes order management processing for managing operations related to prescription drug orders at the pharmacy. In other words, the prescription drug order management system 1 is executed by the order management server 3. Note that the order management server 3 does not need to be a device dedicated to the server, and may be a general-purpose information processing device such as a personal computer.

The order management server 3 is configured to be able to communicate with each device belonging to the external device group 5 and the terminal device group 7 via the network 9. This enables the prescription drug order management system 1 to share data with each device belonging to the external device group 5 and the terminal device group 7, and to send and receive various data related to order management processing between each device.

Here, being able to communicate does not necessarily mean that communication is always possible, but that communication is possible when necessary. Network 9 is assumed to be a general network such as the Internet, but may also include a LAN within a specific facility, a wide area Ethernet (registered trademark), or a WAN consisting of multiple LANs. Network 9 may also be a wired network, or may be partially or entirely a wireless network. Wireless networks may include wireless LAN, Wi-Fi, Bluetooth (registered trademark), and even mobile phone networks.

The group of external devices 5 includes a receipt computer 51, an accounting server 52, a delivery company server 53, a customer support center server (hereinafter referred to as "CS server") 54, a settlement server 55, a wholesaler server 56, and a marketing support server 57. These external devices are server devices that provide various functions, but they do not need to be dedicated server devices and may be general-purpose information processing devices such as personal computers.
The terminal device group 7 includes a medical institution terminal device 71 that is located in a medical institution and whose users are medical institution staff, an applicant terminal device 72 that is located in a pharmacy and whose users are pharmacy administrative staff and pharmacists, and a customer support center terminal device (hereinafter referred to as a "CS terminal device") 74 that is located in a customer support center (CS) and whose users are CS staff. Here, applicants who apply to purchase prescription drugs are assumed to be patients who have been prescribed the drugs, or the patient's family members or caregivers.

These terminal devices are general-purpose information terminal devices with communication and display functions, and are expected to include, for example, personal computers (PCs), tablet terminals, smartphones, etc. The medical institution terminal devices 71 may also include facsimile machines.

(1.1) Overview of the External Device Group Here, an overview of each device belonging to the external device group 5 will be described.
[Receipt computer]
The receipt computer 51 is a computer that mainly creates receipts (medical fee statements) that medical institutions create when they receive medical fees from review and payment institutions. In addition to creating receipts, the receipt computer 51 performs various processes such as entering patient medical treatment details, issuing prescriptions, managing medication dosages, and issuing drug information. The receipt computer 51 is also connected to the remuneration review system 6 and pharmaceutical master 8 so that it can send and receive data.

The remuneration review system 6 is a system at the review and payment agency that processes receipt, review, and payment to medical institutions for prescriptions. The pharmaceutical master 8 is a database that stores various basic information related to pharmaceuticals, including pharmaceutical codes used to create prescriptions. The prescription drug order management system 1 can share data with the prescription computer 51 because the order management server 3 is configured to be able to communicate with the prescription computer 51. Therefore, the prescription drug order management system 1 can acquire data generated by the prescription computer 51 and data acquired by the prescription computer 51 from the remuneration review system 6 and the pharmaceutical master 8. For example, the prescription drug order management system 1 can acquire data related to a patient's medical history and data related to the confirmed remuneration amount for each prescription from the prescription computer 51.
Furthermore, the prescription drug order management system 1 can output (transmit) various generated data to the receipt computer 51. For example, by linking data with the receipt computer 51, the prescription drug order management system 1 can output data related to prescriptions, data related to patients who use pharmacies, data related to dispensing, and the like to the receipt computer.

[Accounting Server]
The accounting server 52 is a server device that provides functions related to accounting operations such as financial accounting and management accounting. In the prescription drug order management system 1, the order management server 3 is configured to be able to communicate with the accounting server 52, so that data related to drug purchase slip data, accounts receivable, and accounts payable can be linked with the accounting server 52.

[Delivery company server]
The delivery company server 53 is a server device managed by the delivery company and provides various functions related to delivery operations. In the prescription drug order management system 1, the order management server 3 is configured to be able to communicate with the delivery company server 53, so that various data related to the delivery of prescription drugs to prescription drug purchase applicants can be linked with the delivery company server 53.

[CS Server]
A customer support center (CS) is an institution located inside or outside the pharmacy for responding to inquiries, and the CS server 54 is a server device that provides various functions related to inquiry operations at the CS. In the prescription drug order management system 1, the order management server 3 is configured to be able to communicate with the CS server 54, so that various data related to inquiries to pharmacies from prescription drug purchase applicants, patients, and medical institutions can be shared with the CS server 54. The CS server 54 is also connected to a CS terminal device 74 via a network 9. Therefore, the CS terminal device 74 can send and receive data to the prescription drug order management system 1 via the CS server 54.

[Payment server]
The payment server 55 is a server device managed by a payment agency, and provides various functions related to the payment of prescription drug purchase prices, etc. In the prescription drug order management system 1, the order management server 3 is configured to be able to communicate with the payment server 55, so that various data related to the payment of prescription drug purchase prices can be linked with the payment server 55, such as data related to the payment method, data related to the payment status, credit data, etc.

[Wholesale business operator server]
The wholesaler server 56 is a server device managed by the wholesaler that provides various functions related to the ordering and receiving of prescription drugs. In the prescription drug order management system 1, the order management server 3 is configured to be able to communicate with the wholesaler server 56, so that various data related to prescription drug orders from pharmacies to wholesalers can be linked with the wholesaler server 56, such as data related to prescription drug orders, data related to the delivery and billing amounts of ordered prescription drugs.

[Marketing support server]
The marketing support server 57 is a server device that provides a customer relationship management (CRM) function, a marketing automation (MA) function, and a sales automation (SA) function. Here, the CRM function is a function for building, improving, and maintaining relationships between the pharmacy and patients and medical institutions that use the pharmacy. The MA function is a function for managing information related to patients and medical institutions that are expected to use the pharmacy in the future and automating and visualizing marketing through digital channels such as email, SNS, and websites. The SA function is a function for automating and visualizing management of data related to sales activities (such as information on patients and medical institutions, progress of business negotiations, and business negotiation examples). The prescription drug order management system 1 can utilize the functions and data provided by the marketing support server 57 because the order management server 3 is configured to be able to communicate with the marketing support server 57.

2. Hardware Configuration of Prescription Drug Order Management System 1 and Linked Devices Next, an example of the hardware configuration of each device of the order management server 3 that realizes the prescription drug order management system 1 according to this embodiment, the group of external devices 5, and the group of terminal devices 7 that are communicably connected to the order management server 3 will be described using Figure 2. Each device of the order management server 3, the group of external devices 5, and the group of terminal devices 7 is realized, for example, by the computer system shown in Figure 2. Figure 2 is a diagram showing an example of the hardware configuration of a computer system 500 according to this embodiment.

The computer system 500 shown in FIG. 2 is configured as an arithmetic unit. The computer system 500 includes a processor 501, a ROM (Read Only Memory) 502, a RAM (Random Access Memory) 503, an auxiliary storage device (memory) 504, and an external interface (I/F) 505. The computer system 500 also includes an input device 506, a display device 507, and a communication interface (I/F) 508. Each of these components is interconnected by a bus 509.

The auxiliary storage device 504 is a non-volatile storage device that stores programs and data. The stored programs and data include, for example, the OS (Operating System), which is the basic software that controls the entire computer system 500, and application software that provides various functions on the OS. The auxiliary storage device 504 manages the stored programs and data using a specified file system and/or DB (database).

The external I/F 505 is an interface with an external device, such as a USB (Universal Serial Bus) port. The external device is assumed to be a specific recording medium. This allows the computer system 500 to read and/or write data from the recording medium via the external I/F 505. Examples of recording media include flexible disks, CDs (Compact Disks), DVDs (Digital Versatile Disks), SD Memory Cards, and USB Memory (Universal Serial Bus Memory).

The input device 506 includes a keyboard, mouse, touch panel, etc., and is used by the user to input various operation signals. The display device 507 includes a display, etc., and displays the results of processing by the computer system 500. The communication I/F 508 is an interface that connects the computer system 500 to an in-house network, the Internet, etc. This allows the computer system 500 to perform data communication via the communication I/F 508.

Processor 501 is a processor that controls the entire computer system 500. Processor 501 reads a program stored in ROM 502 via bus 509 onto, for example, RAM 503, and executes processing in accordance with the program, thereby realizing control and functions in computer system 500.

ROM 502 is a non-volatile semiconductor memory (storage device) that can retain programs and data even when the power is turned off. ROM 502 stores programs and data such as the BIOS (Basic Input/Output System) that is executed when the computer system 500 starts up, OS settings, and network settings. RAM 503 is a volatile semiconductor memory (storage device) that temporarily stores programs and data.

In this embodiment, the order management server 3 and each server device in the external device group 5 may be compatible with cloud computing. Cloud computing refers to a form of usage in which resources on a network are used without regard to specific hardware resources.

3 is a schematic functional block diagram showing an example of the functional configuration of the prescription drug order management system 1 provided by the order management server 3. As shown in FIG. 3, the prescription drug order management system 1 according to this embodiment has a data acquisition unit 11, a prescription data storage unit 12, an order management control unit 13, an order management data storage unit 14, a pharmaceutical data storage unit 15, and a data output unit 16.

Processor 501 (see Figure 2) reads the program stored in auxiliary storage device 504 into RAM 503 via bus 509 and controls each component of computer system 500 in accordance with the read program. For example, processor 501 directly or indirectly controls each component of computer system 500 by outputting control signals, commands, etc. to each component. In this way, processor 501 controls prescription drug order management system 1 to perform management processing for managing prescription drug order operations within the pharmacy. Note that the program related to the control of prescription drug order management system 1 may be distributed from a program distribution server or may be distributed in a state stored on a storage medium.

Each functional block will be explained below.
[Data acquisition section]
The data acquisition unit 11 is an interface that acquires various data transmitted by each device in the external device group 5 and the terminal device group 7 shown in Figure 1. When the data acquisition unit 11 acquires data transmitted from the communication I/F 508 of each device in the external device group 5 and the terminal device group 7, it outputs the data via the processor 501 to an output destination corresponding to the acquired data. This causes the prescription drug order management system 1 to execute processing corresponding to the data transmitted from each device in the external device group 5 and the terminal device group 7. Note that the function of transmitting data to the prescription drug order management system 1 (order management server 3) in each terminal device in the terminal device group 7 may be provided by browser software that operates a web browser.

As shown in FIG. 3, the data acquisition unit 11 includes a prescription data acquisition unit 111 that acquires prescription data indicating the contents of a prescription, and an order data acquisition unit 112 that acquires order data regarding the prescription drug orders indicated by the prescription data.

(Prescription data acquisition unit)
The prescription data acquisition unit 111 acquires prescription data transmitted to the prescription drug order management system 1 from at least one of the medical institution terminal device 71 and the applicant terminal device 72. In the prescription drug order management system 1, the prescription data linkage between the prescription drug order management system 1 and the medical institution terminal device 71 and the applicant terminal device 72 may be performed using email, a network fax (FoIP: FAX over IP) via the network 9, or file transfer (upload) using FTP (File Transfer Protocol).
Furthermore, the prescription data may be image data, text data, or XML data.

The prescription data acquisition unit 111 outputs the acquired prescription data to the prescription data storage unit 12 via the processor 501. The prescription data acquisition unit 111 also outputs a notification (command or signal) indicating that the prescription data has been received to the order management control unit 13 via the processor 501.

(Order data acquisition section)
The order data acquisition unit 112 acquires order data transmitted from the applicant terminal device 72 to the prescription drug order management system 1. The order data includes application data related to the prescription drug purchase application indicated by the prescription data and patient data. The order data is data entered by the user via the input device 506 of the applicant terminal device 72, and is transmitted from the communication I/F 508 of the applicant terminal device 72 to the prescription drug order management system 1. The order data acquisition unit 112 also outputs the acquired order data to the order management control unit 13 via the processor 501.

[Prescription data storage unit]
The prescription data storage unit 12 stores prescription data acquired by the prescription data acquisition unit 111. The prescription data storage unit 12 has an area (medical institution data storage area) for storing prescription data transmitted from the medical institution terminal device 71 and an area (applicant data storage area) for storing prescription data transmitted from the applicant terminal device 72. Data indicating which of the medical institution terminal device 71 and the applicant terminal device 72 transmitted the prescription data is attached to the prescription data. Therefore, prescription data input from the prescription data acquisition unit 111 via the processor 501 is stored in a storage area in the prescription data storage unit 12 corresponding to the transmission source. Furthermore, in the medical institution data storage area and the applicant data storage area, each piece of prescription data is stored in association with the acquisition date and time in the prescription data acquisition unit 111.

[Order Management Control Unit]
The order management control unit 13 controls the process for managing the order taking operations for prescription drugs in the pharmacy. Specifically, the order management control unit 13 controls the process for managing the order taking operations by executing the process for managing various data related to the order taking operations.
3, the order management control unit 13 has a patient management unit 131 that manages data related to patients, an order data management unit 132 that manages order data generated based on order data and prescription data, a medication instruction management unit 133 that manages data related to remote medication instruction to be given to patients, a delivery management unit 134 that manages data related to delivery of prescription drugs to patients, an inventory management unit 135 that manages data related to prescription drug inventory, an order management unit 136 that manages data related to ordering prescription drugs from wholesalers, and an inquiry management unit 137 that manages data related to inquiries from patients and medical institutions. Details of each element of the order management control unit 13 will be described later.

[Order management data storage unit]
The order management data storage unit (an example of a storage unit) 14 is a database that stores various data in table format that is used by the prescription drug order management system 1 to manage prescription drug order processing within the pharmacy. The data in the order management data storage unit 14 is registered, updated, and referenced by each component of the order management control unit 13. Details of the tables stored in the order management data storage unit 14 will be described later.

[Drug data storage unit]
The pharmaceutical data storage unit 15 stores data relating to various basic information on pharmaceuticals held in the pharmaceutical master 8. The data in the pharmaceutical data storage unit 15 is acquired through data linkage that is periodically executed between the prescription computer 51 connected to the pharmaceutical master 8 and the data acquisition unit 11 of the prescription drug order management system 1, and is output to the pharmaceutical data storage unit 15 via the processor 501. This allows the prescription drug order management system 1 to use the various data held in the pharmaceutical master 8.

[Data output section]
The data output unit 16 is an interface that acquires various data transmitted by each device in the external device group 5 and the terminal device group 7 shown in Fig. 1. When the data output unit 16 acquires data generated by the order management control unit via the processor 501, it outputs (transmits) the acquired data to each device in the external device group 5 and the terminal device group 7. This causes each device in the external device group 5 and the terminal device group 7 to execute processing based on the data generated by the prescription drug order management system 1. Note that, at each terminal device in the terminal device group 7, the function of receiving data from the prescription drug order management system 1 (order management server 3) may be provided by browser software that operates a web browser.

Each functional block in the prescription drug order management system 1 is realized by each component of the computer system 500. For example, the data acquisition unit 11 is realized by the communication I/F 508 of the computer system 500. Furthermore, for example, the prescription data storage unit 12, order management data storage unit 14, and drug data storage unit 15 are realized in the auxiliary storage device 504. Furthermore, when the processor 501 reads a program stored in the auxiliary storage device 504 into the RAM 503 and executes it, the program functions as the order management control unit 13.

(3.1) Configuration of the Order Management Data Storage Unit Next, the data stored in the order management data storage unit 14 will be described with reference to FIGS. 4 and 5. FIG.

Figure 4 is a diagram showing the general configuration of the order management data storage unit 14. As shown in Figure 4, the order management data storage unit 14 stores a patient table t401, an ordered prescription table t402, an order table t403, an order data table t404, a medication instruction management table t405, a medication instruction reservation table t406, a pharmacist table t407, a delivery table t408, an inventory table t409, an order table t410, and an inquiry table t411.

(Patient table)
The patient table t401 is a table that stores multiple patient data. Here, a patient refers to a patient to whom a prescription indicated by the prescription data acquired by the prescription data acquisition unit 111 is to be issued. Records in the patient table t401 are composed of data that uniquely identify the patient (patient number) and basic patient data (name, date of birth, email address, address, telephone number, etc.). The data in the patient table is generated and updated based on the patient data that constitutes the order data acquired by the order data acquisition unit 112. The data in the patient table may also be updated with patient data acquired by the data acquisition unit 11 through data linkage with the prescription computer 51.

(Order prescription table)
The received prescription table t402 is a table that stores multiple pieces of data indicating the contents of prescription data acquired by the prescription data acquisition unit 111. The records of the received prescription table t402 are composed of data that identifies the prescription data (prescription number), data related to the medical institution where the patient visited (medical institution name, doctor name, medical institution contact information), data indicating the patient for whom the prescription is issued (patient name, date of birth, gender), data related to the prescribed drug (prescription drug name, prescription drug shape, dosage, method of administration, storage method), data related to the validity period of the prescription (prescription expiration date), etc. The records of the received prescription table t402 also include the date and time when the prescription data acquisition unit 111 acquired the prescription data (prescription reception date and time).

(Orders table)
The order table t403 is a table that stores multiple pieces of order data acquired by the order data acquisition unit 112. Records in the order table t403 include information identifying an order (order number), basic patient data (name, date of birth, email address, address, telephone number), data related to the medical institution where the patient visited (medical institution name, visit date), data related to a patient's request to switch to a generic drug (generic drug preference flag), data related to the patient's request for the date and time of remote medication guidance (requested implementation date and time) (unavailable date and time), data related to payment for prescription drug purchases (payment method), and data related to the delivery of prescription drugs (specified delivery date and time). Of the data constituting the records in the order table t403, the basic patient data corresponds to the patient data in the order data acquired by the order data acquisition unit 112. Furthermore, of the data constituting the records in the order table t403, the data other than the basic patient data corresponds to the application data in the order data acquired by the order data acquisition unit 112.
In addition to the above data, the records of the order table t403 also include data relating to the date and time when the order data acquisition unit 112 acquired the order data (order reception date and time).
The records of the order table t403 are associated with the records of the patient table t401 and the received prescription table t402 by data for identifying the patient (patient number) and data for identifying the prescription data (prescription number), respectively.
In this way, the order management data storage unit 14 stores the prescription data acquired by the prescription data acquisition unit 111 and the order data acquired by the order data acquisition unit 112.

(Order data table)
The received order data table t404 is a table that stores a plurality of pieces of received order data generated based on the prescription data acquired by the prescription data acquisition unit 111 and the order data acquired by the order data acquisition unit 112. Here, the structure of the received order data (records) in the received order data table t404 will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of the structure of the received order data.
As shown in FIG. 5 , the order data includes an order number, a prescription number, a patient number, a patient name, data related to the implementation of remote medication counseling (requested implementation date and time, medication counseling implementation date, and the pharmacist in charge), data related to the prescription (prescription expiration date and name of the medical institution), and data related to the purchase order (whether or not a generic is desired, payment method, desired delivery date and time, and requested delivery method). The requested delivery method indicates the delivery method desired by the patient. The order data may also include data related to the acquisition status of prescription data (whether or not the original has been acquired). Whether or not the original has been acquired indicates whether the original prescription or data equivalent to the original has been acquired. Note that the order data may also include data other than those shown in FIG. 5 . The "requested delivery method," which indicates the patient's desired delivery method, may specify various delivery methods offered by the delivery company. For example, as a face-to-face delivery method (delivery method), "hand delivery" or "in-store pickup," in which the package (here, the prescription drug) is picked up at a storefront such as a convenience store, may be specified. Furthermore, for example, as a non-face-to-face delivery method, it may be possible to specify "drop-off delivery," in which the package (here, prescription drugs) is left at a designated location such as in front of the entrance or in a delivery box, thereby completing the delivery. The "delivery method request" is not limited to the above, and any method recognized as a delivery method for prescription drugs under legal systems or the like may be specified.

The order data is associated with records in the patient table t401 and the received prescription table t402 by the patient number and prescription number, respectively. Furthermore, the patient number and patient name in the order data correspond to the patient's basic data in the order table t403 (patient data in the order data acquired by the order data acquisition unit 112). Furthermore, the requested date and time of service and data related to the purchase order in the order data correspond to the request data in the order table t403 (request data in the order data acquired by the order data acquisition unit 112).

Furthermore, as shown in FIG. 5, the order data in the order data table t404 includes progress data indicating the progress of prescription purchase applications. As will be described in more detail below, the prescription drug order management system 1 can manage the progress of prescription purchase applications by updating the progress data in the order data table t404.

(Medication Instruction Management Table)
4, the medication instruction management table t405 is a table that stores medication instruction data, including the date and time of remote medication instruction provided to patients via two-way communication corresponding to the order data, in association with the order data. The records of the medication instruction management table t405 include data for association with the order data (order number), data related to the date and time of remote medication instruction (implementation date, implementation time zone), and data related to the pharmacist in charge of medication instruction (pharmacist in charge), etc.

(Medication instruction reservation table)
The medication instruction reservation table t406 is a table that stores multiple data related to the reservation status of remote medication instruction. The records (reservation status data) of the medication instruction reservation table t406 are configured to include data on dates and times when remote medication instruction can be performed at the pharmacy (available reservation dates and times) and data on the number of people for whom remote medication instruction can be performed at each available reservation date and time (available number of people). As will be described in detail later, the reservation status data in the medication instruction reservation table t406 is used when determining the date and time when remote medication instruction is performed.

(Pharmacist's table)
The pharmacist table t407 is a table that stores multiple pieces of data (pharmacist data) related to pharmacists working at pharmacies, i.e., pharmacists who are users of the pharmacy terminal devices 73 connected to the prescription drug order management system 1. The records (pharmacist data) in the pharmacist table t407 are composed of data that identify the pharmacist (pharmacist number, pharmacist name) and data related to the pharmacist's working days (working days of the week), etc.

(Delivery table)
The delivery table t408 is a table that stores delivery data related to delivery of prescription drugs included in prescription data corresponding to order data, in association with the order data.
The records in delivery table t408 are composed of data for associating with order data (order number), data regarding the delivery destination (patient name, patient address, patient contact information, desired delivery date), data regarding the delivery method (delivery type), data regarding packaging (packaging size), and data regarding the delivery method (whether or not it can be posted in a mailbox).

(Inventory table)
The inventory table t409 is a table that stores data (inventory data) related to the inventory of pharmaceuticals in the pharmacy for each pharmaceutical. The records in the inventory table t409 are composed of data related to the identification of the pharmaceutical (pharmaceutical code, pharmaceutical name), data related to the number of stocks (number of stocks, number of items to be delivered), data related to the delivery date (scheduled delivery date), etc.
(Order table)
The order table t410 is a table that stores multiple pieces of data (order data) related to pharmaceuticals ordered from wholesalers by pharmacies. Each record in the order table t410 is composed of data related to order identification (order number), data related to the supplier (supplier name), data related to the pharmaceuticals to be ordered (drug code, drug name), data related to the number of orders (order quantity), data related to the order date (order date and time), etc.

(query table)
The inquiry table t411 is a table that stores multiple pieces of data (inquiry data) related to the content of inquiries received by the CS (Customer Support Center). The records of the inquiry table t411 are composed of data related to the identification of the inquiry data (inquiry number), data related to the customer who made the inquiry (patient, purchase applicant, medical institution) (inquirer name, telephone number, email address), data indicating the content of the inquiry (inquiry content), and data such as the inquiry date and time indicating the date and time when the inquiry was made.
The inquiry data in the inquiry table t411 is acquired through data linkage between the CS server 54 and the data acquisition unit 11 of the prescription drug order management system 1, and is registered and updated in the inquiry table t411 via the processor 501. The inquiry data may also include data related to the pharmacist's response to the inquiry (whether a pharmacist is required to respond, and comments from the pharmacist).

In this way, the order management data storage unit 14 stores data related to the management of order operations in the prescription drug order management system 1, and each component of the order management control unit 13 refers to and updates the records in the order management data storage unit 14 in accordance with processing related to the management of order operations. This allows for centralized management of information related to the management of order operations in the prescription drug order management system.
5 are examples of tables stored in the order management data storage unit 14, and other tables may be stored in the order management data storage unit 14. The order management data storage unit 14 may also store data for managing prescription drug order taking operations at multiple pharmacies. This allows the prescription drug order management system 1 to manage prescription drug order taking operations at multiple pharmacies in an integrated manner.

(3.2) Configuration of the Order Management Control Unit Returning to FIG. 3, each unit of the order management control unit will be described.

(Patient Management Department)
The patient management unit 131 manages the patient data included in the order data transmitted from the applicant terminal device 72. Specifically, the patient management unit 131 extracts patient data from the order data acquired by the order data acquisition unit 112, and registers the extracted patient data in the order management data storage unit 14. The patient management unit 131 updates the patient data stored in the order management data storage unit 14 based on the extracted patient data. The order data transmitted from the applicant terminal device 72 is output from the order data acquisition unit 112 to the order management control unit 13 via the processor 501. The patient management unit 131 extracts patient data from the order data output to the order management control unit 13, and registers and updates the extracted patient data in a patient table t401 (described later) in the order management data storage unit 14.

(Order Data Management Department)
The order data management unit 132 generates order data based on the prescription data sent from the medical institution terminal device 71 or the applicant terminal device 72, and the patient data and order data contained in the order data sent from the applicant terminal device 72, and manages the progress of prescription drug purchase applications based on the order data.

Specifically, the order data management unit 132 generates order data based on the prescription data acquired by the prescription data acquisition unit 111 and the order data acquired by the order data acquisition unit 112, associates the order data with the prescription data and stores it in the order data table t404 of the order management data storage unit 14, and manages the progress of prescription drug purchase applications based on the order data. This allows the prescription drug order management system 1 to significantly reduce the burden of checking the progress of prescription drug purchase applications on pharmacists and staff.

Here, we will explain the progress data used to manage the progress of prescription drug purchase orders. The order data in order data table t404 (see Figure 5) includes "progress" data that indicates the progress of the prescription drug purchase order. This "progress" data represents progress data. Progress data is data that indicates the progress of the prescription drug purchase order, and is, for example, character string data. The status of the prescription drug purchase order changes according to the progress of the work (order taking work) within the pharmacy related to the order taking. In other words, the progress of the prescription drug purchase order corresponds to the progress of the work (order taking work) within the pharmacy related to the order taking. In other words, the progress data also corresponds to data that indicates the progress of the order taking work. Note that progress data is not limited to character string data and may be numeric. If the progress data is numeric, the order management data storage unit 14 may be provided with a progress data master table that converts numeric values indicating the progress data into character string information. This allows the numeric values indicating the progress data to be converted into character string data indicating the progress status, which can be used for display or printing.

It is preferable to set multiple progress data according to the content of the order processing. The more types of progress data there are, the more preferable it is, as this allows the progress of the order processing to be managed in finer units. Progress data includes, for example, "Order completed," "Medication instruction reservation completed," "Medication instruction implementation completed," "Dispensing completed," "Prescription confirmation completed," "Shipping completed," and "Delivery completed." In this way, the order data in the order data table t404 includes progress data indicating the progress status, and the order data management unit 132 updates the progress data based on the medication instruction data in the medication instruction management table t405 and the delivery data in the delivery table t408 that correspond to the order data. Details of updating the progress data will be described later.

<Displaying order data>
The order data management unit 132 can output order data (see FIG. 5 ), including progress data stored in the order data table t404, to the pharmacy terminal device 73 via the data output unit 16. For example, the order data management unit 132 generates display data for an order data display screen, including order data extracted from the order data table t404, and outputs the display data to the data output unit 16. As a result, the display data for the order data display screen is received by the communication I/F 508 of the pharmacy terminal device 73 via the network 9. Upon receiving the display data for the order data display screen, the pharmacy terminal device 73 displays the order data display screen via a web browser running on the display device 507. This allows the user of the pharmacy terminal device 73 to view the order data on the order data display screen. The order data management unit 132 may generate and output the display data for the order data display screen, for example, based on an order data display request from the pharmacy terminal device 73 being acquired by the data acquisition unit 11. This allows the order data to be displayed on the pharmacy terminal device 73 at the time desired by the user of the pharmacy terminal device 73, and the progress of the prescription drug purchase application can be confirmed using the progress data.

The order data display screen may display, for example, multiple order data records stored in the order data table t404 (see Figure 5) in a list format. This allows the user of the pharmacy terminal device 73 to check the progress of multiple order processing tasks at the same time. The order data display screen may display data for selected items of order data stored in the order data table t404. For example, the order data display screen may display data for some items of the order data records, including at least the patient name, progress data, medication instruction implementation date and time, and prescription expiration date. The order data display screen may also sort the display of order data in ascending or descending order of the selected item by selecting each item of order data using the input device 506 (e.g., a mouse) of the pharmacy terminal device 73. The order data display screen may also have an input area that can accept character input from the pharmacy terminal device 73 and a pressable search button (not shown). By pressing the search button, the user can extract order data records containing the string information in the input area from the order data table t404.

(Medication Guidance and Management Department)
The medication instruction management unit 133 generates medication instruction data including the date and time of remote medication instruction via two-way communication for the patient corresponding to the order data, and manages the implementation status of the remote medication instruction based on the medication instruction data. When the order data management unit 132 generates order data and stores it in the order data table t404, the medication instruction management unit 133 generates medication instruction data for the patient corresponding to the order data and registers it in the medication instruction management table t405. This allows the prescription drug order management system 1 to support medication instruction via two-way communication, i.e., remote medication instruction, and to significantly reduce the burden of checking the implementation status of the remote medication instruction by pharmacists and staff.

Specifically, the medication instruction management unit 133 determines the date and time for remote medication instruction to be performed for the patient indicated by the patient data included in the order data newly generated by the order data management unit 132 (for example, order data whose progress data is "order completed"), generates medication instruction date data including the date and time for remote medication instruction, and outputs this data to the data output unit 16. The data output unit 16 outputs the input medication instruction date data to the applicant terminal device 72.

As a result, the medication instruction date data is received by the communication I/F 508 of the applicant terminal device 72 via the network 9. The medication instruction date data is text data including the date and time of the remote medication instruction and the name of the patient who will receive the remote medication instruction. This significantly reduces the workload of pharmacists and staff compared to notifying patients of the date and time of the remote medication instruction by phone or email. Furthermore, outputting the medication instruction date data to the applicant terminal device 72 notifies patients that their prescription drug purchase application has been accepted (ordered) and that remote medication instruction will be provided, providing peace of mind to patients and their families and caregivers. The medication instruction date data can be shared between the prescription drug order management system 1 and the applicant terminal device 72 via email, SMS (short message service), or push notification. Details of the process for determining the date and time of the remote medication instruction and the process for outputting medication instruction date data to the applicant terminal device 72 will be described later.

(Delivery Management Department)
The delivery management unit 134 generates delivery data related to delivery of prescription drugs included in the prescription data corresponding to the order data, and outputs the delivery data to the delivery company server (an example of an external device) 53. The delivery management unit 134 also generates the delivery data based on the data related to prescription drugs included in the prescription data corresponding to the order data. This allows the prescription drug order management system 1 to significantly reduce the workload and work time compared to when pharmacists or staff manually create and check data related to prescription drug delivery.
Specifically, the delivery management unit 134 generates delivery data based on order data awaiting delivery (e.g., order data with progress data "prescription confirmation completed") for which a pharmacist has completed dispensing of prescription drugs and an audit of the dispensing (final audit) and confirmed the original prescription, and on prescription data corresponding to the order data awaiting delivery. It is also possible that the original prescription or data equivalent to the original prescription may not have been obtained during the final audit. Therefore, the delivery management unit 134 may generate delivery data based on order data with progress data "dispensing completed" (dispensed order data). The delivery management unit 134 also outputs the generated delivery data to the delivery company server 53 via the data output unit 16. This allows a delivery company to be requested to deliver and collect the prescription drugs. Details of the delivery data generation process will be described later.

(Inventory Management Department)
The inventory management unit 135 generates and updates inventory data in the inventory table t409 related to the inventory of pharmaceuticals at the pharmacy. When order data is generated by the order data management unit 132 and stored in the order data table t404, the inventory management unit 135 extracts prescription data corresponding to the order data from the received prescription table t402. The inventory management unit 135 updates the inventory data based on data related to the prescription drug (e.g., prescription drug name, dosage) in the extracted prescription data. For example, the inventory management unit 135 extracts inventory data based on the prescription drug name extracted from the received prescription table t402 from the inventory table t409 and updates the inventory quantity of the record by subtracting the dosage value from the inventory quantity value of the data. Furthermore, based on updates to the order data in the order table t410, the inventory management unit 135 obtains data related to the pharmaceuticals to be ordered, data related to the order quantity, data on the expected delivery date, etc. from the order management unit 136. As a result, the inventory management unit 135 updates the planned delivery quantity and planned delivery date for the record of inventory data related to the ordered drug in the inventory table t409. Furthermore, if the inventory data related to the ordered drug does not exist in the inventory table t409, the inventory management unit 135 generates new inventory data related to the drug and registers it in the inventory table t409.

(Order Management Department)
The order management unit 136 generates and updates order data in the order table t410 relating to pharmaceuticals ordered from the pharmacy to the wholesaler. The order management unit 136 also places an order for pharmaceuticals with the wholesaler server 56 based on order input data entered by the user of the pharmacy terminal device 73, which is acquired by the data acquisition unit 11 via the network 9.
Specifically, when the data acquisition unit 11 acquires order input data entered by the user of the pharmacy terminal device 73, the order management unit 136 registers the acquired order input data in the order table t410. The order management unit 136 also outputs the order input data registered in the order table t410 to the wholesaler server 56 via the data output unit 16. As a result, data on the pharmaceuticals ordered by the user (e.g., a pharmacist) of the pharmacy terminal device 73 and the order quantity are transmitted to the wholesaler server 56. The order management unit 136 may also generate display data for an order data input screen that allows the user of the pharmacy terminal device 73 to input order input data, and transmit the display data to the pharmacy terminal device 73 via the data output unit 16. As a result, the user of the pharmacy terminal device 73 can input order input data via the order data input screen.

(Inquiry Management Department)
The inquiry management unit 137 generates and updates inquiry data in an inquiry table t411 acquired through data linkage between the CS server 54 and the data acquisition unit 11 of the prescription drug order management system 1. When the data acquisition unit 11 acquires inquiry data from the CS server 54, the inquiry management unit 137 registers the acquired inquiry data in the inquiry table t411. Furthermore, when a reference request for inquiry data from the CS server 54 is acquired by the data acquisition unit 11, the inquiry management unit 137 outputs data extracted from the inquiry table t411 to the data output unit 16. This enables the CS server 54 and the CS terminal devices 74 connectable to the CS server 54 to perform processes related to inquiry responses (e.g., generating and sending inquiry response emails).
Furthermore, the inquiry management unit 137 may generate display data for an inquiry response input screen that enables the user of the pharmacy terminal device 73 to input a response comment (character string data) regarding the inquiry content, and transmit the display data to the pharmacy terminal device 73 via the data output unit 16. This allows the user of the pharmacy terminal device 73 to input a response comment regarding the inquiry content via the inquiry response input screen.

The inquiry management unit 137 may also output data extracted from the inquiry table t411 to the marketing support server 57 via the data output unit 16. This allows the marketing support server 57 to use inquiry data from patients and medical institutions.

As described above, the prescription drug order management system 1 according to this embodiment is a prescription drug order management system that manages operations within a pharmacy related to the receipt of prescription drug purchase applications, and includes a data acquisition unit 11 that acquires prescription data indicating the contents of a prescription, and order data including application data related to the prescription drug purchase application indicated by the prescription data and patient data of the patient for whom the prescription is to be issued. Furthermore, the prescription drug order management system 1 includes an order management data storage unit 14 that stores the prescription data and order data acquired by the data acquisition unit 11, and an order data management unit 132 that generates order data based on the prescription data and order data acquired by the data acquisition unit 11, associates the order data with the prescription data, stores the order data in the order management data storage unit 14, and manages the progress of the prescription drug purchase application based on the order data. Furthermore, the prescription drug order management system 1 includes a medication instruction management unit 133 that generates medication instruction data including the date and time of remote medication instruction via two-way communication to the patient corresponding to the order data generated by the order data management unit 132, and manages the implementation status of the remote medication instruction based on the medication instruction data, and a delivery management unit 134 that generates delivery data regarding the delivery of prescription drugs included in the prescription data corresponding to the order data, and outputs the delivery data to an external server.
As a result, the prescription drug order management system 1 can accommodate remote medication instructions and reduce the workload of pharmacies.

4. Operation of the Prescription Drug Order Management System (4.1) Prescription Drug Order Management Method Next, an example of a prescription drug order management method according to this embodiment will be described with reference to Fig. 6. Fig. 6 is a flowchart illustrating an example of a prescription drug order management method according to this embodiment. In this example, a case will be described in which confirmation of the original prescription corresponding to the order data is performed before the delivery management unit 134 generates delivery data.
First, the data acquisition unit 11 acquires prescription data and order data (step S101). The prescription data and order data may be acquired at approximately the same time by the data acquisition unit 11, or may be acquired with a time lag. Upon acquiring the prescription data, the prescription data acquisition unit 111 outputs a notification indicating that the prescription data has been received to the order management control unit 13, and the order data acquisition unit 112 outputs the acquired order data to the order management control unit 13.

The patient management unit 131 in the order management control unit 13 registers and updates patient data based on the order data output from the order data acquisition unit 112 to the order management control unit 13 (S102).

For example, when new patient data is registered, the patient management unit 131 determines whether an existing record exists in the patient table t401 of the order management data storage unit 14. The patient management unit 131 obtains the patient number attached to the received patient data and searches the patient table t401 based on the patient number. If the search returns one or more results for that patient number, the patient management unit 131 determines that an existing record exists in the patient table t401 for the patient indicated by the received patient data, and updates the data of the record in the patient table t401 (the record with the matching patient number) with the received patient data.

On the other hand, if the search result of the patient table t401 relating to the received patient data is zero, the patient management unit 131 determines that there are no existing records in the patient table t401, and registers a new record based on the received patient data in the patient table t401.
The received patient data includes registration desire flag data indicating whether or not the patient data is desired to be registered in the prescription order receiving system 1. When the registration desire flag data is a value (e.g., "1") indicating that the patient data is desired to be registered, the patient management unit 131 newly stores the received patient data in the order management data storage unit 14 (specifically, the patient table t401).

The order data management unit 132 in the order management control unit 13 generates order data based on the output of a notification (prescription reception notification) to the order management control unit 13 indicating that prescription data has been received, and the output of order data from the order data acquisition unit 112 to the order management control unit 13 (step S103).

Specifically, when prescription data is output from the order data acquisition unit 112 to the order management control unit 13 via the processor 501, the order data management unit 132 stores the order data as a new record in the order management data storage unit 14 (specifically, order table t403). Furthermore, when a prescription reception notification is output to the order management control unit 13, the order data management unit 132 acquires prescription data corresponding to the new order data stored in the order table t403 from the prescription data storage unit 12. The order data management unit 132 stores the contents of the acquired prescription data as a new record in the order management data storage unit 14 (specifically, received prescription table t402). The order data management unit 132 can identify prescription data corresponding to order data based on, for example, the patient's name and medical institution name in the order data, the date and time the order data was received, etc.

The order data management unit 132 also generates the order data shown in Figure 5 based on the prescription data and order data newly stored in the order management data storage unit 14, and stores this as a new record in the order data table t404 of the order management data storage unit 14. At this time, the order data management unit 132 sets the progress data in the generated order data (the "progress status" data shown in Figure 5) to "order completed."

Once the order data is generated, the medication instruction management unit 133 of the order management control unit 13 then executes a medication instruction date data generation process to generate medication instruction data including the date and time of remote medication instruction via two-way communication to the patient corresponding to the generated order data (step S200). In the medication instruction data generation process, the date and time of remote medication instruction is determined, and medication instruction data is generated to notify the patient of the date and time of implementation. Details of the medication instruction data generation process will be described later.

Once the medication instruction date data is generated, the medication instruction management unit 133 transmits the medication instruction date data to the applicant terminal device 72 (step S104). Specifically, the medication instruction management unit 133 outputs the generated medication instruction date data to the data output unit 16. The data output unit 16 outputs the input medication instruction date data to the applicant terminal device 72. This notifies the user of the applicant terminal device 72 (e.g., the patient who is the target of remote medication instruction) of the date and time of medication instruction implementation. At this time, the medication instruction management unit 133 also outputs a notification to the order data management unit 132 that the medication instruction date data has been sent to the applicant terminal device 72, along with the order number that identifies the order data. This causes the order data management unit 132 to extract the order data from the order data table t404 based on the order number, and set the progress data in the order data (the "progress status" data shown in Figure 5) to "medication instruction reservation completed."

In this way, in the prescription drug order management system 1 according to this embodiment, order data includes patient data, and the medication instruction management unit 133 determines the date and time for remote medication instruction for the patient identified by the patient data included in the newly generated order data (order data with progress data of "order completed"), generates medication instruction date data including the implementation date and time, and the data output unit 16 outputs the medication instruction date data to the applicant terminal device 72. This enables the prescription drug order management system 1 to handle remote medication instruction and reduce the workload on the pharmacy related to determining the date for remote medication instruction and notifying the patient.

Next, the order data management unit 132 confirms the completion of the medication instruction implementation (step S105). Based on the input of the medication instruction completion notification indicating that the remote medication instruction has been implemented at the pharmacy, the order data management unit 132 updates the progress data in the order data (the "progress status" data shown in FIG. 5) from "medication instruction reservation completed" to "medication instruction implementation completed."
The medication instruction completion notice may be data input from the pharmacy terminal device 73 by the pharmacist who provided the remote medication instruction, and may be acquired by the data acquisition unit 11 via the network 9 and output to the order data management unit 132. The medication instruction completion notice may also be data input from the applicant terminal device 72 by the patient who received the remote medication instruction, and may be acquired by the data acquisition unit 11 via the network 9 and output to the order data management unit 132.
In addition, when remote medication instructions are performed using the data acquisition unit 11 and data output unit 16 (of the order management server 3) communication I/F 508 of the prescription drug order management system 1, the data acquisition unit 11 or the data output unit 16 may generate a medication instruction completion notification based on the communication history stored in a specified memory area (e.g., RAM 503) of the order management server 3 and output it to the order data management unit 132.

In addition, the order data management unit 132 may send a medication instruction alert notification to the pharmacy terminal device 73 via the data output unit 16 if the medication instruction implementation date and time has passed for order data with progress data of "medication instruction reservation completed." The medication instruction alert notification may include data such as the medication instruction implementation date, patient name, and order number. This allows the pharmacist, who is the user of the pharmacy terminal device 73, to be warned that the medication instruction implementation date and time has passed, and to be prompted to implement remote medication instruction for the patient corresponding to the order indicated by the medication instruction alert notification.

The order data management unit 132 then confirms that the pharmacy has completed dispensing the prescription drug indicated by the prescription data corresponding to the order data (step S106). Based on the input of a dispensing completion notification indicating that the pharmacist has dispensed the prescription drug related to the prescription data and audited the dispensing (final audit) at the pharmacy, the order data management unit 132 updates the progress data in the order data (the "progress status" data shown in Figure 5) from "medication instructions completed" to "dispensing completed." The dispensing completion notification is data entered from the pharmacy terminal device 73 by the pharmacist who performed the dispensing, and is acquired by the data acquisition unit 11 via the network 9 and output to the order data management unit 132.

Next, the order data management unit 132 checks the original prescription corresponding to the order data for which the progress data was updated to "dispensing completed" in step S106 (step S107). Specifically, the order data management unit 132 checks whether the original prescription corresponding to the order data (dispensed order data) or prescription data (data equivalent to the original prescription) sent from the medical institution terminal device 71 has been acquired, and if so, updates the progress data in the dispensed order data (the "progress status" data shown in Figure 5) from "dispensing completed" to "prescription confirmation completed."

For example, the order data management unit 132 extracts data on whether the original has been obtained from the dispensed order data from the order data table t404, and if the data on whether the original has been obtained is a value indicating that the original has been obtained (for example, "1"), the order data management unit 132 updates the progress data in the order data (the "progress status" data shown in Figure 5) from "dispensing completed" to "prescription confirmation completed."
For example, when prescription data with a prescription number that matches the prescription number in the order data is stored in the medical institution data storage area of the prescription data storage unit 12, the order data management unit 132 determines that data corresponding to the original prescription has been acquired and sets the data indicating whether the original has been acquired to "1." Furthermore, when data indicating that the original prescription has been sent to the pharmacy by mail or the like is input from the pharmacy terminal device 73, the order data management unit 132 sets the data indicating whether the original has been acquired to "1." The value of the data indicating whether the original has been acquired remains "0" until the original or prescription data sent from the medical institution terminal device 71 is acquired.

Next, the delivery management unit 134 of the order management control unit 13 executes a delivery data generation process to generate delivery data corresponding to the order data (order data awaiting delivery) whose progress data has been updated to "Prescription confirmation completed" (step S300). The delivery data generation process will be described in detail below.

Next, the delivery management unit 134 outputs the delivery data of the record in the delivery table t408 corresponding to the order data awaiting delivery, generated in step S300, to the delivery company server 53 via the data output unit 16 (step S108). This causes the delivery company server 53 to generate delivery label data based on the delivery data, and transmits the generated delivery label data to the prescription drug order management system 1. After acquiring the delivery label data, the data acquisition unit 11 transmits the delivery label data to a printer (not shown) connected via a network to the order management server 3 on which the prescription drug order management system 1 operates. This causes the printer to print a delivery label. Pharmacy staff simply affix the delivery label to the packaging material containing the prescription drugs by the time the delivery company's delivery person picks up the prescription drugs.
In this way, in the prescription drug order management system 1, the delivery data generated by the delivery management unit 134 is output to the delivery company server 53, thereby significantly reducing the burden of delivery work at pharmacies.

The order data management unit 132 then confirms that the collection of the prescription medications by the delivery company's delivery person has been completed (step S109). Based on the input of the collection completion notification indicating that the prescription medications have been collected, the order data management unit 132 updates the progress data in the order data awaiting delivery (the "progress status" data shown in Figure 5) from "prescription confirmation completed" to "shipment completed." The collection completion notification may be data entered from the pharmacy terminal device 73 by the pharmacy staff member who performed the delivery, or may be data sent from the server of the delivery company that collected the prescription medications (delivery company server 53). The collection completion notification is acquired by the data acquisition unit 11 via the network 9 and output to the order data management unit 132.

Next, the order data management unit 132 confirms that the delivery of the prescription drug to the patient by the delivery person of the delivery company has been completed (step S110). Based on the input of the delivery completion notification indicating that the prescription drug has been delivered, the order data management unit 132 updates the progress data in the order data (delivered order data) whose progress data is "shipped" from "shipped" to "delivered." The delivery completion notification may be data sent from the server of the delivery company that delivered the prescription drug (delivery company server 53), or data input from the applicant terminal device 72 whose user is the patient who received the prescription drug or the patient's family member or caregiver. The delivery completion notification is acquired by the data acquisition unit 11 via the network 9 and output to the order data management unit 132.

In this way, the prescription drug order management method of this embodiment acquires prescription data indicating the contents of the prescription, order data including application data related to the prescription drug purchase application indicated by the prescription data and patient data for the patient for whom the prescription is to be issued, and stores the prescription data and order data. Furthermore, order data including the order data is generated, the order data is stored in association with the prescription data, and the progress of the prescription drug purchase application is managed based on the order data. Furthermore, medication instruction data including the date and time of remote medication instruction via two-way communication for the patient corresponding to the order data is generated, and the implementation status of the remote medication instruction is managed based on the medication instruction data. Furthermore, delivery data related to the delivery of the prescription drug included in the prescription data corresponding to the order data is generated, and the delivery data is output to an external server. This enables the prescription drug order management system 1 to support remote medication instruction and reduce the workload of pharmacies.

The prescription drug order management method described in Figure 6 is merely an example, and the prescription drug order management method of the present invention is not limited to this. The execution order of each process in the prescription drug order management method and the timing of updating progress data may be determined in accordance with legal systems, etc. This allows operations within a pharmacy to be managed in a manner that is adapted to social conditions.
For example, in the above-described prescription drug order management method, the original prescription corresponding to the order data is confirmed (step S107) before the delivery data generation process (step S300), but the present invention is not limited to this. If legal systems, etc. do not require confirmation of the original prescription (or data equivalent to the original) before delivery of prescription drugs, the timing of confirmation of the original prescription may be after the delivery data generation process (step S300). In this case, confirmation of the original prescription (step S107) may be performed at any timing, for example, after the order data is created (step S103).
If the timing of confirming the original prescription is after the delivery data generation process (step S300), the delivery management unit 134 can generate delivery data for order data with progress data of "dispensing completed" (dispensed order data).

(4.1.1) Medication Instruction Date Data Generation Process Here, an example of the medication instruction data generation process (step S200) will be described in detail with reference to FIG.
<Medication instruction date determination process>
7 is a flowchart illustrating an example of the medication instruction data generation process (step S200) in the prescription drug order management method. As shown in FIG. 7, the medication instruction management unit 133 first acquires data from the order data table t404 (step S201). Here, the medication instruction management unit 133 extracts order data whose progress data is set to "order completed" from the order data table t404.

Next, the medication instruction management unit 133 acquires data related to the patient's request regarding the date and time for remote medication instruction (implementation date and time request data) and data related to the prescription validity period (prescription expiration date) from the extracted order data (step S202). Here, in this example, the implementation date and time request data is data indicating the date and time for which the patient does not want remote medication instruction to be implemented.
Next, the medication instruction management unit 133 extracts appointment status data for candidate dates that can be the dates and times for remote medication instruction based on the implementation date and time request data from the medication instruction appointment table t406 (step S203). At this time, the medication instruction management unit 133 extracts appointment status data for available appointment dates and times other than the dates and times indicated by the implementation date and time request data from the medication instruction appointment table t406. Here, the medication instruction management unit 133 can obtain multiple appointment status data that meet the conditions.
In addition to the condition "other than the date and time indicated by the implementation date and time request data," the medication instruction management unit 133 may set additional conditions when extracting appointment status data for candidate dates from the medication instruction appointment table t406. For example, the additional condition may be "within a specified period (e.g., within one week from now)." Here, the "specified period" in the additional condition may be a period within the prescription expiration date. Furthermore, the additional condition may be "a specified number of cases (e.g., any number between 5 and 10 cases)." Furthermore, the additional conditions are not limited to these, and various other conditions can be set. This allows the prescription drug order management system 1 to extract appointment status data for candidate dates that could be the implementation dates for remote medication instruction based on conditions appropriate for the situation of each pharmacy and the convenience of the patient.

Next, the medication instruction management unit 133 detects, from the acquired appointment status data for the candidate date, appointment status data for which the number of available appointments is one or more (step S204). The medication instruction management unit 133 sorts, for example, the multiple appointment status data in ascending order, and determines whether the data for the number of available appointments is one or more for each appointment status data.
Next, the medication instruction management unit 133 determines the available appointment date and time in the appointment status data detected in step S204 as the medication instruction implementation date and registers it in the medication instruction management table t405 (step S205). At this time, the medication instruction management unit 133 also outputs the determined medication instruction implementation date and the order number that identifies the order data to the order data management unit 132. This allows the order data management unit 132 to update the medication instruction implementation date in the order data for that order number in the order data table t404.

In this way, in the prescription drug order management system 1 of this embodiment, the order data includes implementation date and time request data indicating the patient's request for the implementation date and time of the remote medication instruction in the application data, and the medication instruction management unit 133 derives candidate implementation dates and times for the remote medication instruction based on the implementation date and time request data, and determines the implementation date based on the candidate implementation dates and times and the number of appointments available for those candidate implementation dates and times. This allows the prescription drug order management system 1 to handle remote medication instruction and reduce the workload on pharmacies related to determining the implementation date and time for the remote medication instruction.

Next, when the medication instruction management unit 133 determines the medication instruction implementation date, it generates medication instruction date data (step S206).
The medication instruction date data is character string data for notifying the patient who is the target of remote medication instruction of the date on which medication instruction will be provided. The medication instruction date data is generated by the medication instruction management unit 133 based on fixed phrase data, which is character string data stored in advance in the order management data storage unit 14, and the medication instruction data in the medication instruction management table t405 in the order management data storage unit 14.

The medication instruction date data may also be created by reflecting the input contents on the pharmacy terminal device 73. In this case, the medication instruction management unit 133 generates display data for a medication instruction date data input screen for entering medication instruction date data and outputs it to the data output unit 16. The display data for the medication instruction date data input screen is generated based on the record (subject record) in the medication instruction management table t405 for the patient who is the subject of remote medication instruction. As a result, the display data for the medication instruction date data input screen is received by the communication I/F 508 of the pharmacy terminal device 73 via the network 9. Upon receiving the display data for the medication instruction date data input screen, the pharmacy terminal device 73 displays the order data display screen via a web browser running on the display device 507. The medication instruction date data input screen will now be described using Figure 8.

<Medication instruction date data entry screen>
FIG. 8 is a diagram showing an example of the medication instruction date data input screen 133A. As shown in FIG. 8, the medication instruction date data input screen 133A has a patient name display area 331, a text input area 332, and a confirm button 333. The patient name display area 331 displays, for example, the patient name data in the subject record of the medication instruction management table t405. The text input area 332 initially displays text information indicating the medication instruction date data automatically generated by the medication instruction management unit 133 based on the data in the subject record of the medication instruction management table t405. This eliminates the need for the user of the pharmacy terminal device 73 to create all of the text themselves, and allows them to easily create medication instruction date data by adding desired text information as needed.

Here, the order number data in the subject record is displayed as the "inquiry number" displayed in the text input area 332. This allows the user (e.g., patient) of the applicant terminal device 72 who has acquired the medication instruction date data to make an inquiry to a pharmacy or CS (customer support center) based on the order number.
Furthermore, the "medication instruction date and time" displayed in the text input area 332 displays the data on the date and time of medication instruction implementation determined in the processing of step S200. Also, as shown in FIG. 8 , the initial display content in the text input area 332 includes text information indicating that the pharmacy has completed accepting the prescription drug purchase application (e.g., "Your medication order has been accepted"). This notifies the user (e.g., patient) of the applicant terminal device 72 receiving the medication instruction date data that the order has been accepted and that remote medication instruction will be implemented, providing a sense of security to the user.

After the user of the pharmacy terminal device 73 has finished editing the medication instruction date data in the text input area 332, he or she simply presses the confirm button 333. This causes the input content of the text input area 332, i.e., the medication instruction date data, to be sent to the prescription drug order management system 1 and output to the medication instruction management unit 133 of the order management control unit 13 via the data acquisition unit 11.
The pharmacist who will provide remote medication instruction may be determined when the medication instruction date data is generated. For example, the medication instruction management unit 133 may determine the pharmacist who will provide remote medication instruction based on the work day data in the pharmacist table t407 and the available appointment dates and times in the medication instruction appointment table t406, and register the determined pharmacist as medication instruction data in the medication instruction management table t405.

(4.1.2) Delivery Data Generation Processing Here, the delivery data generation processing will be described in detail with reference to FIG.

<Delivery data generation process>
FIG. 9 is a flowchart illustrating the delivery data generation process in the prescription drug order management method. As shown in FIG. 9, the delivery management unit 134 first acquires data from the order data table t404 (step S301). Here, the delivery management unit 134 extracts, for example, order data whose progress data indicates "prescription confirmation completed" from the order data table t404 (order data awaiting delivery). As described above, the delivery management unit 134 may also extract order data whose progress data indicates "dispensing completed" from the order data table t404 as order data awaiting delivery, and use this as the target for generating delivery data. Here, the delivery management unit 134 acquires data on the desired delivery date and time and desired delivery method from the order data awaiting delivery.

Next, the delivery management unit 134 extracts patient data from the patient table t401 based on the patient number in the extracted order data (step S302). Here, the delivery management unit 134 obtains the patient's name and address data from the extracted patient data.

Next, the delivery management unit 134 generates delivery data based on data related to prescription drugs included in prescription data (ordered prescription data) corresponding to the order data awaiting delivery.
Specifically, the delivery management unit 134 determines the delivery type of the prescription drug based on the type of prescription drug included in the prescription data related to the order data awaiting delivery (step S303). Here, the type of prescription drug refers to, for example, data indicating the storage method of the prescription drug. Furthermore, the delivery type refers to, for example, the temperature (refrigerated or room temperature) at which the prescription drug is transported. This allows the prescription drug order management system 1 to easily determine the delivery type of the prescription drug. If the data on the storage method of the prescription drug indicates refrigerated storage, the delivery management unit 134 determines the delivery type of the prescription drug to be "refrigerated." Furthermore, if the data on the storage method of the prescription drug indicates storage other than refrigerated storage, the delivery management unit 134 determines the delivery type of the prescription drug to be "room temperature."

Next, the delivery management unit 134 determines the size of the packaging material for the prescription drug based on the quantity of the prescription drug included in the ordered prescription data corresponding to the order data awaiting delivery (step S304). Here, the size of the packaging material for the prescription drug may be the sum of the three sides of the packaging material in which the prescription drug is packed when it is delivered, or it may be the volume value. Furthermore, the dosage data in the ordered prescription data may be used as the quantity data for the prescription drug.

Next, the delivery management unit 134 determines a delivery method for the prescription drug included in the ordered prescription data corresponding to the order data awaiting delivery (step S305).
For example, the delivery management unit 134 determines the delivery method for the prescription drug based on the shape (prescription drug shape data in the received prescription data) or quantity (dosage data in the received prescription data) of the prescription drug included in the received prescription data corresponding to the order data awaiting delivery. Here, determining the delivery method for the prescription drug refers to determining one of various delivery methods (such as mailing, delivery to a designated location, in-store pickup, or hand delivery) to be used when delivering the prescription drug to the patient. For example, if the shape or quantity of the prescription drug is equal to or exceeds a predetermined threshold, the delivery management unit 134 may determine that mailing is not possible even if the patient's desired delivery method (the "delivery method request" in the received order data awaiting delivery) is mailing, and may select any delivery method other than mailing (such as hand delivery, delivery to a designated location, or in-store pickup). In this case, a priority may be assigned to the selected delivery method. The delivery management unit 134 may also determine the delivery method for the prescription drug based on the content of the prescription drug included in the received prescription data. For example, the delivery management unit 134 may determine the delivery method based on the type of prescription drug (such as name or drug code) included in the ordered prescription data. For example, if the ordered prescription data includes a prescription drug with a specific name, the delivery management unit 134 may determine the delivery method to be hand delivery. Furthermore, for example, the name of the specific prescription drug may be stored in the order management data storage unit 14. In this case, the delivery management unit 134 may extract the name of the specific prescription drug from the order management data storage unit 14 and determine whether it matches the name of the prescription drug included in the ordered prescription data.

The delivery management unit 134 may also determine a delivery method for the ordered prescription data corresponding to the order data awaiting delivery based on payment method data included in the order data awaiting delivery. Specifically, the delivery method may be determined based on the delivery method determined by the shape and quantity of the prescription drug and the content of the payment method data.
For example, if the content of the payment method data is "cash on delivery (COD)," the delivery management unit 134 determines the delivery method to be hand delivery, even if the "Delivery Method Request" of the order data awaiting delivery is a request other than "hand delivery." Also, even if the content of the payment method data is other than "cash on delivery" (such as "card,""banktransfer," or "payment by collection agency") and the "Delivery Method Request" of the order data awaiting delivery indicates "mailing," the delivery management unit 134 may determine the delivery method to be a delivery method other than "mailing," including hand delivery, if it is determined that mailing is impossible based on the shape or quantity of the prescription drug.
In addition, if the delivery method is not limited based on the shape, quantity, and payment method data of the prescription drug (for example, there are no restrictions such as not being able to post the drug or only handing it over in person), the delivery management unit 134 may determine the delivery method based on the "delivery method request" in the order data awaiting delivery.

Next, the delivery management unit 134 generates delivery data including the data acquired and determined in steps S301 to S305, and registers this data in the delivery table t408 together with the order number indicating the order data awaiting delivery (step S306).

In this way, the delivery management unit 134 generates delivery data based on data related to prescription drugs included in the ordered prescription data, which is the prescription data corresponding to the order data. This allows the prescription drug order management system 1 to reduce the workload on pharmacies related to generating delivery data for delivering prescription drugs.

5. Prescription Drug Order Management Program The prescription drug order management program executed by the prescription drug order management system 1 according to this embodiment will now be described. The prescription drug order management system 1 manages operations within the pharmacy related to the receipt of prescription drug purchase orders in accordance with a program that causes a computer to execute at least the following operations (a) to (f). The following program is non-temporarily recorded on a recording medium such as a hard disk drive or memory, or an optical disc such as a DVD or Blu-ray (registered trademark). The following program may be distributed via the Internet. Furthermore, the following program may be recorded on a cloud server and executed via the Internet.

(a) obtaining prescription data indicating the contents of the prescription, and order data including application data regarding an application to purchase the prescription drug indicated by the prescription data and patient data of the patient for whom the prescription is to be issued; (b) storing the prescription data and the order data; (c) generating order data based on the prescription data and the order data, storing the order data in a storage unit in association with the prescription data, and managing the progress of the application to purchase the prescription drug based on the order data; (d) generating medication instruction data including the date and time of implementation of remote medication instruction via two-way communication for the patient corresponding to the order data, and managing the implementation status of the remote medication instruction based on the medication instruction data; (e) generating delivery data regarding the delivery of the prescription drug included in the prescription data corresponding to the order data, and outputting the delivery data to an external server (delivery company server 53).

6. Modifications In the prescription drug order management system 1, the requested implementation date and time data is not limited to dates and times when the patient does not wish to receive remote medication instruction (unavailable dates and times).
For example, in the present invention, the implementation date and time request data may be the date and time at which the patient desires to receive remote medication guidance (desired implementation date and time). In this case, the medication guidance management unit 133 derives candidate implementation dates and times based on the desired implementation date and time indicated by the implementation date and time request data, and determines the implementation date and time for the remote medication guidance based on the candidate implementation dates and times and the number of reservations that can be made at the candidate implementation dates and times.
Specifically, the medication instruction management unit 133 extracts the appointment status data for the desired implementation date and time from the medication instruction appointment table t406. This extracts appointment status data for candidate dates that can be the implementation date and time for remote medication instruction based on the desired implementation date and time. The medication instruction management unit 133 detects appointment status data for the extracted candidate dates that allows one or more people to make an appointment, and determines the date for implementing medication instruction. Multiple dates and times may also be set as the desired implementation date and time. In this case, the medication instruction management unit 133 can obtain multiple appointment status data for dates and times that meet the patient's preferences.

Furthermore, the requested implementation date and time data may include both the unavailable date and time and the desired implementation date and time. In this case, for example, the medication instruction management unit 133 extracts appointment status data for candidate dates from the medication instruction appointment table t406 based on the data indicating the desired implementation date and time. If the number of extracted data is 0 (there is no candidate date corresponding to the desired implementation date and time), the medication instruction management unit 133 may extract appointment status data for available appointment dates and times other than the unavailable date and time from the medication instruction appointment table t406. In other words, in the present invention, the requested implementation date and time data may be data indicating at least one of the unavailable date and time or the desired implementation date and time. In other words, the medication instruction management unit 133 may derive candidate dates and times for remote medication instruction based on at least one of the unavailable date and time or the desired implementation date. In this case, the medication instruction management unit 133 may derive candidate dates and times that satisfy the additional conditions described above in addition to the conditions related to the unavailable date and time and the desired implementation date.
In the present invention, multiple dates and times may be set as the unavailable dates and times. In this case, the medication instruction management unit 133 extracts, from the medication instruction reservation table t406, reservation status data for available dates and times other than the dates and times indicated by the multiple requested date and time data (unavailable dates and times).

In the prescription drug order management system 1, the medication instruction data generation process (step S200) may involve a process of determining a specific pharmacist to be in charge of the remote medication instruction. For example, if the medication instruction management unit 133 determines that a patient receiving remote medication instruction has a specific disease based on the name of a medical institution included in the order data or the prescription data corresponding to the order data, the medication instruction management unit 133 may determine that a pharmacist who can handle the disease (e.g., has specialized knowledge) will be in charge of the remote medication instruction. In this case, the pharmacist table t407 may include data indicating whether the pharmacist can handle the specific disease.
In this way, the pharmacist table t407 of the order management data storage unit 14 stores multiple pieces of pharmacist data related to pharmacists working at pharmacies, and when the order data contains specific information (a specific medical institution name or prescription data with specific content), the medication instruction management unit 133 can select a specific pharmacist (a pharmacist who can handle a specific disease) from the multiple pieces of pharmacist data as the pharmacist to provide remote medication instruction. This allows the prescription drug order management system 1 to provide detailed instruction tailored to patients with specific diseases during remote medication instruction.

Furthermore, in the prescription drug order management system 1, when multiple pieces of order data correspond to the same patient, remote medication instructions for the multiple pieces of order data may be executed simultaneously. In this case, the medication instruction management unit 133 may determine the same date and time for the execution of medication instructions for the order data whose progress data is "order completed" and which have the same patient number or patient name (e.g., name and address) that identifies the patient.
Furthermore, in the prescription drug order management system 1, when the same patient corresponds to multiple order data, delivery data for the prescription drugs indicated by the prescription data related to the multiple order data may be generated together. In this case, the delivery management unit 134 may collectively generate delivery data for prescription drugs related to prescriptions for order data with the same patient name among the order data whose progress data is "prescription confirmation completed."

In addition, the prescription drug order management system 1 may manage order data collectively for multiple patients. In this case, the order data sent by the applicant terminal device 72 may include group management data indicating that order data is managed collectively for multiple patients. The group management data may include, for example, the names of multiple patients. When the order data includes group management data, the order data management unit 132 may associate the order data with the multiple patients indicated by the group management data. For example, the order data management unit 132 may add a group management number to the order data that is managed as a group. This allows the prescription drug order management system 1 to handle order data for multiple patients collectively when generating medication instruction date data and delivery data.

Although the embodiments of the present invention have been described above, the technical scope of the present invention is not limited to the technical scope described in the above-mentioned embodiments. Various modifications and improvements can be made to the above-mentioned embodiments, and it is clear from the claims that forms incorporating such modifications or improvements can also be included within the technical scope of the present invention.

1 Prescription drug order management system 3 Order management server 5 External device group 6 Remuneration examination system 7 Terminal device group 8 Drug master 9 Network 11 Data acquisition unit 12 Prescription data storage unit 13 Order management control unit 14 Order management data storage unit 15 Drug data storage unit 16 Data output unit 51 Receipt computer 52 Accounting server 53 Delivery company server 54 CS server 55 Settlement server 56 Wholesaler server 57 Marketing support server 71 Medical institution terminal device 72 Applicant terminal device 73 Pharmacy terminal device 74 CS terminal device 111 Prescription data acquisition unit 112 Order data acquisition unit 131 Patient management unit 132 Order data management unit 133 Medication instruction management unit 134 Delivery management unit 135 Inventory management unit 136 Order management unit 137 Inquiry management unit

Claims (17)

A prescription drug order management system that manages operations within a pharmacy related to receiving orders for prescription drug purchase applications,
a data acquisition unit that acquires prescription data indicating the contents of a prescription, application data regarding an application for purchase of the prescription drug indicated by the prescription data, and order data including patient data of the patient to whom the prescription is to be issued;
a storage unit that stores the prescription data and order data;
an order data management unit that generates order data based on the prescription data and the order data, stores the order data in the storage unit in association with the prescription data, and manages the progress of the purchase application based on the order data;
a medication instruction management unit that generates medication instruction data including the date and time of remote medication instruction provided to the patient via two-way communication corresponding to the order data, and manages the implementation status of the remote medication instruction based on the medication instruction data;
a delivery management unit that generates delivery data related to delivery of prescription drugs included in prescription data corresponding to the order data;
a data output unit that outputs the delivery data to an external server ,
The order data includes progress data indicating the progress status, which manages the progress of work in a plurality of units in accordance with the progress of work in the pharmacy,
the order data management unit manages the progress status by updating the progress data based on the medication instruction data and the delivery data corresponding to the order data.
Prescription drug order management system. A prescription drug order management system that manages operations within a pharmacy related to receiving orders for prescription drug purchase applications,
a data acquisition unit that acquires prescription data indicating the contents of a prescription, application data regarding an application for purchase of the prescription drug indicated by the prescription data, and order data including patient data of the patient to whom the prescription is to be issued;
a storage unit that stores the prescription data and order data;
an order data management unit that generates order data based on the prescription data and the order data, stores the order data in the storage unit in association with the prescription data, and manages the progress of the purchase application based on the order data;
a medication instruction management unit that generates medication instruction data including the date and time of remote medication instruction provided to the patient via two-way communication corresponding to the order data, and manages the implementation status of the remote medication instruction based on the medication instruction data;
a delivery management unit that generates delivery data related to delivery of prescription drugs included in prescription data corresponding to the order data;
a data output unit that outputs the delivery data to an external server,
The order data includes the patient data and implementation date/time request data indicating a patient's request regarding the implementation date/time of the remote medication guidance in the application data,
the implementation date and time request data is data indicating a date and time on which the patient does not wish to receive the remote medication guidance,
The medication instruction management department
deriving candidate implementation dates and times for the remote medication guidance for the patient indicated by the patient data included in the newly generated order data based on the implementation date and time request data, determining the implementation date and time for the remote medication guidance based on the candidate implementation date and time and the number of available appointments for the candidate implementation date and time, and generating medication guidance date data including the implementation date and time;
The data output unit outputs the medication instruction date data to a terminal device of the applicant of the purchase application. A prescription drug order management system that manages operations within a pharmacy related to receiving orders for prescription drug purchase applications,
a data acquisition unit that acquires prescription data indicating the contents of a prescription, application data regarding an application for purchase of the prescription drug indicated by the prescription data, and order data including patient data of the patient to whom the prescription is to be issued;
a storage unit that stores the prescription data and order data;
an order data management unit that generates order data based on the prescription data and the order data, stores the order data in the storage unit in association with the prescription data, and manages the progress of the purchase application based on the order data;
a medication instruction management unit that generates medication instruction data including the date and time of remote medication instruction provided to the patient via two-way communication corresponding to the order data, and manages the implementation status of the remote medication instruction based on the medication instruction data;
a delivery management unit that generates delivery data related to delivery of prescription drugs included in prescription data corresponding to the order data;
a data output unit that outputs the delivery data to an external server,
The storage unit stores a plurality of pharmacist data related to pharmacists working at the pharmacy,
When the medication instruction management unit determines that the patient has a specific disease based on the inclusion of specific information in the order data, it determines a pharmacist who can handle the specific disease from the plurality of pharmacist data as a pharmacist who will perform the remote medication instruction.
Prescription drug order management system. A prescription drug order management system that manages operations within a pharmacy related to receiving orders for prescription drug purchase applications,
a data acquisition unit that acquires prescription data indicating the contents of a prescription, application data regarding an application for purchase of the prescription drug indicated by the prescription data, and order data including patient data of the patient to whom the prescription is to be issued;
a storage unit that stores the prescription data and order data;
an order data management unit that generates order data based on the prescription data and the order data, stores the order data in the storage unit in association with the prescription data, and manages the progress of the purchase application based on the order data;
a medication instruction management unit that generates medication instruction data including the date and time of remote medication instruction provided to the patient via two-way communication corresponding to the order data, and manages the implementation status of the remote medication instruction based on the medication instruction data;
a delivery management unit that generates delivery data related to delivery of prescription drugs included in prescription data corresponding to the order data;
a data output unit that outputs the delivery data to an external server,
The delivery management unit is capable of determining the delivery method of the prescription drug as the delivery method desired by the patient, and when the shape or quantity of the prescription drug included in the ordered prescription data, which is the prescription data corresponding to the order data, satisfies a predetermined condition, determines the delivery method of the prescription drug to be a specific delivery method regardless of the delivery method desired by the patient and generates the delivery data.
Prescription drug order management system. A prescription drug order management system that manages operations within a pharmacy related to receiving orders for prescription drug purchase applications,
a data acquisition unit that acquires prescription data indicating the contents of a prescription, application data regarding an application for purchase of the prescription drug indicated by the prescription data, and order data including patient data of the patient to whom the prescription is to be issued;
a storage unit that stores the prescription data and order data;
an order data management unit that generates order data based on the prescription data and the order data, stores the order data in the storage unit in association with the prescription data, and manages the progress of the purchase application based on the order data;
a medication instruction management unit that generates medication instruction data including the date and time of remote medication instruction provided to the patient via two-way communication corresponding to the order data, and manages the implementation status of the remote medication instruction based on the medication instruction data;
a delivery management unit that generates delivery data related to delivery of prescription drugs included in prescription data corresponding to the order data;
a data output unit that outputs the delivery data to an external server,
The order data includes payment method data indicating a payment method selected by the purchaser and a delivery method request indicating a delivery method desired by the patient,
The delivery management unit
generating the delivery data based on data relating to prescription drugs included in ordered prescription data, which is prescription data corresponding to the order data;
A prescription drug order management system that, when the payment method data indicates a specific payment method, determines the delivery method for the prescription drug included in the ordered prescription data among the delivery data to be a predetermined delivery method, regardless of the delivery method indicated by the delivery method request. A prescription drug order management system that manages operations within a pharmacy related to receiving orders for prescription drug purchase applications,
a data acquisition unit that acquires prescription data indicating the contents of a prescription, application data regarding an application for purchase of the prescription drug indicated by the prescription data, and order data including patient data of the patient to whom the prescription is to be issued;
a storage unit that stores the prescription data and order data ;
an order data management unit that generates order data based on the prescription data and the order data, stores the order data in the storage unit in association with the prescription data, and manages the progress of the purchase application based on the order data;
a medication instruction management unit that generates medication instruction data including the date and time of remote medication instruction provided to the patient via two-way communication corresponding to the order data, and manages the implementation status of the remote medication instruction based on the medication instruction data;
a delivery management unit that generates delivery data related to delivery of prescription drugs included in prescription data corresponding to the order data;
a data output unit that outputs the delivery data to an external server.
Prescription drug order management system. the order data includes progress data indicating the progress status,
the order data management unit manages the progress status by updating the progress data based on the medication instruction data and the delivery data corresponding to the order data.
The prescription drug order management system according to any one of claims 2 to 6 . The storage unit stores a plurality of pharmacist data related to pharmacists working at the pharmacy,
A prescription drug order management system as described in any one of claims 1 , 2 and 4 to 6, wherein the medication instruction management unit determines a specific pharmacist from multiple pharmacist data as the pharmacist to perform the remote medication instruction when the order data contains specific information. The prescription drug order management system according to claim 1 , wherein the delivery management unit generates the delivery data based on data relating to prescription drugs included in ordered prescription data, which is prescription data corresponding to the order data. The prescription drug order management system according to claim 9 , wherein the delivery management unit determines a delivery type of the prescription drug based on the type of the prescription drug included in the received prescription data. The prescription drug order management system according to claim 9 or 10 , wherein the delivery management unit determines the size of packaging material for the prescription drug based on the amount of the prescription drug included in the received prescription data. The prescription drug order management system according to claim 9 , wherein the delivery management unit determines a delivery method for the prescription drug based on the shape or quantity of the prescription drug included in the received prescription data. The order data includes payment method data indicating the payment method selected by the applicant of the purchase offer,
The prescription drug order management system according to claim 9 , wherein the delivery management unit determines a delivery method for the prescription drug included in the received prescription data based on the payment method data. A prescription drug order management program that manages operations within a pharmacy related to receiving orders for prescription drug purchase applications,
Computer,
a data acquisition unit that acquires prescription data indicating the contents of a prescription, application data regarding an application for purchase of the prescription drug indicated by the prescription data, and order data including patient data of a patient to whom the prescription is to be issued;
a storage unit for storing the prescription data and order data;
an order data management unit that generates order data including the order data, stores the order data in the storage unit in association with the prescription data, and manages the progress of the purchase application based on the order data;
a medication instruction management unit that generates medication instruction data including the date and time of remote medication instruction provided to a patient via two-way communication corresponding to the order data, and manages the implementation status of the remote medication instruction based on the medication instruction data;
a delivery management unit that generates delivery data related to delivery of prescription drugs included in prescription data corresponding to the order data and outputs the delivery data to an external server;
The order data includes progress data indicating the progress status, which manages the progress of work in a plurality of units in accordance with the progress of work in the pharmacy,
The order data management unit manages the progress status by updating the progress data based on the medication instruction data and delivery data corresponding to the order data . A prescription drug order management program that is executed on a single server device and manages operations within a pharmacy related to receiving orders for prescription drug purchase applications,
The one server device,
a data acquisition unit that acquires prescription data indicating the contents of a prescription, application data regarding an application for purchase of the prescription drug indicated by the prescription data, and order data including patient data of a patient to whom the prescription is to be issued;
a storage unit for storing the prescription data and order data;
an order data management unit that generates order data including the order data, stores the order data in the storage unit in association with the prescription data, and manages the progress of the purchase application based on the order data;
a medication instruction management unit that generates medication instruction data including the date and time of remote medication instruction provided to a patient via two-way communication corresponding to the order data, and manages the implementation status of the remote medication instruction based on the medication instruction data;
a delivery management unit that generates delivery data related to delivery of the prescription drug included in the prescription data corresponding to the order data and outputs the delivery data to an external server;
It acts as a prescription drug order management program. The computer
Obtain prescription data indicating the contents of the prescription, application data regarding an application for purchase of the prescription drug indicated by the prescription data, and order data including patient data of the patient to whom the prescription is to be issued;
storing the prescription data and order data;
generating order data based on the prescription data and the order data, storing the order data in association with the prescription data, and managing the progress of the purchase application based on the order data;
generating medication instruction data including a date and time of remote medication instruction provided to a patient via two-way communication corresponding to the order data; and managing the execution status of the remote medication instruction based on the medication instruction data;
generating delivery data relating to delivery of the prescription drug included in the prescription data corresponding to the order data, and outputting the delivery data to an external server;
Furthermore, the order data includes progress data indicating the progress status, which manages the progress of work in multiple units in accordance with the progress of work in the pharmacy,
A prescription drug order management method for managing the progress status by updating the progress data based on the medication instruction data and the delivery data corresponding to the order data . A prescription drug order management method using a server device that provides a system for managing operations within a pharmacy related to receiving orders for prescription drug purchase applications, comprising:
The one server device,
Obtain prescription data indicating the contents of the prescription, application data regarding an application for purchase of the prescription drug indicated by the prescription data, and order data including patient data of the patient to whom the prescription is to be issued;
storing the prescription data and order data;
generating order data based on the prescription data and the order data, storing the order data in association with the prescription data, and managing the progress of the purchase application based on the order data;
generating medication instruction data including a date and time of remote medication instruction provided to a patient via two-way communication corresponding to the order data; and managing the execution status of the remote medication instruction based on the medication instruction data;
Generate delivery data regarding delivery of the prescription drug included in the prescription data corresponding to the order data, and output the delivery data to an external server.
Prescription drug order management methods.