Information processing system, program, and information processing method

Abstract

To provide an information processing system that can improve the business response capabilities of pharmacies. [Solution] An information processing system that provides online medication instructions at a pharmacy store is provided, which includes a server, a patient terminal at the pharmacy store, and a pharmacist terminal at a location different from the pharmacy store, and the server performs identification processing, request processing, and call processing, and in the identification processing, the server acquires data, and in the request processing, the medication instruction task corresponding to the data is presented on the pharmacist terminal, and in the call processing, the pharmacist terminal that selected the presented medication instruction task is connected to the patient terminal so that they can communicate, and the data includes at least one of patient identification information of patients who visit the pharmacy store, patient prescription drug receipt information, audit information, prescription information, drug information, drug history information, medicine notebook information, dispensing record information, medicine bag information, receipt information, receipt certificate details information, reception number information, test result information, health check result information, upper limit management table information, and device output information.

Description

[Technical Field]

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

[0002] Patent Document 1 describes a medication instruction support device for providing highly accurate medication instruction in a pharmacy. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7323664 Summary of the Invention [Problem to be solved by the invention]

[0004] Pharmacies have limited human resources, which can lead to delays in responding to business operations, for example, when the store is crowded.

[0005] An object of the present invention is to provide an information processing system that can improve the business response capabilities of a pharmacy store. [Means for solving the problem]

[0006] According to the present invention, there is provided an information processing system for providing online medication instructions at a pharmacy store, comprising a server, a patient terminal at the pharmacy store, and a pharmacist terminal at a location different from the pharmacy store, wherein the server performs identification processing, request processing, and call processing, wherein in the identification processing, the server acquires data, and in the request processing, a medication instruction task corresponding to the data is presented on the pharmacist terminal, and in the call processing, the pharmacist terminal from which the presented medication instruction task was selected is connected to the patient terminal so that they can communicate, and the data includes at least one of patient identification information of patients who visit the pharmacy store, patient prescription drug receipt information, audit information, prescription information, drug information, drug history information, medicine notebook information, dispensing record information, medicine bag information, receipt information, receipt certificate details information, reception number information, test result information, health check result information, upper limit management table information, and device output information.

[0007] According to the present invention, online medication instruction can be effectively introduced within a pharmacy store, thereby improving the business response capabilities of the pharmacy store. [Brief explanation of the drawings]

[0008] [Figure 1] Fig. 1A shows an example of the overall configuration of an information processing system 1 according to an embodiment. Fig. 1B shows an example of the hardware configuration of each server 2 (2a to 2d) and each terminal 3 (3a to 3d) according to an embodiment. [Figure 2] 2 is a block diagram illustrating a schematic example of the processing contents of the server 2 and the terminal 3 and the work flow of each staff member in the embodiment. FIG. [Figure 3] 2 is a diagram illustrating a schematic example of functions and screens provided by a server 2c as a Web application. FIG. [Figure 4] A screen 10 in FIG. 4A shows an example of a screen for sending an inspection image or the like, and FIG. 4B shows examples of screens 11, 12, and 13 for presenting related functions related to inspection images or the like. [Figure 5] A screen 20 in FIG. 5A shows an example of a request receiving screen of the pharmacist terminal 3c2, and a screen 30 in FIG. 5B shows an example of a call waiting screen of the pharmacist terminal 3c2. [Figure 6] A screen 40 in FIG. 6A shows an example of a call screen on the pharmacist terminal 3c2, and a screen 42 in FIG. 6B shows an example of a call screen on the patient terminal 3c1. [Figure 7] Screen 60 shows another example of the call screen of the pharmacist terminal 3c2 (call screen that also serves as a call standby screen). [Figure 8] This is a screen 70 that displays a list of information on patients who have visited a pharmacy and been accepted. DETAILED DESCRIPTION OF THE INVENTION

[0009] Preferred embodiments of the present invention are described in detail below with reference to the drawings. Note that the embodiments described below are preferred specific examples of the present invention, and therefore various technically preferable limitations are applied, but the scope of the present invention is not limited to these aspects unless otherwise specified in the following description to the effect that the present invention is limited.

[0010] 1. Information processing system configuration 1.1. Overall structure Hereinafter, the pharmacy where the patient visits will be simply referred to as the "own pharmacy." The information processing system 1 of the embodiment in FIG. 1A provides online medication guidance to the patient visiting the pharmacy (own pharmacy) by a pharmacist at a location different from the pharmacy (own pharmacy) (e.g., another pharmacy or a medication guidance center). As shown in FIG. 1, the information processing system 1 of the embodiment includes, as an example, multiple servers 2 (2a-2d) and multiple terminals 3 (3a, 3b1, 3b2, 3c1, 3c2, 3cc1, 3d). Each server 2 and each terminal 3 are connected via a communication network 4. The communication network 4 is not limited to a specific network, and the Internet, an intranet, a LAN, or any combination thereof may be used.

[0011] As an example, among the multiple servers 2 (2a to 2d), server 2a provides a medical receipt computer system (medical accounting system), server 2b provides an electronic medical history system, server 2c provides an online medication instruction system, and server 2d provides a cash register system (e.g., a POS system, etc.). Servers 2a to 2d may be independent of each other, or some or all of them may be linked to each other or integrated.

[0012] The multiple terminals 3 include, for example, terminals 3 within the pharmacy store (own store) and terminals 3 at locations other than the store (e.g., other stores, or optional facilities such as a medication instruction center). The terminals 3 within the store specifically include, for example, a receipt computer terminal 3a at the counter, a patient terminal 3c1, terminals 3 in the dispensing room (medication history terminal 3b1, data terminal 3cc1), and a cash register terminal 3d. The terminals 3 at locations other than the store include, for example, a pharmacist terminal 3c2 and a medication history terminal 3b2. For example, any hardware terminal within the pharmacy store (own store) or a location other than the store may log in (connect) to each server 2, and thereby operate as each terminal 3. In an embodiment, the medication history terminals 3b1 and 3b2 can refer to common medication history data, for example, via a cloud medication history system.

[0013] 1.2.Hardware Configuration Please refer to Figure 1B. For convenience of explanation, the server 2 and the terminal 3 are collectively referred to as "computers" herein. As shown in Figure 1B, in one embodiment, each of the computers 2 and 3 includes a control unit 51, a storage unit 52, a communication unit 53, an input unit 54, an output unit 55, and a timing unit 56. The hardware components of the computers 2 and 3 are connected to each other via a bus.

[0014] The control unit 51 has a physically structured circuit. This circuit executes each process for realizing a desired function according to the code or instructions contained in a program. The control unit 51 is realized, for example, by a data processing device built into hardware. Therefore, the control unit 51 may be expressed as a control circuit. The control unit 51 may be, for example, a central processing unit (CPU), a microprocessor, a processor core, a multiprocessor, an application-specific integrated circuit (ASIC), or a field programmable gate array (FPGA).

[0015] The storage unit 52 has the function of storing various programs and various data required for the operation of the computers 2 and 3. Here, the storage unit 52 is described without distinguishing between an internal storage device and an external storage device, and various storage media such as a hard disk drive (HDD), a solid state drive (SSD), a flash memory, a random access memory (RAM), and a read only memory (ROM) can be arbitrarily adopted for the storage unit 52. The storage unit 52 may also be referred to as a memory.

[0016] Each of the computers 2 and 3 can store a program in the storage unit 52. By executing this program, the control unit 51 realizes various functions of each of the computers 2 and 3.

[0017] The communication unit 53 transmits and receives various data between the computers 2 and 3 (or between these and any other computer) via the communication network 4. The communication may be wired or wireless, and any communication protocol may be employed. The communication unit 53 transmits various data to various devices in accordance with instructions from the control unit 51. The communication unit 53 also receives various data via the communication network 4 and transmits it to the control unit 51. The communication unit 53 can also receive data transmitted from other terminals or other systems via the communication network 4.

[0018] The input unit 54 is a device for inputting various operations to the computers 2 and 3. The output unit 55 is a device for outputting the processing results of the computers 2 and 3. The input unit 54 and the output unit 55 may be separate devices or may be an integrated device.

[0019] The input unit 54 is realized by any one of or a combination of all types of devices that can accept input from a user (such as an operator of each computer) and transmit information related to the input to the control unit 51. The input unit 54 may be, for example, a touch panel, a touch display, hardware keys such as a keyboard, a pointing device such as a mouse, a camera (operation input via moving images), a microphone (operation input by voice), a headset, or a bone conduction microphone. The input unit 54 may also include an audio input unit or an imaging unit. The audio input unit is capable of inputting audio data and includes a microphone, etc. The imaging unit is used to acquire image data (still image data, moving image data, three-dimensional image data, etc.; the same applies below).

[0020] The output unit 55 is realized by any one of or a combination of all types of devices that can output the processing results processed by the control unit 51. The output unit 55 may be a display, a touch panel, a touch display, a speaker (audio output), a directional speaker, a headset, a bone conduction earphone, a printer, or the like. The display, touch panel, or touch display serving as the output unit 55 is realized by any one of or a combination of all types of devices that can display according to display data written in a frame buffer (memory).

