Information processing system, program, and information processing method

Abstract

We provide information processing systems and other tools that can improve the operational capabilities of pharmacy stores. [Solution] An information processing system is provided that provides online medication guidance 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, the identification processing acquires patient identification information of a patient who has come to the pharmacy store, the request processing presents a medication guidance task corresponding to the patient identification information on the pharmacist terminal, and the call processing connects the pharmacist terminal that has accepted the medication guidance task with the patient terminal so that they can communicate.

Description

Technical Field

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

Background Art

[0002] Patent Document 1 describes a medication guidance support device for providing highly accurate medication guidance at a pharmacy.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] At a pharmacy store, human resources are limited, and there is a problem that business response is delayed, for example, during congestion.

[0005] An object of the present invention is to provide an information processing system capable of improving the business response ability of a pharmacy store.

Means for Solving the Problems

[0006] According to the present invention, there is provided an information processing system for providing online medication guidance at a pharmacy store, including a server, a patient terminal of the pharmacy store, and a pharmacist terminal at a location different from the pharmacy store. The server executes identification processing, request processing, and call processing. In the identification processing, patient identification information of a patient who has come to the pharmacy store is acquired. In the request processing, a medication guidance task corresponding to the patient identification information is presented on the pharmacist terminal. In the call processing, the pharmacist terminal that has received the medication guidance task and the patient terminal are connected so as to be able to make a call.

[0007] According to the present invention, it is possible to effectively introduce online medication guidance within pharmacy stores and improve the operational capabilities of pharmacy stores. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1A shows an example of the overall configuration of the information processing system 1 of the embodiment. Figure 1B shows an example of the hardware configuration of each server 2 (2a to 2d) and each terminal 3 (3a to 3d) of the embodiment. [Figure 2] This block diagram schematically illustrates the processing content of Server 2 and Terminal 3, as well as the work flow of each individual, in the embodiment. [Figure 3] This diagram schematically illustrates the functions and various screens that Server 2c provides as a web application. [Figure 4] Figure 4A shows an example of a screen for sending audit images, etc., and Figure 4B shows an example of screens 11, 12, and 13 for displaying related functions related to audit images, etc. [Figure 5] Screen 20 in Figure 5A shows an example of the request reception screen of the pharmacist terminal 3c2, and screen 30 in Figure 5B shows an example of the call waiting screen of the pharmacist terminal 3c2. [Figure 6] Screen 40 in Figure 6A shows an example of the call screen of the pharmacist terminal 3c2, and screen 42 in Figure 6B shows an example of the call screen of the patient terminal 3c1. [Figure 7] Screen 60 shows another example of the call screen on the pharmacist terminal 3c2 (a call screen that also serves as a call waiting screen). [Modes for carrying out the invention]

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

[0010] 1. Configuration of the Information Processing System 1.1. Overall Structure Hereinafter, the pharmacy store visited by a patient will also be simply referred to as "the store." The information processing system 1 of the embodiment shown in Figure 1A provides online medication guidance to patients visiting the pharmacy store (the store) by a pharmacist at a different location (e.g., another store or medication guidance center). As shown in Figure 1, the information processing system 1 of the embodiment includes, as an example, a plurality of servers 2 (2a to 2d) and a plurality of terminals 3 (3a, 3b1, 3b2, 3c1, 3c2, 3cc1, 3d). Each server 2 and each terminal 3 are connected by a communication network 4. The communication network 4 is not limited and can be the Internet, an intranet, a LAN, or any combination thereof.

[0011] As an example, in a system with multiple servers 2(2a-2d), server 2a provides a medical billing system (medical accounting system), server 2b provides an electronic patient record system, server 2c provides an online medication guidance system, and server 2d provides a cash register system (e.g., a POS system). Servers 2a-2d may be independent of each other, but some or all of them may be able to cooperate with or integrate with each other.

[0012] The multiple terminals 3 include, for example, each terminal 3 within the pharmacy store (the store itself) and each terminal 3 in a location different from the store (e.g., another store, or any facility such as a medication guidance center). Specifically, each terminal 3 within the store includes, for example, a prescription terminal 3a at the counter, a patient terminal 3c1, a terminal 3 in the dispensing room (medication history terminal 3b1, image terminal 3cc1), and a cash register terminal 3d. Each terminal 3 in a location different from the store includes, for example, a pharmacist terminal 3c2 and a medication history terminal 3b2. For example, any hardware terminal located in the pharmacy store (the store itself) or in a location different from the store may log in (connect) to each server 2, and each hardware terminal may then function as each terminal 3. In this embodiment, medication history terminals 3b1 and 3b2 can access common medication history data, for example, through a cloud-based medication history system.

[0013] 1.2. Hardware Configuration Please refer to Figure 1B. For the sake of explanation, here we will refer to Server 2 and Terminal 3 collectively as "computers." As shown in Figure 1B, in this embodiment, each computer 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 each computer 2 and 3 are interconnected via a bus.

[0014] The control unit 51 has a physically structured circuit. This circuit executes each process to realize any function according to the code or instructions contained in the program. The control unit 51 is implemented, for example, by a data processing device built into the hardware. Therefore, the control unit 51 may also be described 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 ASIC (application-specific integrated circuit), or an FPGA (field programmable gate array).

[0015] The memory unit 52 has the function of storing various programs and data necessary for the operation of each computer 2 and 3. Here, the memory unit 52 is described without distinction between internal and external storage devices, and various storage media such as HDD (hard disk drive), SSD (solid state drive), flash memory, RAM (random access memory), and ROM (read-only memory) can be arbitrarily used in the memory unit 52. The memory unit 52 is also sometimes referred to as 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 the various functions of each of the computers 2 and 3.

[0017] The communication unit 53 transmits and receives various data between computers 2 and 3 (or between these and any other arbitrary computer) via the communication network 4. The communication may be either wired or wireless, and any communication protocol can be adopted. The communication unit 53 transmits various data to various devices according to instructions from the control unit 51. Also, the communication unit 53 receives various data via the communication network 4 and transmits it to the control unit 51.

[0018] <000009​​​​​​​​​​​ For example, if the input unit 54 is a touch panel, the input unit 54 and the display unit as the output unit 55 may be arranged opposite each other and have substantially the same size and shape.

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

[0023] Please note that the hardware configuration described above is merely an example. Furthermore, the form in which each server 2 in this embodiment is provided may be a dedicated physical server or an arbitrary virtual server. This point will be further explained in the modified examples described later.