[0021] For example, when the input unit 54 is a touch panel, the input unit 54 and a display unit serving as the output unit 55 may be disposed opposite each other with approximately the same size and shape.

[0022] The timekeeping unit 56 is, for example, a clock built into each of the computers 2 and 3, and outputs time information (timekeeping information). The timekeeping unit 56 includes, for example, a clock that uses a crystal oscillator.

[0023] The above hardware configuration is merely an example. Each server 2 in the embodiment may be provided as a dedicated physical server or as an arbitrary virtual server. This point will be explained in more detail in the modified example described later.

[0024] 2. Operation of the information processing system An example of a business flow and system processing according to an embodiment will be described below with reference to FIG. 2. In FIG. 2, interactions between each server 2 and each terminal 3 correspond to system processing. Interactions between each terminal 3 and a human correspond to any user interface (UI) input / output. This UI input / output includes any input operation and any output (e.g., visual, auditory, or tactile notification via a screen or sound). Note that FIG. 2 illustrates, as an example, the interaction between servers 2a and 2b, simply and schematically illustrated with arrows. It should be noted that the present invention is not limited to a specific server interaction method, and any interaction can be employed. Typically, various types of inter-server interaction technology can be employed depending on factors such as differences in manufacturers and whether or not the system is cloud-based, and the interaction can become complex. Inter-server interaction can be established as needed. As another example, one or both of servers 2a and 2b may be linked to server 2c, and additional server 2d may also be linked.

[0025] 2, for those corresponding to system processing (input / output or calculation processing), a program read from the storage unit 52 is executed by the control unit 51, thereby realizing functional units of each process (e.g., a recognition unit, a request unit, a guidance unit, and a counting unit) on the control unit 51. Also, for detailed examples of each screen (screens 10, 20, 30, 40, 42, and screen 60 of a modified example) of each terminal 3 (3b1 to 3c2), please refer to the section "3. Examples of terminal functions, etc." described later.

[0026] Please note that the description of the embodiment is merely an example and various modifications are possible. The order or content of steps S1 to S31 below can be replaced, integrated, or omitted as necessary, and other steps can be inserted between steps. For convenience, the accounting system server 2d (see FIG. 1) is not shown in FIG. 2.

[0027] 2.1. Description of steps S0 to S12b (including identification process S12b) First, please pay attention to step S0 in the upper right corner of Figure 2. A patient who visits a pharmacy presents various information at the pharmacy counter, and a pharmacy clerk inputs the information into the receipt computer terminal 3a accordingly (see S0 and S1). Specifically, for example, a paper prescription, a reception card, an insurance card, etc. may be submitted to the pharmacy counter. Alternatively, for example, a My Number card may be submitted and an electronic prescription may be obtained via the My Number. As a result, the prescription information and the patient's personal information (e.g., address, name, date of birth, insurance number, My Number, etc.) are acquired by the server 2a (receipt computer) (see S2). The server 2a (receipt computer) issues sequential reception numbers, which are output to the receipt computer terminal 3a (see S3). The pharmacy clerk acquires the reception number (see S4). The pharmacy clerk can guide the patient based on the reception number. The reception number may be issued by an automatic ticket issuing machine or the like. At least a part of the receipt computer input work may be outsourced, and prescriptions and the like may be input to the server 2a from another remote terminal connected via the communication network 4.

[0028] In this embodiment, for example, in step S0, the "presence or absence of online medication instruction" of the visiting patient is acquired. A specific example of this "acquisition of presence or absence" is "acquisition of preference." In "acquisition of preference," the visiting patient is asked by any means whether or not they would like to receive online medication instruction, and their response is acquired.

[0029] For example, when a patient visits a pharmacy and receives medical treatment at a hospital, the prescription corresponding to that treatment may state "online support" or "online medication instruction requested." This statement indicates whether the patient can receive online medication instruction at home or elsewhere without visiting the pharmacy. In other words, based on this statement, it is possible to determine whether dispensing, instruction, and administration of medication are possible without the original prescription. In contrast, in the embodiment (in-store online medication instruction), the store receives the original prescription as usual, and provides online medication instruction to patients visiting the pharmacy within the store. The online medication instruction in the embodiment differs from the scenarios anticipated by the "online support" statement on the prescription. Unless other regulations (e.g., various local government rules) are imposed, the online medication instruction in the embodiment can be provided regardless of the "online support" statement on the prescription.

[0030] As described above in "Acquisition of preference," in this embodiment, the patient is asked whether or not to receive online medication instruction. When acquiring the patient's preference, the advantages of online medication instruction (e.g., shorter waiting times) are explained, and the patient is provided with information to help them make a decision, thereby improving convenience for the patient.

[0031] The availability of online medication instructions can be obtained by any staff member or any device, by any means and at any location. For example, a pharmacy clerk may verbally confirm with the patient at the counter, or the availability may be obtained by the patient operating a storefront reception terminal (e.g., a tablet). The availability of online medication instructions can be managed in any manner within the pharmacy's workflow. As an example, as shown near step S0 in Figure 2, "paper-based management" may be used. For example, the availability of online medication instructions may be clearly indicated by an optional mark (e.g., a sticky note) on any paper document (e.g., a prescription, medication record, or any other form). Note that in certain cases (e.g., when the prescribed drug or the patient's symptoms are not suitable for online medication instructions), the "available" status may not be adopted, and online medication instructions may be "not available (cancelled)" at any stage of the workflow. If online medication instructions are "not available," the pharmacy proceeds to another workflow (not shown) so that a pharmacist can provide face-to-face medication instructions within the pharmacy. Examples of cases where the answer is "no" include when the patient visiting the pharmacy does not wish to receive online medication instructions, or when online medication instructions are inappropriate for some reason.

[0032] Next, from step S5 onwards, work in the dispensing room in the pharmacy proceeds. Specifically, a pharmacist in the dispensing room acquires and views prescription information and the like on medication history terminal 3b1, conducts an audit (prescription audit), checks the medication history and the like on server 2b (electronic medication history system, see Figure 1A), and makes inquiries about any doubts as necessary (see S5 and S6). After dispensing, the pharmacist inputs the dispensing information into medication history terminal 3b1, which is acquired by server 2b (see S7 and S8).

[0033] Next, a further audit (audit of dispensed drugs) is conducted in the dispensing room. The pharmacist acquires dispensing information using the medication history terminal 3b1 (see S9, S10). The pharmacist in the dispensing room conducts the audit (audit of dispensed drugs), and if there are no problems, enters the final audit results and audit images into the medication history terminal 3b1 (see S11). This allows the server 2b to acquire the final audit results (see S12). Upon completion of the audit, all items to be handed over to patients visiting the pharmacy (prescription drugs, drug bags, drug instructions, etc.) are prepared. Note that the audit of dispensed drugs is sometimes referred to as an "inspection" of dispensed drugs, but in the embodiments, these terms are treated as having the same meaning.

[0034] In the embodiment, specific operations of the audit in the dispensing room (e.g., types of terminals, procedures in the dispensing room, etc.) are explained as examples, but this is merely an example. Please note that the specific contents of the flow in Figure 2 can be modified as desired depending on the operations at each pharmacy.

[0035] Next, for patients who have online medication instructions, in one embodiment, a pharmacist in the dispensing room enters patient identification information (e.g., reception number, name, etc.) and an image f (e.g., audit image g, etc.; details will be described later) into the screen 10 (see FIG. 4A) of the data terminal 3cc1 (see S12a). The patient identification information is not limited to the reception number, and any information that can distinguish each patient (e.g., patient name, etc.) can be used. The server 2c then acquires the patient identification information (identification process S12b), and an instruction to provide online medication instructions to the specific patient is issued to the server 2c. The data terminal 3cc1 may be configured to display a screen (see FIG. 8) that lists patients currently accepting prescriptions, in addition to the screen for entering data related to individual patients, such as the screen 10 shown in FIG. 4A. For example, patients currently accepting prescriptions who are registered on the screen 10A are listed in a separate window, along with their current status. The list screen may also display the time the patient was accepted and their personal information. Furthermore, when a request for medication instruction for a patient is made, the screen displaying the list may display the request so as to indicate that it has been "requested." In other words, the data terminal 3cc1 can be configured to display information contained in the data F, including patient identification information, as a list. Furthermore, this list display of patients currently being accepted may be displayed as a list of medication instruction tasks displayed on the pharmacist terminal 3c2.

[0036] In one embodiment, as an example, the server 2c acquires (receives) "image f" (see S12b). Image f is "at least one image to be displayed on (at least) the pharmacist terminal 3c2 in the request process S13 or the call process S23a, S23." Image f can be, for example, "any image that can be used to convey information when requesting medication instruction to a pharmacist," or "any image that can be used for medication instruction." Image f is associated with patient identification information.