[0024] 2. Operation of the Information Processing System The following describes an example of the business flow and system processing of the embodiment using Figure 2. In Figure 2, the interaction between each server 2 and each terminal 3 corresponds to system processing. The interaction between each terminal 3 and a human corresponds to arbitrary user interface (UI) input / output. This UI input / output includes arbitrary input operations and arbitrary outputs (e.g., visual, auditory, or tactile notifications via screen, sound, etc.). In Figure 2, as an example, the cooperation between servers 2a and 2b is schematically and simply shown with arrow lines. It should be noted that the present invention is not limited to specific server cooperation methods, and any cooperation can be adopted. Normally, various forms of server cooperation technology can be adopted depending on differences in manufacturers, whether or not it is cloud-based, etc., and cooperation can sometimes be complex. Furthermore, server cooperation can be established as needed, and as another example, one or both of servers 2a and 2b may be cooperated with server 2c, and server 2d may also be cooperated in addition.

[0025] Of the steps S1 to S31 in Figure 2, those corresponding to system processing (input / output or arithmetic processing) are executed in the control unit 51 by reading the program from the storage unit 52, thereby realizing the functional units for each process (e.g., identification unit, request unit, guidance unit, aggregation unit) on the control unit 51. For detailed examples of each screen (screens 10, 20, 30, 40, 42, and modified screen 60) of each terminal 3 (3b1 to 3c2), please refer to the section "3. Examples of Terminal Functions, etc." below.

[0026] It should be noted that the description of the embodiment is merely an example, and various modifications are possible. The order or content of each step S1 to S31 below can be replaced, combined, or omitted as needed, and other steps can be inserted between them. For convenience, the accounting system server 2d (see Figure 1) is not shown in Figure 2.

[0027] 2.1. Explanation of steps S0 to S12b (including identification process S12b) First, please focus on step S0 in the upper right of Figure 2. When a patient visits a pharmacy, they present various information at the pharmacy counter, and the pharmacy clerk inputs this information into the prescription terminal 3a (see S0 and S1). Specifically, for example, a paper prescription, a reception card, and an insurance card may be submitted to the pharmacy counter, or, for example, a My Number card may be submitted and an electronic prescription may be obtained via the My Number. As a result, prescription information and the patient's personal information (e.g., address, name, date of birth, insured person number, and My Number, etc.) are obtained by the server 2a (prescription computer) (see S2). The server 2a (prescription computer) issues sequential reception numbers, and these reception numbers are output to the prescription terminal 3a (see S3), and the pharmacy clerk obtains these reception numbers (see S4). The pharmacy clerk can then guide the patient based on the reception number. The reception number may also be issued by an automatic ticketing machine, etc. At least some of the data entry work for the medical billing system may be outsourced, and prescriptions and other data may be entered into the server 2a from other remote terminals connected via the communication network 4.

[0028] In this embodiment, as an example, in step S0, the presence or absence of online medication guidance for the visiting patient is obtained. One specific example of this "obtaining presence or absence" is "obtaining preference." In "obtaining preference," the visiting patient is asked by any means whether or not they wish to receive online medication guidance, and their response is obtained.

[0029] For example, when a patient visiting a pharmacy receives medical treatment at a hospital, the prescription for that treatment may have "online available" or "online medication guidance requested" written on it. This notation indicates whether or not the patient can receive online medication guidance at home without visiting the pharmacy. In other words, based on this notation, it is possible to determine whether dispensing, guidance, and medication can be performed without the original prescription. In contrast to this, in the implementation example (in-store online medication guidance), the normal procedure of receiving the original prescription at the store is followed, and online medication guidance is provided to the patient visiting the pharmacy within the store. The online medication guidance in the implementation example differs from the scenario envisioned by the "online available" notation on the prescription. Unless subject to other regulations (e.g., various rules of each local government), it is possible to provide online medication guidance in the implementation example without the "online available" notation on the prescription.

[0030] As described in the "Request Acquisition" section above, in this embodiment, patients visiting the pharmacy are asked whether they would like to receive online medication guidance. When obtaining this request, the advantages of online medication guidance (e.g., shorter waiting times) are explained, and the convenience for patients visiting the pharmacy is improved by providing them with information to help them make a decision.