[0037] In performing the identification process S12b, the data terminal 3cc1 may not only acquire the image f and transmit it to the server 2c, but also acquire the data F. The data terminal 3cc1 may be communicably connected to the servers 2a, 2b, the receipt computer terminal 3a, the medication history terminal 3b, and the pharmacist terminal 3c.

[0038] Specifically, the "image f" in the embodiment may be, for example, an "audit image," a "prescription image," a "medication information image," a "medication notebook image," a "prescription record image," a "medication envelope image," a "receipt image," a "detailed receipt certificate image," a "reception number slip image," a "test result image," a "health check result image," a "upper limit management table image," or a "dispensing device output information image." One (one type) or more (multiple types) of the images listed here may be used as the image f.

[0039] The above image examples will be explained. An "audit image" is an image of a patient's prescription drug taken during a dispensed drug audit (also called a dispensed drug inspection). In the embodiment, the audit image is an image acquired at the final stage of the audit process, and may be called a final audit image. In the embodiment, a "prescription image" is an image of a patient's prescription. A "medication information image" is an image of a drug information sheet for a patient's prescribed drug. A "medication notebook image" is an image of a patient's medication notebook (whether paper or electronic). A "dispensing record image" is an image of a dispensing record related to a patient.

[0040] A "medicine envelope image" is an image of a medicine envelope. The medicine envelope contains information required by law (items that must be written on the container or packaging of dispensed medication, such as the patient's name, usage and dosage, dispensing date, name of the dispensing pharmacist, and name and address of the pharmacy, hospital, or clinic that dispensed the medication). Other precautions (e.g., storage or usage precautions) may also be written on the medicine envelope. A "receipt image" is an image of a receipt. Receipts are provided to show the breakdown of medical expenses, and are divided into categories such as "dispensing technical fee," "pharmacy management fee," and "drug fee," with the points and costs for each item listed. A "detailed receipt certificate image" is an image of the detailed receipt certificate. The detailed receipt certificate is provided to show a more detailed breakdown of medical expenses than a receipt, and lists, for example, the cost of each prescribed medication.

[0041] The "reception number slip image" is an image of the reception number slip (see Figure 2, step S4). The "examination result image" is an image of documents or data showing any test results (if any) of the patient visiting the pharmacy. The "health check result image" is an image of documents or data showing the results of the patient's health check (if any, whether partial or complete). The "limit management table image" is an image of the copayment limit management table. The copayment limit management table is used at the counter of a medical institution or pharmacy to check that the copayment for a specified period (one month) does not exceed the limit. The "equipment output information image" is an image of a form or data of "output information output from the equipment in the store." The "equipment in the store" may be any equipment in a dispensing room, for example (e.g., dispensing equipment, etc.). For example, in the case of dispensing equipment, audit results, etc. are included as output information.

[0042] The above examples show images that can be used as image f, but some of these can be used alone, while others are intended to be used in combination with other images. Images intended to be used in combination with other images may be transmitted to server 2c together with images that can be used alone, or the necessary information may be transmitted to server 2c as text data, for example, and the images intended to be used in combination may be transmitted to server 2c together.

[0043] Multiple types of images may be used for image f. In one embodiment, an inspection image g, a prescription image h, and a medication information image j are used as image f (see FIG. 4A ). Some of the images f include patient identification information (e.g., the patient's name, etc.). It should be noted that other images may be used, not limited to the above examples. For example, "any other image capable of presenting the information or items indicated by each of the images exemplified above" may be used for image f. For example, some of the images exemplified above may present prescription drug information (e.g., appearance, contents, ingredients, quantity, dosage, dosage, precautions for taking or storing the medication, various information regarding the dispensing date and time, location, or dispenser, etc.), or patient information (e.g., name, age, medical examination results, health check results, medical fee-related information, etc.). Thus, for example, "any image capable of presenting at least one of prescription drug information and patient information" may be used for image f. Text information may be extracted from image f using OCR processing. Furthermore, the format of image f can be any image format, including raster and vector images. Of course, an example of image f includes PDF data. If there is a priority order based on the order in which patients are treated, that priority order may be entered on screen 10.

[0044] 2.2.1. Modification of Data Received by Server 2c In the above, an example in which the server 2c receives "image f" has been described, but the server 2c may receive information other than the image included in data F instead of or in addition to receiving "image f." The "data F" received by the server 2c is, for example, data including at least one selected from the group consisting of patient identification information, audit information, prescription information, drug information, medication history information, medicine notebook information, dispensing record information, medicine envelope information, receipt information, receipt certificate details information, reception number information, test result information, health check result information, upper limit management table information, time information (reception time, dispensing completion time, audit completion time, patient desired time of receiving dispensed medicine), and device output information. Data F is not limited to image data, and may be in the form of CSV (Comma-Separated Values) The data F may be data in the (Data Format) (Data Values) format, a text file, a PDF file, an XML format, a JSON format, or other structured data output by a device. Data F may also be character information extracted from an image by OCR processing. For example, the content information of a patient's prescription may be transmitted to the server 2c as data F in CSV format, and the prescription content may be displayed on the pharmacist terminal 3c2 based on data F. Furthermore, for example, it may be possible to visually and efficiently check numerical information related to the patient (e.g., medication schedule, test value trends, health checkup result sheets, etc.) on the pharmacist terminal.

[0045] Data F can include various pieces of information that can be used in NSIPS, as defined by the Japan Pharmaceutical Association, a public interest incorporated association. For example, patient identification information can use patient information used in NSIPS. In addition, prescription information, drug information (prescription information, dispensing results, drug name, usage and dosage, efficacy and effects, side effect information, cautions for use in combination and contraindications, storage method, precautions, etc.), medicine notebook information, and dispensing record information can also use data used in NSIPS. In addition, data F used by information processing system 1 and data F generated may be output as data that can be used in NSIPS.

[0046] Furthermore, data F may include information and images acquired from other external systems, servers 2a and 2b, receipt computer terminal 3a, and medication history terminals 3b1 and 3b2, or may be configured to acquire additional information or images based on data F. For example, a drug image may be acquired from a database based on drug information in prescription information. This may be used to display the acquired drug image and an image of the actually dispensed drug for comparison. Furthermore, if a patient's test values ​​included in data F deviate from their reference values, an explanatory image of the corresponding disease may be automatically acquired from an external medical information database and used for medication instruction. For example, prescription information and personal information of patients brought to the pharmacy may be acquired not only by server 2a but also by server 2c (online medication instruction system) as data F. Data F may also include information about drug preparations prepared by pharmacists in the dispensing room, as well as information about dispensed drug audits, such as audit results and audit images.

[0047] In addition, images may be generated based on the data. For example, a graph image that visualizes the patient's medication history in chronological order or a calendar-style image illustrating the drug administration schedule can be automatically generated and displayed on the call screen of the pharmacist's terminal. This type of image generation allows the pharmacist to provide guidance while receiving visual assistance.

[0048] 2.2. Explanation of request processing S13 Next, the server 2c executes the request process (see S13). In the request process S13, the server 2c presents the medication instruction task corresponding to the patient identification information (e.g., reception number) to the medication instruction pharmacist via the screen 20 (see FIG. 5A) of the pharmacist terminal 3c2 (see S14). The pharmacist terminal 3c2 is installed in a location (e.g., another store) different from the pharmacy where the patient is staying. When the medication instruction pharmacist selects (clicks) the desired medication instruction task (see S15), the selection information is sent to the server 2c (see S16). If a priority order is specified for the medication instruction task, the display content may be changed to prompt the medication instruction pharmacist to select a task in accordance with the priority order. In the processes of steps S13 and S14, the server 2c may be configured to call the pharmacist. For example, a pop-up display or an audio notification may be displayed on the specified pharmacist terminal 3c2 via the server 2c by operating the data terminal 3cc1.

[0049] In the request process S13, it is also possible to use data F. For example, when displaying medication instruction tasks on the pharmacist terminal 3c2, time information (such as reception time information) may be used as data F to display the priorities of multiple medication instruction tasks.

[0050] 2.3. Description of Call-Related Processing (Including Call Processing S23a) Next, the server 2c executes call-related processing for the selected medication instruction task in accordance with the selection information (S16). The specific contents of the call-related processing can be configured in various ways, but two examples are provided in this embodiment. In the first example, a call waiting screen and a call screen are provided (e.g., screen 30 and screen 40, see Figures 5B and 6A), and the screen transition is performed as call waiting → call execution. In the second example, a screen that integrates the call waiting function and the call function (e.g., screen 60, see Figure 7) is used.

[0051] 2.3.1. First Example (Screens 30 and 40) To explain the first example, in one embodiment, server 2c displays screen 30 (see FIG. 5B) for the selected medication instruction task on pharmacist terminal 3c2 in accordance with the selection information (S16), and enters a call standby state (see S17). At this point, the assignment has not yet been determined, and the task can be canceled by pressing the "Back" button on screen 30. The medication instruction pharmacist checks notes and image f (e.g., audit image g, prescription image h, medication information image j, etc.; images of a medication notebook or dispensing record can also be used. Information other than image f included in data F can also be used) on screen 30 (see S18a). The medication history is also checked, and the medication instruction pharmacist may check it by personally accessing server 2b (electronic medication history system) (see S18b), or, as a variant, servers 2b and 2c may be linked to display the medication history on screen 30 (see S18c). Thereafter, if medication instruction can be started, a connection operation is performed with the intention of accepting the task (see S19). In this embodiment, the connection operation is performed by clicking the "Call patient / start call" button on screen 30 of FIG. 5B. In response to the connection operation, pharmacist terminal 3c2 transmits a connection instruction (or any connection information such as access information) (see S20).

[0052] In the embodiment, as an example, when a connection (or connection information) is sent in step S20, processing such as "medication instruction notification" is performed (see S21). In the embodiment, as an example, a medication instruction notification and patient identification information (e.g., a reception number) are sent from server 2c to receipt computer terminal 3a. Specific examples of notification methods will be described later in section "3.2. Examples of Notification Function." In the embodiment, as an example, a pharmacy clerk calls a patient visiting the pharmacy with a specific reception number in accordance with the medication instruction notification and guides the patient to the location of patient terminal 3c1 (e.g., an arbitrary desk in an open space near the counter, a partitioned booth, or a private room), and the pharmacy clerk (or the visiting patient) performs a "call start operation" on patient terminal 3c1 (see S22). The call start operation is, for example, pressing a call start button or the like displayed on the screen of patient terminal 3c1 (e.g., the "Patient Call / Call Start" button on screen 30). Accordingly, task acceptance is confirmed on pharmacist terminal 3c2. Note that multiple patient terminals 3c1 may be installed in the same pharmacy store. In this case, the medication instruction notice includes terminal designation information (indication of which patient terminal 3c1 the patient should be guided to).

[0053] Next, in the embodiment, as an example, server 2c executes a call process (see S23a and S23b). In this process, server 2c connects pharmacist terminal 3c2, which has been assigned the medication instruction task, and patient terminal 3c1 so that they can communicate with each other. During the connection, screen 40 (call screen: see FIG. 6A) is displayed on pharmacist terminal 3c2, and screen 42 (call screen: see FIG. 6B) is displayed on patient terminal 3c1.

[0054] According to the first example described above, a medication instruction pharmacist can provide online medication instruction from outside his / her own store (see S24a), and patients visiting his / her own store can receive this instruction (see S24b).

[0055] 2.3.2. Second example (Screen 60) In the embodiment, various arbitrary screens and processes can be adopted without being limited to the first example. In the second example, screen 60 (see FIG. 7) is used instead of the above screens 30 and 40. In the second example, when the state shifts from call standby to call in progress, the screen does not transition and screen 60 is maintained.

[0056] To explain the second example, in one embodiment, the server 2c displays a screen 60 (see FIG. 7) for the selected medication instruction task on the pharmacist terminal 3c2 in accordance with the selection information (S16). In one embodiment, the screen 60 is initially set to a call standby state (corresponding to S17). The screen 60 is provided with the functions of the screens 30 and 40. In the second example, the screen 60 can be used to perform processes and tasks corresponding to steps S17, S18a, S19, and S20 in the first example.

[0057] Here, in the second example, when the "Patient Call / Start Call" button (button 61) is clicked on the screen 60 of FIG. 7, the following processes (x1) to (x4) may be executed, for example. (x1) A patient call notification is sent to the store (own store) (corresponding to step S21). (x2) The remote side (pharmacist terminal 3c2) enters a call standby state. At this time, the following processes (x2-1) and (x2-2) are executed. (x2-1) The selfie camera will start up and wait for the call to start. (x2-2) The "patient call / start call" button (button 61) changes to the "end call" button. In other words, button 61 is an "operation button for starting / ending a call." (x3) The call starts when patient terminal 3c1 starts the call (corresponding to steps S23a and S23b). The medication instruction pharmacist can provide online medication instruction through screen 60. The patient terminal 3c1 may be installed anywhere, and may be installed, for example, at a medication counter in a store. (x4) When the "End Call" button displayed in (x2-2) above is clicked, the call ends (see step S25 described below).

[0058] In this second example, the medication instruction pharmacist can also provide online medication instruction from outside his own store (see S24a), and patients visiting his own store can receive this instruction (see S24b).

[0059] 2.3.3. Ending a call After the processing illustrated in the first or second example above, when medication instructions via online communication are completed, the server 2c receives an instruction to disconnect (see S26) in response to the completion operation (see S25), and the server 2c disconnects. At this point, the task is completed.

[0060] 2.4. Steps S27 to S31 (Processing after Medication Instructions) Thereafter, in an embodiment, as an example, server 2c displays guidance information (e.g., accounting information, accounting information, voucher number, etc.) on patient terminal 3c1 (see S27). The voucher number may be printed from a ticket issuing machine connected to patient terminal 3c1. Upon receiving the guidance information, the patient proceeds to the counter or the like in accordance with the information (see S28). A notification may be sent to reception computer terminal 3a together with or instead of patient terminal 3c1.

[0061] In response to the end of the call processing (disconnection S26), the server 2c sends a "medication instruction completion notice" to the receipt computer terminal 3a (see S29) at the same time as or before or after displaying guidance information (S27, S28). After that, the pharmacy clerk prepares for the payment (see S30), and the patient completes the payment and receives the prescribed medicine (see S31).

[0062] As described above, in the embodiment, the server 2c executes the identification process S12b, the request process S13, and the call processes S23a and S23b. This effectively introduces online medication instruction into the operation of a pharmacy store, enabling the effective utilization of human resources outside the store (pharmacists at other stores) and improving the business response capabilities of the pharmacy store. Face-to-face consultations at the pharmacy store offer various advantages (e.g., the peace of mind of face-to-face administrative procedures and medication instruction, the ability to receive and manage original prescriptions, and the ability to directly hand over prescription drugs). These various advantages of in-store consultations can be achieved while also improving business response capabilities. Conventionally, during busy periods, pharmacists sometimes had to travel from headquarters or another store to assist with medication instruction, spending time and money. However, the effective introduction of online medication instruction in the embodiment offers the advantage of reducing such time and costs. Preferably, the information processing system of the embodiment is introduced without making major changes to store operations (more preferably, without making any changes to basic store operations).

[0063] In the embodiment, as an example, an inspection image g or the like is displayed on the pharmacist terminal 3c2 as an example of the image f in the request process S13 or the call process S23a (see FIGS. 4A, 5A to 6A, and 7). This improves convenience when confirming a request or making a call.

[0064] 3. Examples of terminal functions, etc. 3.1. Examples of login and screen transitions Please refer to Figure 3. In this embodiment, as an example, server 2c provides an online medication instruction service in the form of a web application. As an example, each terminal 3 at a pharmacy store logs in using a pre-registered store account. If dispensing room mode is selected on the subsequent mode selection screen, the functions of data terminal 3cc1 (e.g., display of screen 10, etc.) are provided, and if counter mode is selected, the functions of patient terminal 3c1 (e.g., display of screen 42, etc.) are provided.

[0065] Each terminal 3 outside the store (e.g., other pharmacy stores, etc.) logs in using a pre-registered pharmacist account. This provides the functions of the pharmacist terminal 3c2 (e.g., display of screens 20, 30, 40, notifications to other terminals 3, etc.). After logging in, for example, one or more pharmacy stores linked to the account (e.g., person in charge, affiliation, same chain, same group, etc.) may be listed, and related information may be displayed.

[0066] 3.2. Notification function example "Notification" is shown in FIG. 3, which means the notification function of the terminal 3. In one embodiment, as an example, a function of the terminal OS in each terminal 3 may be used to output any notification sound, notification message, notification image, etc. Specifically, the pharmacist terminal 3c2 may be able to access the OS settings, message or alarm setting function, etc. in each terminal 3 in the pharmacy store. The notification function may be set using any communication function between terminals 3, or may be provided through a web application on the server 2c.

[0067] Specifically, in the embodiment, at least the following three patterns are adopted as examples of using the notification function of the pharmacist terminal 3c2: Each pattern includes a notification (for example, sounding a notification sound or displaying a message). · Pattern 1: Patient call · Call start · Second pattern: Calling a pharmacist (e.g., contacting a pharmacist regarding a suspected case) · Third pattern: Accounting contact

[0068] The first pattern notification is performed, for example, when the "Call patient / start call" button is pressed on a screen 30 (see FIG. 5B) described later. This notification corresponds to step S21 (medication instruction notification) in FIG. 2.

[0069] In the second and third pattern notifications, for example, a message is displayed along with a notification sound, and the timing of displaying the message is, for example, when the "Call pharmacist" or "Notify accounting" button is pressed on screen 30 (see FIG. 5B) described below. The third pattern notification (notify accounting) after the medication instruction completion operation (S25) corresponds to the medication instruction completion notification (S29).

[0070] In the first and third patterns, for example, the notification function is activated on an arbitrary clerk terminal at the reception desk (e.g., receipt computer terminal 3a). In some cases, it may also be activated on another arbitrary terminal at an adjacent desk (e.g., electronic medication history terminal). In the second pattern of calling a store pharmacist (e.g., when a question arises, etc.), for example, the notification function may be activated on an arbitrary terminal in the dispensing room (e.g., medication history terminal 3b1 or data terminal 3cc1).

[0071] In the embodiment, it is possible to set which notification is to be sent at each terminal 3 in order to accommodate the above-mentioned first to third patterns. For example, notification conditions may be set so that any terminal at the counter (e.g., receipt computer terminal 3a, etc.) can receive notifications of the first and third patterns, and any terminal in the dispensing room (e.g., medication history terminal 3b1 or data terminal 3cc1) can receive notifications of the second pattern. When receiving multiple different notifications (e.g., first and third patterns) at the same terminal 3, it is preferable to differentiate the notification content (e.g., alarm sound, etc.), so it is also preferable that the notification content (e.g., alarm sound, etc.) can be set to multiple different contents. In addition, it may be possible to select whether the alarm sound is played in a loop or not.

[0072] 3.3. Data terminal screen example Figure 4A shows an example of a screen 10 displayed on the data terminal 3cc1. Screen 10 is an example of an image transmission screen for transmitting image f. A pharmacist in the dispensing room enters patient identification information (e.g., reception number) via screen 10, clicks the "Take Image (Capture)" button, attaches image f, writes notes as necessary, and presses the send button. This allows the server 2c to receive the various information. The "Visit Later" checkbox is an example of a priority specification function; checking it and pressing the send button reflects the priority in the transmitted information. Image f is preferably clear enough to accurately recognize information about the object being captured (e.g., shape, color, pattern, letters, numbers, symbols, etc.). For example, it is preferable that the inspection image g be captured with the prescription drugs arranged clearly on a tray or similar.

[0073] FIG. 4B shows examples of screens 11 to 13 used in the embodiment for status confirmation, etc. The data terminal 3cc1 can display screen 11 (status confirmation screen), and pressing the "Captured Image List" button transitions to screen 12 (image list screen). Screen 12 displays a list of sent images f (e.g., audit image g, etc.). A filtering function, such as by the date of sending (e.g., the current day), is also available. For example, if an online medication instruction was originally planned but the user wishes to change to face-to-face medication instruction, the corresponding medication instruction task may be canceled by selecting the desired image f and pressing the cancel button. Screen 12 also provides status buttons ST. The status buttons ST include "Received," "Confirmed by pharmacist," "On hold," and "Instruction completed," and can display the status of the received image. For example, each status button ST does not have to be a button that triggers an event when clicked, and a checkbox that toggles on and off with each click may be used. For example, clicking the "Search" button with all four status buttons ST turned on displays images of all statuses. For example, if you turn off everything except "Received," you can narrow down the display to only images with a status of "Received." For example, if you turn on the "Pharmacist Confirmed" button and click the "Search" button, you can narrow down the display to "Images f already opened on the pharmacist terminal" (i.e., audit images that have been confirmed by a pharmacist). By pressing the "Message" button, screen 13 (message window) opens, allowing you to check the message reception history. This allows you to check messages from the remote pharmacist terminal 3c2.

[0074] In addition, in processing using the data terminal 3cc1, data F may be used instead of image f. Data F may include information such as prescription information, dispensing record information, test result information, and audit information stored in CSV data, text data, JSON data, or XML data, or information stored in these formats. Image f used for medication instructions may be automatically generated based on the information included in data F using image processing technology or template processing. Furthermore, based on data F, an external database and information providing server, each server 2, and each terminal 3 shown in FIG. 2 may be accessed to obtain related image data and present it on the pharmacist terminal 3c2. This makes it possible to prepare materials that provide visual assistance in medication instructions without relying on imaging.

[0075] 3.4. Example of a pharmacist terminal screen 3.4.1. Request Receipt Screen Screen 20 in FIG. 5A is displayed on pharmacist terminal 3c2 by the request process (S13 in FIG. 2). Screen 20 is a request receiving screen, and is a screen for receiving a request for a medication instruction task. As an example of the screen layout of screen 20, each medication instruction task is displayed as a tile. In the embodiment, as an example, medication instruction tasks 21 and 22 are presented together with image f. Specifically, in the embodiment, as an example, as shown in FIG. 5B, medication instruction tasks 21 and 22 are presented together with inspection image g, etc. (e.g., overall thumbnail display). In the example of FIG. 5A, medication instruction task 21 corresponding to reception number 55 (e.g., inspection image g1, etc. is attached as image f) and medication instruction task 22 corresponding to another reception number 56 (e.g., inspection image g2, etc. is attached as image f) are illustrated. Inspection image g may be displayed together with other information, such as inspection information G, included in data F, or may be replaced with other information, such as inspection information G, included in data F. The status button ST described in Fig. 4B is also provided on screen 20. When a desired medication instruction task (e.g., medication instruction task 21) is selected (clicked), the screen transitions to screen 30 in Fig. 5B.

[0076] As an example, various display switching menus may be provided on the screen 20, etc., which may enable narrowing down and displaying or sorting medication instruction tasks. The display switching menu may include, for example, one or more of the following menus (M1) to (M5), or may employ a combination of these. (M1) Display or rank order of requesting pharmacies (M2) Ranking by request time (M3) Display ranking by reception number (M4) Display by priority (e.g., "urgent," "later," "standard," etc.) (M5) Filter and display only requests that are specified for you

[0077] 3.4.2. First Example of Call-Related Screen Q The dashed line Q in Figure 3 indicates call-related screens related to the call function, specifically including screens 30 and 40. Screen 30 in Figure 5B is an example of a call standby screen. As an example, medication instruction task 21 (reception number: 55) is selected. In the window selection menu, "Window 1" is selected as an example, which means that patient terminal 3c1 installed at window 1 is specified as the call connection destination. In Figure 5B, audit image g1 is displayed as an example of image f (in this example, the second of three images is displayed), and a memo field is provided next to it, and the status of this medication instruction task (cancelled, suspended, completed) is also displayed. Image f can also be substituted for each piece of information contained in data F, either in place of image f or together with image f. "Hold" indicates waiting for a call to resume remotely, rather than at the store, after an interruption due to a question or other reason. The "Call pharmacist" button can send messages and notifications to data terminal 3cc1, and the "Contact accounting" button can send messages and notifications to receipt computer terminal 3a. Pharmacist call can be used, for example, for question or inquiry. When the "Call patient / start call" button is pressed, a message is sent to patient terminal 3c1 and a medication instruction notification (see S21 in Figure 2) is issued. At the same time, a notification is also sent to any terminal used by a clerical staff member, etc. (e.g., receipt computer terminal 3a). When there is a response (connection is started) on patient terminal 3c1, the screen transitions to screen 40 in Figure 6A.

[0078] Screen 40 in Fig. 6A is an example of a call screen of the pharmacist terminal 3c2. Screen 40 includes a patient call button, an image sharing screen for audit images, etc., a call end button, and call start and end times and user records. Buttons for turning on background control functions (e.g., background blurring) or audio subtitles, etc. may also be provided.

[0079] In the embodiment, as an example, the image f may be displayed on a call waiting screen (e.g., screen 30) or a call screen (e.g., screen 40). In Figures 5B and 6A, an inspection image g1 is displayed as an example of the image f, but any other image can be displayed by clicking an image switching operation (e.g., the "<" and ">" buttons below the inspection image g1 in Figures 5B and 6A).

[0080] Screen 40 in FIG. 6A is a call screen of pharmacist terminal 3c2 connected by call processing (S23a). As an example, pharmacist terminal 3c2 that selected medication instruction task 21 (reception number: 55) is connected so as to be able to make a call with patient terminal 3c1 that is linked to the corresponding patient identification information (e.g., reception number 55). The main display area 40a displays the visiting patient (reception number: 55) captured by the camera of patient terminal 3c1. The sub-display area 40b displays a self-camera image (of the medication instruction pharmacist himself). In the embodiment, as an example, an inspection image g1 and the like are also displayed on screen 40.

[0081] 3.4.2. Second Example of Call-Related Screen Q The call-related screen Q may be integrated into a single screen 60 (see FIG. 7). Screen 60 is a screen that can be used for both call waiting and call. Similar to screen 30, screen 60 provides, for example, a "Back" button (cancel function), a memo entry field, an "Image Confirmation" function (e.g., the user can confirm any image f, such as an audit image g, a prescription image h, or a drug information image j), a "Pharmacist Call" function (a function for inquiring about doubts), a "Patient Call / Start Call" function, an "Accounting Contact" function, and a medication instruction status function. Similarly to screen 40 (see FIG. 6A), screen 60 provides a main display area 40a, a sub-display area 40b, and an "Image Sharing" function.

[0082] Screen 60 also provides image confirmation functions, including a thumbnail area 62, a magnification area 63, and an annotation function 63a (e.g., pen selection, writing / erasing). When a thumbnail image is selected from thumbnail area 62 (e.g., audit image g1 is selected as an example in FIG. 7), the selected image is enlarged and displayed in magnification area 63 on the right side of screen 60. Clicking the "Image Share" button subsequently shares the image with patient terminal 3c1. Annotation function 63a can employ, for example, button-like radio buttons, and allows for arbitrary drawing (e.g., graphic drawing, pen drawing, text input, etc.) on the image in magnification area 63. The image with the combined drawing is also shared with patient terminal 3c1. Furthermore, clicking the "Call Screen Enlargement" button during image sharing enlarges the patient's face displayed on patient terminal 3c1 in magnification area 63. Typically, the patient's face is enlarged during the initial greeting, and then audit images and other information are shared to provide medication instructions.

[0083] 3.5. Example of patient device screen Screen 42 in FIG. 6B is an example of the screen of patient terminal 3c1 (e.g., counter 1) connected by call processing (S23b). Main display area 42a displays the medication instruction pharmacist captured by the camera of pharmacist terminal 3c2. Sub-display area 42b displays the patient (visiting the pharmacy) captured by the self-camera.

[0084] When an image is shared on the pharmacist terminal 3c2, the shared image can be displayed in the main display area 42a. When an image is shared, another sub-display area for displaying the pharmacist's face may be additionally displayed. Any one of the images f can be shared as the shared image. Furthermore, the main display area 42a may display and share not only the image f but also information contained in the data F or tables, images, etc. generated based on the information.

[0085] 4. Variations in Request Processing In an embodiment, as an example, multiple pharmacist terminals 3c2 may be installed in "different locations" or "the same location." "Different locations" may be other pharmacy stores (which may be chain stores, etc.), or any location not limited to pharmacy stores. The number of locations where pharmacist terminals 3c2 are installed may be any number of two or more, and may be comprehensively installed in, for example, multiple chain stores, etc. "The same location" is, for example, within the same building. As an example of the "same location," a "medication instruction center" may be established, and multiple pharmacists within this center may provide online medication instructions.

[0086] In the request process S13, a medication instruction task may be presented to each pharmacist terminal 3c2 according to the "individual specific situation" (e.g., deciding whether to present or allocate, etc.). The individual specific situation may be, for example, "the current situation, state, environment, attributes, geography, time, designation (agreement), evaluation, or history, etc." regarding the "prescription, pharmacist, terminal location (store, etc.), or patient visiting the pharmacy, etc." The individual specific situation may be based on various factors, such as natural factors, geographical factors, human factors, or system factors. The following (B1) to (D2) are examples of individual specific situations.

[0087] (B1) Examples include the store to which each pharmacist (using the pharmacist terminal 3c2) belongs, or the history of help provided at other stores. For example, past help history (e.g., the number of times or cumulative time spent helping at other stores), whether the store is nearby (e.g., the closer the store, or the store within a specified distance), whether the store is a pharmacy adjacent to a similar medical department, etc. Data from the "aggregation process" described below may also be used. (B2) Examples include designating a pharmacist or store, or a bulk request without any designation. For example, the input items on the data terminal 3cc1 may have a designation menu for designating one or more specific pharmacists or one or more specific pharmacy stores. For example, the requesting store and the accepting store may be set based on predetermined arbitrary conditions (e.g., shift setting or schedule setting between multiple stores with different workloads). This shift setting, etc., can be considered an online version of helping out at a real store. Bulk requests can also be adopted.

[0088] (C1) The contents of a prescription for a patient visiting a pharmacy can be considered as an example. For example, the ease of requesting a prescription may be determined according to the prescription contents. For example, in order to increase turnover when a store is crowded, a process may be adopted to automatically pick up prescription contents that are easy to request from other stores (e.g., a single acute patient with a common cold, etc.). Prescription information, etc. may be linked between servers 2a and 2c. (C2) Examples include patient information, symptoms, and medication history. As in (C1) above, a process may be adopted to automatically select individual patients, symptoms, or medication history that are easy to request from other stores. Servers 2a, 2b, and 2c may share patient information, etc.

[0089] (D1) The situation or external environment of the installation location where each pharmacist terminal 3c2 is installed may be considered. The installation location may be a pharmacy store other than the pharmacist's own store or a medication instruction center. The external environment or store situation of each pharmacy store (where each pharmacist terminal 3c2 is installed) may be considered as an example. The external environment may be, for example, weather information or traffic congestion information obtained from the Internet in the area of ​​each store or medication instruction center. For example, there is a tendency for more customers to visit the pharmacy in good weather than in bad weather. The situation of the installation location may be, for example, the number of patients visiting each store or the vacancy situation, or any situation within each store or medication instruction center (e.g., temporary closure, etc.). Based on these, each medication instruction task may be allocated to avoid, for example, a concentrated load. As a measure for BCP (Business Continuity Plan), various emergency situations may be included in the situation of the installation location or the external environment. Various types of emergency situations may include, for example, natural disasters (e.g., earthquakes, fires, typhoons, floods, etc.), man-made disasters (e.g., incidents, accidents, scandals, etc.), or system failures. For example, request tasks may be allocated so as to avoid stores in an emergency (e.g., stores in the area where the emergency occurred or nearby) and give priority to stores operating normally (e.g., stores relatively far from the area where the emergency occurred). (D2) Examples include the workload, activity status, and evaluation of each pharmacist. For example, data on the work status, workload, and other recent status of each pharmacist using each pharmacist terminal 3c2 may be collected. Data from the "aggregation process" described below may also be used.

[0090] Two or more of the above (B1) to (D2) can be combined with each other. Furthermore, for example, the data management unit 2c1 of the server 2c may store and manage the information of the above (B1) to (D2), and medication instruction tasks may be allocated based on the data stored in the data management unit 2c1. Depending on the individual and specific situation (e.g., the above (B1) to (D2)), for example, if no suitable candidate for request is found (or if the task cannot currently be requested), or if the result of the appropriateness / inappropriateness determination process for online medication instruction is inappropriate, a notification to that effect may be sent to any terminal (e.g., the receipt computer terminal 3a or the data terminal 3cc1, etc.).

[0091] Although various examples of individual specific situations have been given above, it is not necessary to assume multiple pharmacist terminals 3c2. For example, in the request process S13, a medication instruction task may be presented to one pharmacist terminal 3c2 depending on (C1) or (C2). As in this example, whether to request a task may be adopted for one pharmacist terminal 3c2 depending on the individual specific situation.

[0092] 5. Aggregation processing In the embodiment, as an example, the server 2c may further perform a counting process. The counting process can be performed for any item, and the counted data can be managed individually for each pharmacist account or each pharmacy store. In addition, any counted data may be shared between the servers 2c of each pharmacy store via data communication.

[0093] In the embodiment, as an example of the tallying process, the medication instruction task allocation status is tallied for each pharmacist using the pharmacist terminal 3c2. The "allocation status" may be, for example, the number of tasks accepted, the number of tasks completed, or the number of tasks assigned, or may include two or more of these. After task assignment, the number of tasks accepted and declined may be tallied together or separately. The number of tasks accepted by each pharmacist may be tallied as other-store help history or activity status, either collectively or by store. Evaluations of each pharmacist may be recorded based on the task allocation status. The tallying process can be performed, for example, by the data management unit 2c1 in the server 2c, but is not limited to this and may also be performed, for example, by any database system (not shown) external to the server 2c.

[0094] 6. Modifications, etc. 6.1. Modification of business flow, etc. Various modifications can be made to the workflow and system processing in Figure 2. For example, in the embodiment, in the identification process S12b, the server 2c acquires patient identification information (e.g., reception number) via the data terminal 3cc1, and various processes are executed in association with this patient identification information, but this is not limiting. For example, as a variation of the identification process, the identification process may be realized by an "any entity" inputting patient identification information (e.g., reception number) from an "any terminal" to the server 2c at an "any timing."

[0095] For example, computer management may be employed in step S0. As computer management, for example, when a patient visiting the pharmacy requests online medication instruction, "online medication instruction available" and patient identification information may be transmitted to server 2c directly or via any server 2 (e.g., server 2a) in response to operation of a terminal (e.g., receipt computer terminal 3a) by a pharmacy clerk or the like. Alternatively, when a patient visiting the pharmacy requesting online medication instruction presses a confirmation button on an in-store reception terminal (e.g., tablet) or the like, "online medication instruction available" and patient identification information may be transmitted to server 2c directly or via any server 2 (e.g., server 2a).

[0096] For example, server 2c may acquire "information indicating that online medication instruction is available for a visiting patient." Server 2c may store this "information" in a table or the like, and when online medication instruction is "available," may execute request process S13 or send any notification to the receipt computer terminal 3a, data terminal 3cc1, or the like. For example, a "desire" for online medication instruction for each visiting patient (e.g., by reception number) may be recorded and managed in a predetermined column of the table (this can also be used for managing cancellations, etc.). Data management may be performed by server 2c in cooperation with another server 2 (e.g., server 2a or server 2b).

[0097] In addition, in the embodiment, after the request process (S13), several system processes or business procedures (S15-S22) are performed, and then the connection process (S23a, S23b) is executed. However, this is just one example, and the processes between the request process and the connection process can be arbitrarily changed. For example, the response confirmation operation (S22) may be omitted. In this case, the pharmacist terminal 3c2 may first establish a call connection state and wait for the patient terminal 3c1 to take its seat. As another example, each process related to call waiting (S17, etc.) may be omitted. In this case, the call process may be executed immediately in response to the task selection operation (S15), or a confirmation message (e.g., "Do you want to connect?") or a countdown display (the call is connected after the countdown ends) may be adopted. In these cases, the screen layout of screen 20 (request receiving screen) may be designed so that details of each medication instruction task can be confirmed, or detailed information may be confirmed by any operation on screen 20 (e.g., detailed information may be displayed as a pop-up when the cursor is hovered over it).

[0098] 2, steps S22 and S30 are illustrated in dashed box Z. The hardware example shown is the receipt computer terminal 3a, but is not limited to this. At least one of steps S22 and S30 may be performed by a terminal other than the receipt computer terminal 3a.

[0099] 6.2. Medication instruction task cancellation and history management The server 2c may be able to switch the online medication instruction status from "yes" to "no" at the time of (during) or after the request processing S13. This may be possible at each terminal 3 (e.g., the receipt computer terminal 3a, the data terminal 3cc1, the patient terminal 3c1, or the pharmacist terminal 3c2). The history of the switching may be saved.

[0100] The server 2c may store and manage the history of online medication instruction for each patient who visits the pharmacy, and may execute various processes based on the history. For example, the server 2c may output to any terminal 3 the implementation history of online medication instruction, or a recommendation notice (regardless of image or audio) based on the history.

[0101] 6.3.Priority specification function The priority specification function (e.g., a "visit later" checkbox, etc.) may be displayed not only on the data terminal 3cc1 but also on any screen of several terminals 3 (e.g., 3a, 3c2). For example, a priority specification menu, etc. may be provided, and multiple types of priority (e.g., "urgent (or emergency)," "later," "standard," or time specification (e.g., 11:00)) may be set. For example, an example of using "later" is when a patient visits the pharmacy after checking in, going out, and then returning.

[0102] In addition, in the request process S13, data F may be used to indicate that the visiting patient will come to pick up the dispensed medication later. For example, in step S0 of the information processing flow in FIG. 2, information about receipt of the prescription medication may be acquired from the visiting patient, registered in server 2 (2a, 2b, 2c), and managed as data F together with patient identification information. At this time, information indicating "Come later" as prescription medication receipt information is displayed on the pharmacist terminal 3c2 as part of the status of the medication instruction task in the request process. Note that while "Come later" is displayed, the medication instruction pharmacist cannot start remote instruction (call-related processing) on ​​the pharmacist terminal 3c2, but may be able to refer to, for example, information regarding dispensing and audit information. The "Come later" setting is canceled when the patient visits the pharmacy to pick up the prescription medication, and server 2c updates the medication instruction task to cancel the status indicating "Come later," allowing the medication instruction pharmacist to start the medication instruction task.

[0103] Information about the patient's receipt of prescription drugs may be managed as data F together with the patient's scheduled visit time. Medication instruction tasks with a status of "visit later" may be selectable on the medication instruction terminal, and may be configured so that a notification is sent from server 2c to pharmacist terminal 3c2 when the scheduled visit time or the "visit later" status is canceled.

[0104] 6.4. List screen of accepted patients FIG. 8 shows a screen 70 displaying a list of information about patients who have visited the pharmacy. The list 71 displayed on the screen 70 displays the following information for each task: "Reception Number," "Reception Time," "Patient ID," "Name," "Katakana," "Gender," "Age," "Date of Birth," and "Remote (a column indicating the status of the online medication instruction request)." In the example shown in FIG. 8, information is listed by reception number. For example, when a patient visits the pharmacy with multiple prescriptions, a reception number is assigned to each prescription, and the information processing system 100 manages each reception number as a task. The "Visit Later" status described above can also be included in the information in the list 71, and the amount of information displayed in the list 71 can be increased or decreased as needed. By checking and operating the screen 70, pharmacy staff can select patients and perform processing such as requesting online medication instruction (presenting the medication instruction task). The list 71 may also be configured to sort and display information based on each information item. The list 71 may also be configured to extract and display only relevant information based on a specific information item. This allows pharmacy staff to grasp reception information at a glance, enabling smooth guidance and operational management.

[0105] When a task is selected on screen 70, the screen may transition to a screen displaying detailed information related to the patient (e.g., reception information, prescription information, drug information, audit information, etc.). The "Remote" field may display a symbol, such as a "●," to easily indicate that online medication counseling has been requested. List 71 may also include a field indicating whether the patient requires online medication counseling. This information, combined with attribute information such as age, gender, and date of birth, can also be used as supplementary information for determining the priority of the response. Screen 70 displays various buttons, such as "Close," "Calendar," "Audit," "Interview," "Report," and "Medication History," which allow selective execution of tasks for each reception. Buttons other than those listed above may also be provided, such as a "Call Pharmacist" button.

[0106] The "Calendar" button is a function that displays the patient's medication calendar. In other words, it is a function that displays a table that visualizes each patient's medication status (schedule, past results) in chronological order. The screen displayed by the "Calendar" button may also be configured to allow editing of the medication schedule. In this case, each terminal 3 on which the list 71 is displayed may be linked to the receipt computer terminal 3a via the server 2. The "Audit" button is operated in relation to step S11, and may transition to a screen for not only checking the audit image and audit result, but also uploading the audit image and inputting the audit result. This enables the pharmacist to efficiently carry out the audit of the dispensing contents based on the prescription.

[0107] The "Transfer" button is operated in connection with step S7 and is used to input or confirm information to be transferred, such as information about dispensing, precautions, special notes for the patient, etc. This supports smooth information sharing within the pharmacy and contributes to improving the quality of medication instructions. The "Remote" button is used to cause server 2c to execute the request process (step S13). Specifically, it starts the process of requesting online medication instructions for the selected patient, and can be used as an opportunity to prepare for connection with a pharmacist terminal or a patient terminal. For example, it requests online medication instructions from the selected pharmacist, and serves as an opportunity to prepare for connection between pharmacist terminal 3c2 and patient terminal 3c1 (establishing a communication link, sending a notification, triggering a screen transition, etc.). In FIG. 8, a task in list 71 operated with the "Remote" button has a "●" symbol added to the "Remote" column of list 71.

[0108] The "Medication History" button is used by pharmacists who provide online medication instructions to refer to the medication history information of the patient. This allows them to check the patient's past medication history, allergy information, side effect information, etc. Medication history information may be acquired and displayed in cooperation with medication history terminals 3b1, 3b2 or server 2c.

[0109] Screen 70 can be displayed on terminals 3a, 3b1, and 3cc1 in the pharmacy store, and can also be displayed on pharmacist terminal 3c2 that provides online medication instructions. On each terminal 3, it is possible to not display buttons that execute at least some of the functions.

[0110] 6.5. Image capture device It is preferable that the image f is a clear, easy-to-view image of the object to be imaged (for example, prescription drugs in the case of the inspection image g). An imaging device for the image f may be provided, and for example, an imaging terminal (for example, a smartphone or tablet terminal), a fixing device for the terminal (for example, a bendable arm), and a placement section (for example, a tray) for placing the object to be imaged (for example, prescription drugs, etc.) may be prepared. The imaging terminal can transmit the image f to the data terminal 3cc1, for example, by wireless communication. Note that if the data terminal 3cc1 is a terminal with a camera, it may also function as the imaging terminal.

[0111] In some cases, the inspection image is captured by an "inspection device installed in the dispensing room." This inspection device may be of various known types, such as a stand-alone device, or a terminal of a dispensing inspection system (also called a dispensing inspection support system, drug inspection support system, audit support system, dispensing weighing audit system, or prescription drug inspection system). The data terminal 3cc1 may receive the inspection image data from this inspection device and transmit it to the server 2c.

[0112] 6.6. Modifications of each terminal 3 The patient terminal 3c1 may be realized by a terminal (e.g., a smartphone) of a patient visiting the pharmacy. The patient may access the server 2c on their own terminal via a browser or by installing an app, and use their own terminal as the patient terminal 3c1 to receive online medication instructions within the pharmacy. Patient accounts may be managed by the server 2c.

[0113] 6.7.Other In the embodiment, each server 2 may have any configuration capable of providing "server functions in a client-server model." Each server 2 is any logical or functional component for providing data, functions, or processing power in response to requests from clients (terminals 3). Each server 2 is not limited to a physical server (e.g., on-premise or in a data centre), but may also be a virtual server, a container, or "dynamically allocated computing resources using a serverless architecture." Each server 2 may be built on an infrastructure such as Amazon Web Services (AWS). Each server 2 may be a web application (e.g., see FIG. 3) built on the cloud using a service model such as Software as a Service (SaaS), Platform as a Service (PaaS), Infrastructure as a Service (IaaS), or Everything as a Service (XaaS). Some of the multiple servers 2 may be physical servers, and others may be virtual servers.

[0114] Although the present invention has been described above based on the embodiments, the present invention is not limited to the configurations of the above-described embodiments. The same functions as those of the information processing system 1 may be realized in various computers, such as personal computers that do not constitute a client-server system, and various communication terminals and mobile information terminals, such as mobile terminals and tablets. The computer program may be implemented in various computers, communication terminals, and mobile information terminals.

[0115] In the embodiments, a program or information processing method for causing a computer to execute each process of the information processing system 1 described above can also be provided. It should be noted that in this program or information processing method, each process of the embodiment may be executed by "any computer," and whether or not the server executes each process (or whether or not it is server-side processing) is optional. For example, some or all of the processes of the embodiment may be executed by a client (e.g., terminal 3) (in the case of all processes, communication may be performed only between terminals 3, omitting the server). Furthermore, each feature of the above embodiments and variations can independently constitute an invention, and can also be combined as appropriate. It should be noted that the gist (technical scope) of the present invention also encompasses various modifications, applications, and uses that may be made by those skilled in the art as needed.

[0116] The information processing system 1 described above may also include combinations of the features described in the following supplementary notes. These combinations are described below.

[0117] [Appendix 1] An information processing system for providing online medication guidance at a pharmacy store, A server, a patient terminal at the pharmacy store, and a pharmacist terminal at a location different from the pharmacy store, The server performs an identification process, a request process, and a call process; In the identification process, the server acquires data, In the request process, a medication instruction task corresponding to the data is presented on the pharmacist terminal, In the communication process, the pharmacist terminal on which the presented medication instruction task has been selected is connected to the patient terminal so that they can communicate with each other; The data is An information processing system that includes at least one of the following information for patients who visit the pharmacy store: patient identification information, patient prescription drug receipt information, audit information, prescription information, drug information, medication history information, medication notebook information, dispensing record information, drug envelope information, receipt information, receipt certificate details information, reception number information, test result information, health check result information, upper limit management table information, and device output information. [Appendix 2] 10. The information processing system of claim 1, An information processing system in which the information contained in the data is displayed on the pharmacist terminal during the request processing or the call processing. [Appendix 3] 10. The information processing system according to claim 2, An information processing system, wherein the data includes information for transmitting information at the time of a request in the request processing, or information used for medication instructions in the call processing. [Appendix 4] 10. The information processing system according to claim 2, In the request processing, the medication instruction task is presented together with at least a part of the information included in the data. [Appendix 5] 10. The information processing system according to claim 2, In the call processing, at least a part of the information included in the data is displayed on the call screen of the pharmacist terminal. [Appendix 6] An information processing system according to any one of Supplementary Notes 1 to 5, The server further performs a counting process, In the tallying process, the allocation status of the medication instruction task is tallied for the pharmacist using the pharmacist terminal. [Appendix 7] An information processing system according to any one of Supplementary Notes 1 to 6, In the identification process, Acquire information indicating that the patient visiting the pharmacy has online medication instructions; The request process includes: An information processing system that is performed when online medication guidance is provided. [Appendix 8] An information processing system according to any one of Supplementary Notes 1 to 7, The information processing system is configured so that the server can switch to not providing the online medication instruction during or after the request processing. [Appendix 9] An information processing system according to any one of Supplementary Notes 1 to 8, A plurality of the pharmacist terminals are installed, In the request processing, the medication instruction task is presented to each pharmacist terminal in accordance with the following (B1) or (B2): (B1) Help history of each pharmacist using each pharmacist terminal at their own store or other stores (B2) Designation of a pharmacist or store, or bulk request without designation [Appendix 10] An information processing system according to any one of Supplementary Notes 1 to 9, In the request processing, the medication instruction task is presented to the pharmacist terminal in accordance with the following (C1) or (C2): (C1) Contents of the prescription of the patient visiting the pharmacy (C2) Information, symptoms, or medication history of the patient visiting the pharmacy [Appendix 11] An information processing system according to any one of Supplementary Notes 1 to 10, A plurality of the pharmacist terminals are installed, In the request processing, the medication instruction task is presented to each pharmacist terminal in accordance with the following (D1) or (D2): (D1) The situation or external environment of the location where each pharmacist terminal is installed (D2) Workload, activity, or evaluation of each pharmacist using each pharmacist terminal [Appendix 12] A program that causes a computer to execute each process of the information processing system according to any one of Supplementary Note 1 to Supplementary Note 11. [Appendix 13] An information processing method for causing a computer to execute each process of the information processing system according to any one of Supplementary Note 1 to Supplementary Note 11. [Explanation of symbols]

[0118] 1: Information processing system 2: Server (computer), 2a: Server (receipt computer system), 2b: Server (electronic medication history system), 2c: Server (online medication instruction system), 2c1: Data management department, 2d: Server (cash register system) 3: Terminal (computer), 3a: Terminal (receipt computer terminal), 3b1, 3b2: Terminal (medication history terminal), 3c1: Terminal (patient terminal), 3c2: Terminal (pharmacist terminal), 3cc1: Terminal (data terminal), 3d: Terminal (cash register terminal) 4: Communication network 10: Screen (Audit image capture screen), 11, 12, 13: Screen, 20: Screen (Request reception screen), 30: Screen (Call standby screen), 40: Screen (Call screen), 42: Screen (Call screen), 60: Screen (Call standby and call screen) 21, 22: Medication instruction task 40a, 42a: Main display area, 40b, 42b: Sub display area 51: control unit, 52: storage unit, 53: communication unit, 54: input unit, 55: output unit, 56: timing unit 61: Button (patient call / call start), 62: Thumbnail area, 63: Enlarged display area, 63a: Annotation function 70: Screen (reception patient list screen), 71: List F: Data, G: Audit information, g, g1, g2: Prescription image, h: Medication information image, S12b: Recognition processing, S13: Request processing, S23a, S23b: Call processing

Claims

1. An information processing system for providing online medication guidance at a pharmacy store, A server, a patient terminal at the pharmacy store, and a pharmacist terminal at a location different from the pharmacy store, the server performs an identification process, an acquisition of first data, a request process, and a call process; In the identification process, the server acquires patient identification information of a patient who has visited the pharmacy store, In the request process, a medication instruction task corresponding to the first data and the patient identification information is presented on the pharmacist terminal; In the communication process, the pharmacist terminal on which the presented medication instruction task has been selected is connected to the patient terminal so that they can communicate with each other; The first data is An information processing system, including prescription information.

2. An information processing system according to claim 1, An information processing system, wherein the first data is electronic prescription data.

3. 2. The information processing system according to claim 1, In the identification process, Acquire information indicating that the patient visiting the pharmacy has online medication instructions; The request process includes: An information processing system that is performed when online medication guidance is provided.

4. 2. The information processing system according to claim 1, In the request processing, the medication instruction task is presented together with at least a part of the information included in the first data and second data acquired by the server.

5. An information processing system according to claim 4, In the call processing, At least a part of the information included in the first data and the second data are displayed on the pharmacist terminal; The second data is An information processing system that processes data used for medication instructions.

6. An information processing system according to claim 5, The second data is An information processing system that includes, at least in part, an image.

7. The information processing system according to any one of claims 1 to 6, The information processing system is configured so that the server can switch to not providing the online medication instruction during or after the request processing.

8. The information processing system according to any one of claims 1 to 6, A plurality of the pharmacist terminals are installed, In the request process, the medication instruction task is presented to each pharmacist terminal in accordance with (B1) or (B2) below. (B1) Help history of each pharmacist using each pharmacist terminal at their affiliated store or other stores (B2) Designation of a pharmacist or store, or a blanket request without designation

9. The information processing system according to any one of claims 1 to 6, In the request processing, the medication instruction task is presented to the pharmacist terminal in accordance with (C1) or (C2) below. (C1) Contents of the prescription of the patient visiting the pharmacy (C2) Information, symptoms, or medication history of the patient visiting the pharmacy

10. The information processing system according to any one of claims 1 to 6, A plurality of the pharmacist terminals are installed, In the request process, the medication instruction task is presented to each pharmacist terminal in accordance with (D1) or (D2) below. (D1) The situation or external environment of the installation location where each pharmacist terminal is installed (D2) Workload status, activity status, or evaluation of each pharmacist using each pharmacist terminal

11. A program that causes a computer to execute each process of the information processing system according to any one of claims 1 to 6.

12. An information processing method for causing a computer to execute each process of the information processing system according to any one of claims 1 to 6.

Images