[0031] Whether or not online medication guidance is provided can be obtained by any means and location, by any staff member, or by any device. For example, a pharmacy clerk could verbally confirm this with the patient at the counter, or it could be obtained through the patient's operation on a terminal (e.g., a tablet) at the front desk. Whether or not online medication guidance is provided can be managed in any way within the pharmacy's workflow. For example, as shown near step S0 in Figure 2, "paper-based management" is possible, and any paper document (e.g., prescription, medication record book, or any form) could be clearly marked with an arbitrary indicator (e.g., a sticky note) to indicate whether or not online medication guidance is provided. In certain cases (e.g., when the prescribed medication or the patient's symptoms are not suitable for online medication guidance), "Yes" may not be selected, and online medication guidance may be marked as "No (cancelled)" at any stage in the workflow. If online medication guidance is marked as "No," the workflow proceeds to another stage (not shown) where a pharmacist provides face-to-face medication guidance within the pharmacy. Examples of cases where the response is "None" include situations where the patient visiting the pharmacy does not wish to receive online medication guidance, or where online medication guidance is inappropriate for some reason.

[0032] Next, from step S5 onward, the operations in the dispensing room of the pharmacy proceed. Specifically, the pharmacist in the dispensing room obtains and views prescription information, etc., on the medication history terminal 3b1, performs an audit (prescription audit), checks the medication history etc. on the server 2b (electronic medication history system, see Figure 1A), and makes inquiries as necessary (see S5, S6). After dispensing, the pharmacist enters the dispensing information into the medication history terminal 3b1, which is then obtained by the server 2b (see S7, S8).

[0033] Next, a further audit (dispensing drug audit) is conducted in the dispensing room. The pharmacist obtains dispensing information using the medication history terminal 3b1 (see S9 and S10). The pharmacist in the dispensing room conducts the audit (dispensing drug audit), and if there are no problems, inputs the final audit results and audit images into the medication history terminal 3b1 (see S11). As a result, the server 2b obtains the final audit results (see S12). With the audit complete, the items to be handed to the patient (prescription drugs, medicine bags, drug instructions, etc.) are ready. Note that dispensing drug audit is sometimes referred to as dispensing drug "inspection," but in this embodiment, these are treated as having the same meaning.

[0034] In this embodiment, we provide an example of the specific operation of audits within the dispensing room (e.g., the type of terminal and procedures within the dispensing room), but this is merely an example. Please note that the specific contents of the flow in Figure 2 can be arbitrarily modified according to the operations of each pharmacy.

[0035] Next, for patients who have opted for online medication guidance, in this embodiment, as an example, a pharmacist in the dispensing room inputs patient identification information (e.g., reception number, name, etc.) and image F (e.g., audit image G, etc., details will be described later) into screen 10 of image terminal 3cc1 (see Figure 4A) (see S12a). The patient identification information is not limited to the reception number, but can be any information that can distinguish each patient (e.g., patient name, etc.). As a result, server 2c acquires the patient identification information (identification process S12b), and an instruction to provide online medication guidance to the specific patient is given to server 2c.

[0036] In one embodiment, server 2c is made to acquire (receive) "image F". Image F is "at least one image to be displayed on the pharmacist terminal 3c2 in request processing S13 or call processing S23a, S23". Image F can be, for example, "any image usable for transmitting information when making a request to a medication guidance pharmacist" or "any image usable for medication guidance". Image F is associated with patient identification information.

[0037] Specifically, "Image F" in the embodiment may be, for example, an "audit image," a "prescription image," a "medication information image," a "medication record image," a "dispensing record image," a "medication bag image," a "receipt image," a "receipt certificate image," a "reception number slip image," a "test result image," a "health check result image," a "limit management table image," or a "dispensing equipment output information image." One (one type) or more (multiple types) of each of the images listed here as examples can be used for Image F.

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

[0039] The "medication bag image" is an image of a medicine bag. The medicine bag contains information required by law (information that must be written on the container or packaging of the dispensed medicine, such as the patient's name, dosage and administration instructions, date of dispensing, name of the dispensing pharmacist, and name and address of the dispensing pharmacy, hospital, or clinic). The medicine bag may also contain other precautions (e.g., storage or usage precautions). The "receipt image" is an image of a receipt. The receipt is provided as a document that shows the breakdown of medical expenses, and is divided into categories such as "dispensing fee," "pharmaceutical management fee," and "medication fee," with the points and costs for each item listed. The "receipt details image" is an image of a receipt details document. The receipt details document is provided as a document that shows a more detailed breakdown of medical expenses than the receipt, and is listed as the cost of each prescribed medication.

[0040] The "Reception Number Slip Image" is an image of the reception number slip (see Figure 2, Step S4). The "Test Result Image" is an image of documents or data showing the test results (if any) of the visiting patient. The "Health Checkup Result Image" is an image of documents or data showing the results of the visiting patient's health checkup (if any, whether partial or complete). The "Upper Limit Management Sheet Image" is an image of the self-pay upper limit management sheet. The self-pay upper limit management sheet is used at the counter of medical institutions and pharmacies to confirm that the self-pay amount for a specified period (1 month) does not exceed the upper limit. The "Equipment Output Information Image" is an image of a form or data of "output information output from the equipment of the store." "Equipment of the store" may be any equipment in the dispensing room, for example (e.g., dispensing equipment). For example, in the case of dispensing equipment, the output information may include audit results, etc.

[0041] The above examples illustrate various images that can be used as image F. Some of these can be used independently, while others are intended to be used in combination with other images. Images intended for use in combination may be sent to server 2c together with images that can be used independently, or the necessary information may be sent to server 2c as text data, for example, along with these images intended for use in combination.

[0042] Multiple types of images may be used for image F. In this embodiment, for example, an audit image G, a prescription image H, and a drug information image J may be used as image F (see Figure 4A). Some of the images F may include patient identification information (e.g., patient's name). However, other images are not limited to the examples above and can be used. For example, "any other image capable of displaying the information or items shown in each of the images exemplified above" can be used as image F. For example, some of the images exemplified above can display information about the prescribed drug (e.g., appearance, contents, ingredients, quantity, usage, dosage, precautions for taking or storing the medication, date and time of dispensing, location or dispensing information, etc.), or information about the patient visiting the pharmacy (e.g., name, age, health check results, medical expense-related information, etc.). Thus, for example, "any image capable of displaying at least one of the information about the prescribed drug and the patient visiting the pharmacy" may be used as image F. Note that text information may be extracted from image F using OCR processing. Furthermore, the format of image F can be any image format, including both raster and vector images. Of course, PDF data can also be an example of image F. If there is a priority order based on the order in which patients are treated, that priority order may be entered on screen 10.

[0043] 2.2. Explanation of Request Processing S13 Next, server 2c executes the request processing (see S13). In request processing S13, server 2c presents the medication guidance task corresponding to the patient identification information (e.g., reception number) to the medication guidance pharmacist via screen 20 (see Figure 5A) of pharmacist terminal 3c2 (see S14). The pharmacist terminal 3c2 is located in a different location from the pharmacy where the patient is (e.g., another branch). When the medication guidance pharmacist selects (clicks) the desired medication guidance task (see S15), the selection information is sent to server 2c (see S16). If there is a priority instruction for the medication guidance task, the display content may be changed to prompt the medication guidance pharmacist to select according to the priority instruction.

[0044] 2.3. Explanation of call-related processing (including call processing S23a) Next, server 2c executes call-related processing for the selected medication guidance task according to the selection information (S16). The specific content of the call-related processing can be constructed 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 respectively (e.g., screens 30 and 40, see Figures 5B and 6A), and the screen transitions from call waiting to call execution. In the second example, a screen that integrates the call waiting function and the call function is used (e.g., screen 60, see Figure 7).

[0045] 2.3.1. First example (Screens 30, 40) To explain the first example, in this embodiment, as an example, server 2c displays screen 30 (see Figure 5B) for the selected medication guidance task on the pharmacist terminal 3c2 according to the selection information (S16), and puts it into call waiting state (see S17). At this point, the assignment has not yet been finalized, and it can be canceled by pressing the "back" button on screen 30. The medication guidance pharmacist checks the memo and image F (e.g., audit image G, prescription image H, drug information image J, etc., other images such as medication notebook images and dispensing record images can also be used) on screen 30 (see S18a). The medication history is also checked, but the medication guidance pharmacist may check it by accessing server 2b (electronic medication history system) themselves (see S18b), or as a modified example, servers 2b and 2c may be linked and the medication history may be displayed on screen 30. After that, if it is possible to start medication guidance, the connection operation is performed with the intention of accepting the task (see S19). In this embodiment, the connection operation is performed by clicking the "Patient Call / Start Call" button on screen 30 in Figure 5B. In response to the connection operation, the pharmacist terminal 3c2 transmits a connection instruction (or arbitrary connection information such as access information) (see S20).

[0046] In one embodiment, when a connection (or connection information) is transmitted in step S20, processing such as "medication guidance notification" is performed (see S21). In one embodiment, a medication guidance notification and patient identification information (e.g., reception number) are transmitted from server 2c to prescription terminal 3a. A specific example of the notification method will be explained in the following section, "3.2. Examples of Notification Functions". In one embodiment, a pharmacy clerk calls a patient with a specific reception number according to the medication guidance notification and guides them to the location where the patient terminal 3c1 is installed (e.g., any desk in an open space near the counter, a partitioned booth, or a private room, etc.), and the pharmacy clerk (or the patient) performs the "call start operation" on the patient terminal 3c1 (see S22). The call start operation is, for example, pressing the call start button displayed on the screen of the patient terminal 3c1 (e.g., the "Patient Call / Start Call" button on screen 30). Accordingly, the pharmacist terminal 3c2 confirms that the task has been accepted. Multiple patient terminals 3c1 may be installed within the same pharmacy. In this case, the medication guidance notification will include terminal designation information (an indication of which patient terminal 3c1 the patient should be directed to).

[0047] Next, in this embodiment, as an example, server 2c performs call processing (see S23a and S23b). In this process, server 2c connects pharmacist terminal 3c2, which has been assigned a medication guidance task, and patient terminal 3c1 to enable communication. During the connection, screen 40 (call screen: see Figure 6A) is displayed on pharmacist terminal 3c2, and screen 42 (call screen: see Figure 6B) is displayed on patient terminal 3c1.

[0048] According to the first example above, a pharmacist providing medication guidance can offer online medication guidance from outside their own pharmacy (see S24a), and patients visiting the pharmacy can receive this guidance (see S24b).

[0049] 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 described above. In the second example, screen 60 (see Figure 7) is used instead of screens 30 and 40 described above. In the second example, when transitioning from call waiting to call in progress, the screen does not change and screen 60 is maintained.

[0050] To describe the second example, in this embodiment, as an example, the server 2c displays a screen 60 (see Figure 7) for the selected medication guidance task on the pharmacist terminal 3c2 according to the selection information (S16). In this embodiment, as an example, the screen 60 is initially in a call waiting state (corresponding to S17). The screen 60 is provided with the functions of screens 30 and 40. In the second example, the screen 60 enables the execution of processes and tasks corresponding to each step S17, S18a, S19, and S20 of the first example.

[0051] In the second example, clicking the "Patient Call / Start Call" button (button 61) on screen 60 in Figure 7 may execute the following processes (x1) to (x4) as an example. (x1) A patient call notification is sent to the store (the store itself) (corresponding to step S21). (x2) The remote side (pharmacist terminal 3c2) enters a call waiting state. At this time, the following processes (x2-1) and (x2-2) are executed. (x2-1) The self-camera activates and the device enters a standby state for starting a call. (x2-2) The "Patient Call / Start Call" button (button 61) changes to the "End Call" button. In other words, button 61 is the "Call Start / End Operation Button". (x3) The call begins when the patient terminal 3c1 initiates the call (corresponding to steps S23a and S23b). The pharmacist providing medication guidance can then provide online medication guidance via screen 60. The location of the patient terminal 3c1 is arbitrary and may be, for example, installed at the dispensing counter in a store. (x4) Clicking the "End Call" button shown in (x2-2) above will end the call (see step S25 below).

[0052] In this second example, the pharmacist providing medication guidance can offer online medication guidance from outside their own pharmacy (see S24a), and patients visiting the pharmacy can receive this guidance (see S24b).

[0053] 2.3.3. End of call After the process exemplified in the first or second example above, once the medication guidance via online call is completed, server 2c receives a disconnection instruction (see S26) in response to the completion operation (see S25), and server 2c disconnects the connection. At this point, the task is completed.

[0054] 2.4. Steps S27-S31 (Post-medication guidance procedures) Subsequently, in this embodiment, for example, the server 2c displays guidance information (e.g., accounting guidance, accounting information, exchange ticket number, etc.) on the patient terminal 3c1 (see S27). The exchange ticket number may be printed from a ticket machine connected to the patient terminal 3c1. Upon receiving the guidance information, the patient proceeds to the counter or other designated location accordingly (see S28). A notification may be sent to the medical billing terminal 3a along with or instead of the patient terminal 3c1.

[0055] Upon completion of the call (connection disconnected S26), server 2c sends a "Medication Guidance Completion Notification" to the prescription terminal 3a at the same time as or before / after the display of guidance information (S27, S28) (see S29). Subsequently, the pharmacy clerk prepares for accounting, etc. (see S30), and the patient pays and receives their prescribed medication (see S31).

[0056] As described above, in this embodiment, the server 2c performs the identification process S12b, the request process S13, and the call processes S23a and S23b. This allows for the effective introduction of online medication guidance into the operation of pharmacy stores, enabling the effective utilization of human resources outside the store (pharmacists at other stores) and improving the operational capabilities of the pharmacy stores. Providing face-to-face service at the pharmacy store offers various advantages (e.g., the sense of security from face-to-face administrative procedures and medication guidance, the ability to receive and manage original prescriptions, the ability to hand over prescribed medications directly, etc.). This embodiment makes it possible to achieve both these various advantages of pharmacy store service and improved operational capabilities. In the past, during busy periods, pharmacists sometimes had to be sent from headquarters or other stores, incurring time and expense, to provide medication guidance. However, according to this embodiment, the effective introduction of online medication guidance has the advantage of saving such time and expense. Preferably, the information processing system of this embodiment is introduced without making significant changes to store operations (more preferably without any changes to basic store operations).

[0057] In this embodiment, as an example, during the request processing S13 or call processing S23a, an audit image G or the like is displayed on the pharmacist terminal 3c2 as an example of image F (see Figures 4A, 5A-6A, and 7). This improves convenience during request confirmation or calls.

[0058] 3. Examples of terminal functions, etc. 3.1. Examples of login and screen transitions, etc. Please refer to Figure 3. In this embodiment, as an example, server 2c provides an online medication guidance service in the form of a web application. Each terminal 3 in the pharmacy store logs in with a pre-registered store account, as an example. On the subsequent mode selection screen, selecting the dispensing room mode provides the functions of the image terminal 3cc1 (e.g., display of screen 10), and selecting the counter mode provides the functions of the patient terminal 3c1 (e.g., display of screen 42).

[0059] Each terminal 3 located outside the store (e.g., other pharmacy stores) logs in with the pre-registered pharmacist account. This provides the functions of pharmacist terminal 3c2 (e.g., display of screens 20, 30, and 40, notifications to other terminals 3, etc.). After logging in, one or more pharmacy stores linked to the account (e.g., assigned pharmacist, affiliated pharmacist, same chain, or same group) may be displayed in a list, and related information may also be displayed.

[0060] 3.2. Examples of notification functions Figure 3 shows "Notification," which refers to the notification function of terminal 3. In this embodiment, as an example, the terminal OS functions of each terminal 3 may be used to output an arbitrary notification sound, notification message, or notification image. Specifically, the pharmacist terminal 3c2 may be able to access the OS settings and message or alarm setting functions of each terminal 3 in the pharmacy store. The notification function settings may be provided using any communication function between the terminals 3, or through the web application of server 2c.

[0061] Specifically, in this embodiment, at least three patterns are adopted as examples of how the notification function of the pharmacist terminal 3c2 is used. Each pattern includes each type of notification (e.g., playing a notification sound or displaying a message). • Pattern 1: Patient calling and call initiation • Second pattern: Calling a pharmacist (e.g., reporting a question about a prescription) • Pattern 3: Accounting communication

[0062] The first type of notification occurs, for example, when the "Call Patient / Start Call" button is pressed on screen 30 (see Figure 5B), which will be described later. This notification corresponds to step S21 (Medication Guidance Notification) in Figure 2.

[0063] In the second and third notification patterns, a message is displayed along with a notification sound, for example, and the timing of this display is when the "Call Pharmacist" or "Payment Contact" button is pressed on screen 30 (see Figure 5B), which will be described later. Note that the third notification pattern (payment contact) after the medication guidance completion operation (S25) corresponds to the medication guidance completion notification (S29).

[0064] In the first and third patterns, the notification function is activated on any staff terminal at the reception desk, for example (e.g., prescription terminal 3a). In some cases, another terminal at an adjacent counter, for example (e.g., electronic medical record terminal), may also be used. In the second pattern, when calling a pharmacist at the store (e.g., when a prescription inquiry arises), the notification function of any terminal in the dispensing room, for example (e.g., medical record terminal 3b1 or image terminal 3cc1), may also be activated.

[0065] In this embodiment, it is possible to set which notification to send at each terminal 3 to correspond to the first to third patterns described above. For example, notification conditions may be set so that any terminal at the counter (e.g., prescription terminal 3a, etc.) can receive notifications for the first and third patterns, and any terminal in the dispensing room (e.g., medication history terminal 3b1 or image terminal 3cc1) can receive notifications for 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 preferable to be able to set multiple different notification contents (e.g., alarm sound, etc.). In addition, it may be possible to select whether the alarm sound is looped or not.

[0066] 3.3. Example of a terminal screen Figure 4A shows an example of screen 10 displayed on image terminal 3cc1. Screen 10 is an example of an image transmission screen for sending image F. The pharmacist in the dispensing room enters patient identification information (e.g., reception number) via screen 10, clicks the "Capture Image" button, attaches image F, adds notes as needed, and presses the send button. Server 2c then receives all of this information. The "Come back later" checkbox is an example of a priority setting function; checking it and pressing the send button reflects the priority in the transmitted information. It is preferable that image F is clear enough to accurately visualize the information of the object being imaged (e.g., shape, color, pattern, letters, numbers, symbols, etc.). For example, it is preferable that the audit image G is actually captured with the prescribed medications arranged in an easily visible manner on a tray or the like.

[0067] Figure 4B shows examples of screens 11-13 used for status confirmation and other purposes in the embodiment. The image terminal 3cc1 can display screen 11 (status confirmation screen), and pressing the "List of Captured Images" button transitions to screen 12 (image list screen). Screen 12 displays a list of sent images F (e.g., audit image G). Filtering functions such as sending date (e.g., today) are also available. If the user initially planned for online medication guidance but wants to change to in-person guidance, they may be able to cancel the corresponding medication guidance task by specifying the desired image F and pressing the cancel button. Screen 12 also provides status buttons ST. The status buttons ST include "Received," "Pharmacist Confirmed," "On Hold," and "Guidance Completed," and can display the status of the received images. Each status button ST does not necessarily have to be a button that triggers an event when clicked; a checkbox that toggles on / off with each click may be used. For example, if all four status buttons ST are turned on and the "Search" button is clicked, all images with all statuses will be displayed. For example, by turning off all options except "Received" and performing a search, you can filter and display only images with the status "Received". For example, by turning on the "Pharmacist Confirmation" button and clicking the "Search" button, you can filter and display only "Image F already opened on the pharmacist terminal" (i.e., audit images that have been confirmed by a pharmacist). By pressing the "Messages" button, screen 13 (message window) opens, allowing you to check the message reception history. This makes it possible to check messages from the remote pharmacist terminal 3c2.

[0068] 3.4. Example of a pharmacist's terminal screen 3.4.1. Request Received Screen Screen 20 in Figure 5A is displayed on the pharmacist terminal 3c2 as a result of the request processing (S13 in Figure 2). Screen 20 is a request reception screen, and is the screen for receiving requests for medication guidance tasks. The screen layout of screen 20 displays each medication guidance task as tiles, as an example. In this embodiment, medication guidance tasks 21 and 22 are presented along with images F, as an example. Specifically, in this embodiment, as an example, as shown in Figure 5B, medication guidance tasks 21 and 22 are presented along with audit images G, etc. (e.g., overall thumbnail display). In the example in Figure 5A, medication guidance task 21 corresponding to reception number 55 (e.g., audit image G1, etc. attached as image F) and medication guidance task 22 corresponding to another reception number 56 (e.g., audit image G2, etc. attached as image F) are shown. The status button ST described in Figure 4B is also provided on screen 20. When the desired medication guidance task (e.g., medication guidance task 21) is selected (clicked), the screen transitions to screen 30 in Figure 5B.

[0069] For example, various display switching menus may be provided on screen 20, etc., which may allow for filtering or rearranging the display of medication guidance tasks. The display switching menu may consist of one or more of the following menus (M1) to (M5), or a combination thereof. (M1) Filter or sort display by requesting pharmacy store. (M2) Displayed in order of request time (M3) Ranking displayed by reception number (M4) Display in order of priority (e.g., "Urgent", "Later", "Standard", etc.) (M5) Filter and display only requests that specify the user.

[0070] 3.4.2. First example of call-related screen Q The dashed line Q in Figure 3 refers to call-related screens associated with the call function, specifically including screens 30 and 40. Screen 30 in Figure 5B is an example of a call waiting screen. As an example, medication guidance 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 designated 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, as well as a status display for this medication guidance task (cancelled, on hold, completed). "On hold" means that after being interrupted for a query or other reason, the call is waiting to be resumed remotely, not at the store. The "Call Pharmacist" button can send messages and notifications to image terminal 3cc1, and the "Contact Accounting" button can send messages and notifications to prescription computer terminal 3a. Calling a pharmacist can be used, for example, for a query. When the "Call Patient / Start Call" button is pressed, a message is sent to patient terminal 3c1, and a medication guidance notification (see S21 in Figure 2) is issued. At the same time, a notification is also sent to any terminal used by administrative staff, etc. (e.g., prescription computer terminal 3a). When patient terminal 3c1 responds (connection initiated), the screen transitions to screen 40 in Figure 6A.

[0071] Screen 40 in Figure 6A is an example of a call screen on 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 to turn on background control functions (e.g., background blur function) or audio subtitles may also be provided.

[0072] In this embodiment, for example, the aforementioned image F may be displayed on the call waiting screen (e.g., screen 30) or the call screen (e.g., screen 40). In Figures 5B and 6A, audit image G1 is displayed as an example of image F, but any other image can be displayed by clicking the image switching operation (e.g., the "<" and ">" buttons below audit image G1 in Figures 5B and 6A).

[0073] Screen 40 in Figure 6A is the call screen of pharmacist terminal 3c2 connected via call processing (S23a). As an example, pharmacist terminal 3c2, which has selected medication guidance task 21 (reception number: 55), is connected to patient terminal 3c1, which is linked to the corresponding patient identification information (e.g., reception number 55), and is able to communicate via call. The main display area 40a shows the patient (reception number: 55) as captured by the camera of patient terminal 3c1. The sub-display area 40b shows a self-camera image (the pharmacist providing medication guidance). In this embodiment, as an example, audit image G1, etc., are also displayed on screen 40.

[0074] 3.4.2. Second example of call-related screen Q The call-related screen Q may be integrated into a single screen 60 (see Figure 7). Screen 60 is a screen that can be used for both call waiting and call. On screen 60, similar to screen 30, for example, a "back" button (cancel function), a memo entry field, an "image confirmation" function (e.g., any image F such as audit image G, prescription image H, drug information image J can be confirmed), a "pharmacist call" function (inquiry function), a "patient call / start call" function, an "accounting contact" function, and a medication guidance status function are provided. On screen 60, similar to screen 40 (see Figure 6A), a main display area 40a, a sub-display area 40b, and an "image sharing" function are provided.

[0075] On screen 60, the following image confirmation functions are provided: a thumbnail area 62, an enlarged display area 63, and an annotation function 63a (e.g., selection of a writing pen, writing and erasing). When an arbitrary thumbnail image is selected from the thumbnail area 62 (for example, audit image G1 is selected in Figure 7), the selected image is displayed enlarged in the enlarged display area 63 on the right side of screen 60. Clicking the "Share Image" button then shares the image with the patient terminal 3c1. The annotation function 63a can use, for example, button-style radio buttons, and allows arbitrary drawing on the image in the enlarged display area 63 (e.g., drawing shapes, drawing with a pen, entering text, etc.). The image with the drawing superimposed is also shared with the patient terminal 3c1. Even while sharing the image, clicking the "Enlarge Call Screen" button enlarges the patient's face as seen on the patient terminal 3c1 and displays it in the enlarged display area 63. Generally, the patient's face is displayed enlarged during the initial greeting, and thereafter, audit images, etc., can be shared to provide medication guidance.

[0076] 3.5. Example of a patient terminal screen Screen 42 in Figure 6B is an example of the screen of a patient terminal 3c1 (e.g., window 1) connected via call processing (S23b). The main display area 42a shows the pharmacist providing medication guidance as captured by the camera of the pharmacist terminal 3c2. The sub-display area 42b shows the patient (visiting the pharmacy) as captured by the self-camera.

[0077] When image sharing is performed on the pharmacist terminal 3c2, the shared image can be displayed in the main display area 42a. When image sharing occurs, additional sub-display areas may be added to show the pharmacist's face. Any one of the images F can be shared as the shared image.

[0078] 4. Variations of request processing In this 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 (including chain stores, etc.), or any location not limited to pharmacy stores. The number of locations where pharmacist terminals 3c2 are installed can be any number of two or more, and they may be installed comprehensively in, for example, many chain stores. "The same location" may be, for example, within the same building. As an example of "the same location", one could consider setting up a "medication guidance center" where multiple pharmacists provide online medication guidance.

[0079] In request processing S13, medication guidance tasks may be presented to each pharmacist terminal 3c2 according to the "individual specific circumstances" (e.g., decision on whether to present or distribute). Individual specific circumstances may include, for example, "current situation, condition, environment, attributes, geography, time, designation (agreement), evaluation, or history" regarding "prescription, pharmacist, terminal location (store, etc.), or visiting patient, etc." Individual specific circumstances may also 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 circumstances.

[0080] (B1) Examples include the store to which each pharmacist belongs (using pharmacist terminal 3c2), or the history of helping out at other stores. For example, this could include past help history (e.g., number of times or total hours worked helping out at other stores), whether the store is nearby (e.g., priority given to stores closer in distance, or stores within a specified distance), or whether it is a pharmacy located in front of a clinic of a similar medical specialty. The data from the "aggregation processing" described below may also be used. (B2) Examples include specifying a pharmacist or store, or making a bulk request without specifying a particular pharmacist or store. For example, the input field on image terminal 3cc1 may include a specification menu that allows specifying one or more specific pharmacists or one or more specific pharmacy stores. For example, the requesting store and the receiving 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 providing help at a physical store. Bulk requests are also possible.

[0081] (C1) The contents of prescriptions from patients visiting the pharmacy can be considered as an example. For example, the ease of making a request based on the prescription content may be determined. For example, in order to increase turnover during busy periods, a process may be adopted to automatically pick out prescriptions that are easy to request from other stores (e.g., single acute patients with common colds, etc.). Prescription information may be shared between servers 2a and 2c. (C2) Examples include patient information, symptoms, or medication history. Similar to (C1) above, a process may be adopted to automatically pick up individual patient information, symptoms, or medication history that is easy to request from other stores. Patient information, etc., may be shared between servers 2a, 2b, and 2c.

[0082] (D1) The conditions or external environment of the installation location where each pharmacist terminal 3c2 is installed can be considered. Installation locations can be other pharmacy branches or medication guidance centers. The external environment or store conditions of each pharmacy branch (where each pharmacist terminal 3c2 is installed) can be considered as an example. The external environment may be, for example, weather information or traffic congestion in the area of ​​each branch or medication guidance center obtained from the internet. For example, there is a tendency for more customers to visit the pharmacy in good weather than in bad weather. The conditions of the installation location may be, for example, the number of patients visiting each branch or the staffing situation, or any situation within each branch or medication guidance center (e.g., temporary closure). Based on these, medication guidance tasks may be allocated in a way that avoids, for example, load concentration. As a measure for BCP (Business Continuity Plan), various emergencies may be included in the conditions or external environment of the installation location. Various emergencies 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, requested tasks may be assigned in a way that prioritizes normal stores (e.g., stores relatively far from the emergency site) over stores experiencing an emergency (e.g., stores in or near the emergency site). (D2) Examples include the workload, activity status, or evaluation of each pharmacist. For example, data may be collected on the work status, workload, and other recent status of each pharmacist using each pharmacist terminal 3c2. The data from the "aggregation processing" described later may also be used.

[0083] Two or more of the above (B1) to (D2) can be combined with each other. Furthermore, for example, the data management unit 2c1 of server 2c may store and manage each of the above (B1) to (D2) information, and medication guidance tasks may be allocated based on the data stored in the data management unit 2c1. In addition, depending on the specific circumstances (e.g., (B1) to (D2) above), if, for example, no suitable candidate recipient can be found (or task requests are currently unavailable), or if, for example, the suitability / unsuitability of online medication guidance is determined to be unsuitable, this fact may be notified to any terminal (e.g., prescription terminal 3a or image terminal 3cc1, etc.).

[0084] While various specific situations have been given as examples above, it is not always necessary to assume the existence of multiple pharmacist terminals 3c2. For example, in the request processing S13, a medication guidance task may be presented to one pharmacist terminal 3c2 depending on (C1) or (C2). As in this example, the ability to request a task from a single pharmacist terminal 3c2 may be determined based on the specific situation.

[0085] 5. Aggregation Processing In this embodiment, for example, server 2c may further perform aggregation processing. Aggregation processing can be performed on any item, and the aggregated data can be managed individually for each pharmacist account or each pharmacy store. In addition, arbitrary aggregated data may be shared between the servers 2c of each pharmacy store via data communication.

[0086] In this embodiment, as an example of aggregation processing, the assignment status of medication guidance tasks is aggregated for each pharmacist using the pharmacist terminal 3c2. "Assignment status" may include, for example, the number of tasks accepted, the number of tasks completed, or the number of tasks nominated, and may include two or more of these. After task nomination, accepted and declined tasks may be aggregated together or separately. The number of tasks accepted by each pharmacist may be aggregated together or by store, etc., as part of the help history at other stores or activity status. An evaluation of each pharmacist may be recorded based on the task assignment status. Aggregation processing can be performed, for example, in the data management unit 2c1 within the server 2c, but is not limited to this, and may be performed in any database system (not shown) outside the server 2c, for example.

[0087] 6. Variations, etc. 6.1. Modification of business processes, etc. The business flow and system processing shown in Figure 2 can be modified in various ways. For example, in the embodiment, in the identification process S12b, the server 2c obtains patient identification information (e.g., reception number) via the image terminal 3cc1, and various processes are executed in association with this patient identification information, but it is not limited to this. For example, as a variation of the identification process, the identification process may be realized by having "any entity" input patient identification information (e.g., reception number) to the server 2c from "any terminal" at "any timing".

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

[0089] For example, server 2c may acquire "information indicating that online medication guidance is available for visiting patients." Server 2c may store this "information" in a table or the like, and if online medication guidance is "available", execute request processing S13 or send arbitrary notifications to the prescription terminal 3a or image terminal 3cc1, etc. For example, the "desire" for online medication guidance 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 other servers 2 (e.g., server 2a or server 2b).

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

[0091] Note that steps S22 and S30, indicated by the dashed box Z in Figure 2, use the medical billing terminal 3a as an example of hardware, but are not limited to this. At least one of the processes in steps S22 and S30 may be performed on a terminal other than the medical billing terminal 3a.

[0092] 6.2. Cancellation and History Management of Medication Counseling Tasks Server 2c may switch the online medication guidance status from "enabled" to "disabled" during or after request processing S13. This switch may also be possible at each terminal 3 (e.g., prescription terminal 3a, image terminal 3cc1, patient terminal 3c1, or pharmacist terminal 3c2, etc.). A history of the switch may be saved.

[0093] Server 2c may store and manage the history of online medication guidance for each patient visiting the pharmacy, and may perform various processes based on the history. For example, Server 2c may output the history of online medication guidance, or recommendation notifications (whether images or audio, etc.) based on the history, to any terminal 3.

[0094] 6.3. Priority assignment function Priority setting functions (e.g., "Come back later" checkbox) may be displayed on any screen of several terminals 3 (e.g., 3a, 3c2), not just on image terminal 3cc1. For example, a priority setting menu may be provided, and it may be possible to set multiple types of priorities (e.g., "Urgent (or Critical)", "Later", "Standard", or time-specified (e.g., 11:00)). For example, an example of using "Later" is when a patient who has checked in leaves the pharmacy and then returns.

[0095] 6.4. Imaging equipment for image F Image F is preferably a clear and easily viewable image of the subject being imaged (for example, prescription drugs in the case of audit image G). Image acquisition equipment for Image F may be provided, for example, an imaging terminal (e.g., a smartphone or tablet), a fixing device for the terminal (e.g., a flexible arm), and a mounting section (e.g., a tray, etc.) for placing the subject being imaged (e.g., prescription drugs, etc.) may be prepared. The imaging terminal can transmit Image F to the image terminal 3cc1, for example, by wireless communication. If the image terminal 3cc1 is a camera-equipped terminal, it may also function as the imaging terminal.

[0096] In addition, audit images may be captured by "auditing equipment installed in the dispensing room." This auditing equipment can be a variety of known types, such as a standalone device, or it may be a terminal of a dispensing audit system (also called a dispensing audit support system, drug inspection support system, audit support system, dispensing weighing audit system, medical drug prescription audit system, etc.). The image terminal 3cc1 may receive audit image data from this auditing equipment and transmit it to the server 2c.

[0097] 6.5. Modified versions of each terminal 3 The patient terminal 3c1 may be implemented using the patient's own device (e.g., a smartphone). The patient may access the server 2c on their own device via a browser or by installing an app, and use their own device as the patient terminal 3c1 to receive online medication guidance within the pharmacy. The patient account may be managed by the server 2c.

[0098] 6.6. Other In this embodiment, each server 2 can adopt any configuration capable of providing "server functionality in a client-server model." Each server 2 is any logical and functional component for providing data, functionality, or processing power in response to requests from clients (each terminal 3). Each server 2 is not limited to a physical server (e.g., on-premises or using a data center), 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 infrastructure such as AWS (Amazon Web Services). Each server 2 may also be a web application (e.g., see Figure 3) built on the cloud using a service model such as SaaS (Software as a Service), PaaS (Platform as a Service), IaaS (Infrastructure as a Service), or XaaS (Everything as a Service). Among the multiple servers 2, some may be physical servers and others may be virtual servers, etc.

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

[0100] In the embodiment, a program or information processing method can also be provided that causes a computer to execute each of the processes of the information processing system 1 described above. It should be noted that in this program or information processing method, each of the processes of the embodiment can be executed by "any computer," and it is optional whether the server is the entity executing each process (or whether it is server-side processing). For example, some or all of the processes of the embodiment may be executed by a client (e.g., terminal 3) (if all are executed, only communication between terminals 3 is possible, and the server can be omitted). Furthermore, each of the features of the above embodiment and modifications can independently constitute the invention and can be combined as appropriate. It should be noted that the scope of various modifications, applications, and uses that a person skilled in the art may make as needed is also included in the gist (technical scope) of the present invention.

[0101] Furthermore, the information processing system 1 described above may also include combinations of the features shown in the following appendices. These combinations are shown below.

[0102] [Note 1] An information processing system that provides online medication guidance at pharmacy stores, The system comprises a server, a patient terminal at the pharmacy store, and a pharmacist terminal at a location different from the pharmacy store. The aforementioned server performs identification processing, request processing, and call processing. In the aforementioned identification process, patient identification information of a patient who has visited the pharmacy store is obtained, In the aforementioned request processing, the patient identification information and the corresponding medication guidance task are presented on the pharmacist's terminal. The aforementioned call processing involves an information processing system that connects the pharmacist terminal, which has been assigned the medication guidance task, and the patient terminal in a way that enables communication.

[0103] [Note 2] The information processing system described in Appendix 1, The server is made to acquire at least one image. An information processing system in which the at least one image is an image to be displayed on the pharmacist terminal during the request processing or call processing.

[0104] [Note 3] The information processing system described in Appendix 2, An information processing system in which at least one image is selected from the group consisting of audit images, prescription images, drug information images, medication record images, dispensing record images, medicine bag images, receipt images, receipt certificate detailed images, reception number slip images, test result images, health checkup result images, upper limit management table images, and equipment output information images.

[0105] [Note 4] An information processing system as described in Appendix 2 or Appendix 3, An information processing system in which at least one image includes an image for transmitting information at the time of a request in the request processing, or an image used for medication guidance in the call processing.

[0106] [Note 5] An information processing system described in any one of the appendices 2 to 4, An information processing system that, in the aforementioned request processing, presents the medication guidance task along with at least one image.

[0107] [Note 6] An information processing system described in any one of the appendices 2 to 5, An information processing system that, in the aforementioned call processing, displays the at least one image on the call screen of the pharmacist's terminal.

[0108] [Note 7] An information processing system described in any one of the appendices 1 to 6, The aforementioned server further performs aggregation processing, The aforementioned aggregation process involves an information processing system that aggregates the assignment status of medication guidance tasks for pharmacists using the pharmacist terminal.

[0109] [Note 8] An information processing system described in any one of the appendices 1 to 7, In the aforementioned identification process, We obtained information indicating that the aforementioned patient who visited the pharmacy received online medication guidance. The aforementioned request processing is, An information processing system used when online medication guidance is provided.

[0110] [Note 9] An information processing system described in any one of the appendices 1 to 8, The server is an information processing system configured to be able to switch off online medication guidance during or after the processing of the request.

[0111] [Note 10] An information processing system described in any one of the appendices 1 to 9, Multiple pharmacist terminals are installed, The aforementioned request processing system presents the medication guidance task to each pharmacist's terminal according to (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 general request without designation.

[0112] [Note 11] An information processing system described in any one of the appendices 1 to 10, In the aforementioned request processing, an information processing system presents the medication guidance task to the pharmacist terminal according to (C1) or (C2) below. (C1) Contents of the prescription of the aforementioned patient (C2) Information, symptoms, or medication history of the patient who visited the pharmacy.

[0113] [Note 12] An information processing system described in any one of the appendices 1 to 11, Multiple pharmacist terminals are installed, The aforementioned request processing includes an information processing system that presents the medication guidance task to each pharmacist's terminal according to (D1) or (D2) below. (D1) The location or external environment where each pharmacist terminal is installed (D2) The workload, activity status, or evaluation of each pharmacist using each pharmacist terminal.

[0114] [Note 13] A program that causes a computer to execute each of the information processing system processes described in any one of the appendices 1 to 12.

[0115] [Note 14] An information processing method in which each process of the information processing system described in any one of the appendices 1 to 12 is executed by a computer. [Explanation of Symbols]

[0116] 1: Information Processing System 2: Server, 2a: Server (Prescription System), 2b: Server (Electronic Medical Record System), 2c: Server (Online Medication Guidance System), 2c1: Data Management Department, 2d: Server (Cash Register System) 3: Terminal, 3a: Terminal (reception terminal), 3b1, 3b2: Terminal (medication history terminal), 3c1: Terminal (patient terminal), 3c2: Terminal (pharmacist terminal), 3cc1: Terminal (image terminal), 3d: Terminal (cash register terminal) 4: Communication Network 10: Screen (Audit image capture screen), 11, 12, 13: Screens, 20: Screen (Request reception screen), 30: Screen (Call waiting screen), 40: Screen (Call screen), 42: Screen (Call screen), 60: Screen (Combined screen for call waiting and call in progress) 21, 22: Medication guidance tasks 40a, 42a: Main display area, 40b, 42b: Sub-display area 51: Control unit, 52: Memory unit, 53: Communication unit, 54: Input unit, 55: Output unit, 56: Timing unit 61: Button (Patient Call / Initiate Call), 62: Thumbnail Area, 63: Enlarged View Area, 63a: Annotation Function F: Image (at least one image), G, G1, G2: Audit image, H: Prescription image, J: Drug information image, S12b: Identification processing, S13: Request processing, S23a, S23b: Call processing

Claims

1. An information processing system that provides online medication guidance at pharmacy stores, The system comprises a server, a patient terminal at the pharmacy store, and a pharmacist terminal at a location different from the pharmacy store. The aforementioned server performs identification processing, request processing, and call processing. In the aforementioned identification process, patient identification information of a patient who has visited the pharmacy store is obtained, In the aforementioned request processing, the patient identification information and the corresponding medication guidance task are presented on the pharmacist's terminal. The aforementioned call processing involves an information processing system that connects the pharmacist terminal, which has been assigned the medication guidance task, and the patient terminal in a way that enables communication.

2. The information processing system according to claim 1, The server is made to acquire at least one image. An information processing system in which the at least one image is an image to be displayed on the pharmacist terminal during the request processing or call processing.

3. The information processing system according to claim 2, An information processing system in which at least one image includes one or more images selected from the group consisting of audit images, prescription images, drug information images, medication record images, dispensing record images, medicine bag images, receipt images, receipt certificate detailed images, reception number slip images, test result images, health checkup result images, upper limit management table images, and equipment output information images.

4. The information processing system according to claim 2, An information processing system in which at least one image includes an image for transmitting information at the time of a request in the request processing, or an image used for medication guidance in the call processing.

5. The information processing system according to claim 2, An information processing system that, in the aforementioned request processing, presents the medication guidance task along with at least one image.

6. The information processing system according to claim 2, An information processing system that, in the aforementioned call processing, displays the at least one image on the call screen of the pharmacist's terminal.

7. The information processing system according to claim 1, The aforementioned server further performs aggregation processing, The aforementioned aggregation process involves an information processing system that aggregates the assignment status of medication guidance tasks for pharmacists using the pharmacist terminal.

8. The information processing system according to claim 1, In the aforementioned identification process, We obtained information indicating that the aforementioned patient who visited the pharmacy received online medication guidance. The aforementioned request processing is, An information processing system used when online medication guidance is provided.

9. The information processing system according to claim 1, The server is an information processing system configured to be able to switch off online medication guidance during or after the processing of the request.

10. The information processing system according to claim 1, Multiple pharmacist terminals are installed, The aforementioned request processing system presents the medication guidance task to each pharmacist terminal according to (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 general request without designation.

11. The information processing system according to claim 1, An information processing system that, in the aforementioned request processing, presents the medication guidance task to the pharmacist terminal according to (C1) or (C2) below. (C1) Contents of the prescription of the patient who visited the pharmacy. (C2) Information, symptoms, or medication history of the patient who visited the pharmacy.

12. The information processing system according to claim 1, Multiple pharmacist terminals are installed, The aforementioned request processing includes an information processing system that presents the medication guidance task to each pharmacist terminal according to (D1) or (D2) below. (D1) Conditions or external environment of the installation location where each pharmacist terminal is installed (D2) The workload, activity status, or evaluation of each pharmacist using each pharmacist terminal.

13. A program that causes a computer to execute each of the processes of the information processing system described in any one of claims 1 to 12.

14. An information processing method comprising executing each process of the information processing system described in any one of claims 1 to 12 using a computer.

Images