Information processing system, program, and information processing method
The information processing system addresses the operational challenges of pharmacy stores by enabling online medication instruction through a server and terminals, improving efficiency and response times.
Patent Information
- Application Number
- JP2025003139
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2025-01-08
- Publication Date
- 2025-05-16
- Estimated Expiration
- 2045-01-08
AI Technical Summary
Pharmacy stores face challenges in efficiently managing operations due to limited human resources, often resulting in delayed responses during busy periods.
An information processing system is introduced that enables online medication instruction, comprising a server, a patient terminal at the pharmacy store, and a pharmacist terminal located elsewhere. The system executes identification, request, and call processing to facilitate online medication guidance.
The system effectively improves the operational capabilities of pharmacy stores by enabling efficient online medication instruction, reducing the need for on-site pharmacist presence during busy times, and enhancing business response capabilities.
Smart Images

Figure 0007678637000001_ABST
Abstract
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, and there is an issue of delays in responding to business operations, for example, when it is crowded.
[0005] An object of the present invention is to provide an information processing system capable of improving 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, the information processing system comprising a server, a patient terminal at the pharmacy store, and a pharmacist terminal at a location different from the pharmacy store, the server executing an identification process, a request process, and a call process, the identification process acquiring patient identification information of a patient visiting the pharmacy store, the request process presenting a medication instructions task corresponding to the patient identification information on the pharmacist terminal, and the call process connecting the pharmacist terminal that has been assigned the medication instructions task to the patient terminal so that they can communicate with each other.
[0007] According to the present invention, online medication instructions can be effectively introduced within a pharmacy store, thereby improving the business response capabilities of the pharmacy store. [Brief description 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 the embodiment. [Diagram 2] 2 is a block diagram illustrating a schematic example of the processing contents of a server 2 and a terminal 3 and the work flow of each staff member in the embodiment. FIG. [Diagram 3] 2 is a diagram showing a schematic example of functions and screens provided by the server 2c as a Web application. FIG. [Figure 4] A screen 10 in FIG. 4A shows an example of an inspection image transmission screen, and FIG. 4B shows examples of presentation screens 11, 12, and 13 for related functions related to the inspection image and the like. [Diagram 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 of the pharmacist terminal 3c2, and a screen 42 in FIG. 6B shows an example of a call screen of the patient terminal 3c1. [Figure 7] Screen 60 shows another example of the call screen of the pharmacist terminal 3c2 (a call screen that also serves as a call waiting screen). DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[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 attached, 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 store." The information processing system 1 of the embodiment in FIG. 1A provides online medication instruction to the patient visiting the pharmacy store (own store) by a pharmacist at a location (e.g., another store or a medication instruction center) different from the pharmacy store (own store). As shown in FIG. 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. There is no limitation on the communication network 4, and the Internet, an intranet, a LAN, or any combination of these may be adopted.
[0011] As an example, among the multiple servers 2 (2a to 2d), the server 2a provides a medical receipt computer system (medical accounting system), the server 2b provides an electronic medical history system, the server 2c provides an online medication instruction system, and the server 2d provides a cash register system (e.g., a POS system, etc.). The 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 in the pharmacy store (own store) and terminals 3 in places other than the store (for example, other stores, or optional facilities such as a medication instruction center). The terminals 3 in the store specifically include, for example, a receipt computer terminal 3a at the counter, a patient terminal 3c1, a dispensing room terminal 3 (medication history terminal 3b1, image terminal 3cc1), and a cash register terminal 3d. The terminals 3 in places other than the store include, for example, a pharmacist terminal 3c2 and a medication history terminal 3b2. For example, any hardware terminal in the pharmacy store (own store) or a place other than the store may log in (connect) to each server 2, so that each hardware terminal operates as each terminal 3. In the embodiment, the medication history terminals 3b1 and 3b2 can refer to common medication history data, for example, through a cloud medication history system.
[0013] 1.2.Hardware Configuration Please refer to Fig. 1B. For convenience of explanation, the server 2 and the terminal 3 are collectively referred to as "computers" herein. As shown in Fig. 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 clock 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 given function according to a code or instruction included 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 a function of storing various programs and various data required for the operation of each 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 the storage unit 52 can employ any of 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). The storage unit 52 may also be expressed as a memory.
[0016] Each of the computers 2 and 3 can store a program in the storage unit 52. The control unit 51 realizes various functions of each of the computers 2 and 3 by executing the program.
[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 adopted. The communication unit 53 transmits various data to various devices according to 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.
[0018] The input unit 54 is a device for inputting various operations to each of the computers 2 and 3. The output unit 55 is a device for outputting the results of processing performed by each 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 or combination of all kinds of devices capable of receiving input from a user (such as an operator of each computer) and transmitting information related to the input to the control unit 51. The input unit 54 may be, for example, a touch panel, a touch display, a hardware key 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 include a sound input unit or an imaging unit. The sound input unit is capable of inputting sound data and includes a microphone, etc. The imaging unit is used to obtain 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 or a combination of all kinds of devices capable of outputting 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 or a combination of all kinds of devices capable of displaying 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 facing each other and have 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 has, for example, a clock using 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 the business flow and system processing of the embodiment will be described below with reference to FIG. 2. In FIG. 2, the interaction between each server 2 and each terminal 3 corresponds to the system processing. The interaction between each terminal 3 and a human corresponds 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 through a screen, sound, etc.). In FIG. 2, as an example, the cooperation between the servers 2a and 2b is illustrated simply and diagrammatically with arrows. It should be noted that the present invention is not limited to a specific server cooperation method, and any cooperation can be adopted. Usually, various modes of cooperation technology between servers can be adopted depending on the manufacturer, whether or not it is a cloud, etc., and the cooperation may become complicated. The cooperation between the servers may be constructed as necessary. As another example, one or both of the servers 2a and 2b may be cooperated with the server 2c, and the server 2d may be additionally cooperated.
[0025] 2, those corresponding to system processing (input / output or arithmetic processing) are executed by the control unit 51, so that a program read from the storage unit 52 is executed by the control unit 51, thereby realizing functional units (e.g., a recognition unit, a request unit, a guidance unit, and a counting unit) of each process 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 each of the following steps S1 to S31 can be replaced, integrated or omitted as necessary, and other steps can be inserted between steps. For convenience, the server 2d of the accounting system (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 FIG. 2. A patient who visits a pharmacy presents various information at the pharmacy counter, and the pharmacy clerk performs input operations on the receipt computer terminal 3a accordingly (see S0, 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, the prescription information and personal information of the visiting patient (e.g., address, name, date of birth, insured person number, My Number, etc.) are obtained by the server 2a (receipt computer) (see S2). The server 2a (receipt computer) issues consecutive reception numbers, which are output to the receipt computer terminal 3a (see S3), and the pharmacy clerk obtains 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 performed on behalf of the other party (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, as an 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 he or she wishes to receive online medication instruction, and the answer is acquired.
[0029] For example, when a patient visits a pharmacy and receives medical treatment at a hospital, the prescription corresponding to that medical treatment may state "online support" or "online medication instruction requested." This statement indicates whether or not the patient can receive online medication instruction at home without visiting the pharmacy. In other words, based on this statement, it is possible to determine whether dispensing, instruction, medication, etc. are possible without the original prescription. In contrast, in the embodiment (online medication instruction in store), the normal operation of receiving the original prescription at the store is performed, and online medication instruction is provided to the patient visiting the pharmacy in the store. The online medication instruction in the embodiment is different from the situation assumed by the statement "online support" on the prescription. Unless other regulations (e.g. various rules of each local government) are imposed, the online medication instruction in the embodiment can be provided regardless of the statement "online support" 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 preference, the advantages of online medication instruction (e.g., short waiting time) are explained, and the patient is provided with information for making a decision, thereby improving the convenience of the patient.
[0031] The presence or absence of online medication instruction can be obtained by any staff or any device at any means and place. For example, a pharmacy clerk may verbally confirm with a patient at the counter, or the presence or absence may be obtained by the patient operating a store reception terminal (e.g., tablet) or the like. The presence or absence of online medication instruction is managed by any method in the business flow within the pharmacy store. As an example, as shown in the vicinity of step S0 in FIG. 2, "paper-based management" may be used, and for example, the "presence" of online medication instruction may be clarified by any mark (e.g., sticky note) on any paper document (e.g., prescription, medicine notebook, or any form). Note that in certain cases (e.g., when the prescription drug or the patient's symptoms are not suitable for online medication instruction), "presence" may not be adopted, and online medication instruction may be "not present (cancelled)" at any stage of the business flow. When online medication instruction is "not present," the process proceeds to another business flow (not shown) so that a pharmacist provides face-to-face medication instruction within the pharmacy store. Examples of cases where the answer is "no" include when a 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, the work of the dispensing room in the pharmacy proceeds. Specifically, a pharmacist in the dispensing room acquires and views prescription information and the like on the medical history terminal 3b1, performs an audit (prescription audit), checks the medical history and the like on the server 2b (electronic medical history system, see Fig. 1A), and makes inquiries about any doubts as necessary (see S5 and S6). After dispensing, the pharmacist inputs the dispensing information into the medical history terminal 3b1, which is acquired by the server 2b (see S7 and S8).
[0033] Next, a further audit (dispensed drug audit) is conducted in the dispensing room. The pharmacist acquires dispensing information on the medical history terminal 3b1 (see S9, S10). The pharmacist in the dispensing room conducts the audit (dispensed drug audit), and if there are no problems, inputs the final audit results and audit images into the medical 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 the visiting patient (prescription drugs, drug envelopes, drug instructions, etc.) are prepared. Note that the dispensed drug audit is sometimes referred to as a dispensed drug "inspection," but in the embodiment, these are treated as having the same meaning.
[0034] In the embodiment, the specific operation of the audit in the dispensing room (e.g., the type of terminal and the procedure in the dispensing room) is described as an example, but this is merely an example. Please note that the specific content of the flow in FIG. 2 can be modified as desired depending on the operation of each pharmacy.
[0035] Next, for patients who have online medication instructions "available," in one embodiment, 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 the screen 10 (see FIG. 4A) of the image 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. As a result, the server 2c acquires the patient identification information (identification process S12b), and an instruction to provide online medication instructions to the specific patient is given to the server 2c.
[0036] In the embodiment, as an example, the server 2c is caused to acquire (receive) "image F." 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] 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 bag image", a "receipt image", a "detailed receipt proof image", a "reception number slip image", a "test result image", a "health check result image", a "upper limit management table image", or a "prescription device output information image". One (one type) or more (multiple types) of the images listed here may be used for the image F.
[0038] The above image examples will be explained. An "audit image" is an image of a prescription drug for a patient visiting the pharmacy during a dispensed drug audit (also called a dispensed drug inspection). In the embodiment, the audit image is an image obtained 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 prescription for a patient visiting the pharmacy. A "medication information image" is an image of a drug information sheet for a prescribed drug for a patient visiting the pharmacy. A "medication notebook image" is an image of a medication notebook (whether paper or electronic) for a patient visiting the pharmacy. A "dispensing record image" is an image of a dispensing record related to a patient visiting the pharmacy.
[0039] A "medicine envelope image" is an image of a medicine envelope. The medicine envelope contains information required by law (such as the patient's name, directions for use and dosage, dispensing date, name of the dispensed pharmacist, and name and address of the dispensed pharmacy, hospital, or clinic, etc.) that must be written on the container or packaging of the dispensed medicine. Other precautions (e.g., precautions for storage or use, etc.) may also be written on the medicine envelope. A "receipt image" is an image of a receipt. A receipt is provided as a "distribution of medical expenses" and is divided into, for example, "dispensing technical fee," "pharmacy management fee," "drug fee," etc., with the points and costs for each item written. A "detailed receipt certificate image" is an image of detailed receipt certificate. Detailed receipt certificates are provided as a "distribution of medical expenses in more detail than a receipt," and are provided with, for example, the cost of each prescribed drug.
[0040] The "reception number slip image" is an image of the reception number slip (see FIG. 2, step S4). The "examination result image" is an image of documents or data, etc., showing any examination results (if any) of the visiting patient. The "health check result image" is an image of documents or data, etc., showing the results of the health check of the visiting patient (if any, regardless of whether some or all of them are included). The "upper limit management table image" is an image of the self-payment upper limit management table. The self-payment upper limit management table is used at the counter of the medical institution or pharmacy to check that the self-payment for a specified period (one 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 itself." The "equipment of the store itself" may be any equipment (e.g., dispensing equipment, etc.) in the dispensing room, for example. In the case of dispensing equipment, for example, audit results, etc. are included as output information.
[0041] In addition, although the above examples show images that can be used as image F, some of these images can be used alone, while others are intended to be used in combination. Images intended to be used in combination may be transmitted to server 2c together with images that can be used alone, or necessary information may be transmitted to server 2c as, for example, text data, and the images intended to be used in combination may be transmitted to server 2c.
[0042] A plurality of types of images may be adopted for the image F, and in the embodiment, as an example, an inspection image G, a prescription image H, and a drug information image J are adopted as the image F (see FIG. 4A). Some of the images F include images on which patient identification information (e.g., the patient's name, etc.) is written. It should be noted that the above examples are not the only examples, and other images may be adopted. For example, "any other image capable of presenting the information or items shown by each of the images exemplified above" may be adopted for the image F. For example, some of the images exemplified above can present information on prescription drugs (e.g., appearance, contents, ingredients, quantity, usage, dosage, precautions for taking or storing the medicine, various information on the date and time of dispensing, location, or dispenser, etc.), or information on patients visiting the pharmacy (e.g., name, age, medical examination results, health check results, related information on medical expenses, etc.). In this way, for example, "any image capable of presenting at least one of prescription drug information and patients visiting the pharmacy" may be adopted for the image F. It should be noted that character information may be extracted from the image F by OCR processing. Any image format can be used for the format of image F, and it does not matter whether it is a raster image or a vector image. Of course, PDF data is included as an example of image F. If there is a priority order based on the order in which patients are treated, the priority order may be entered on screen 10.
[0043] 2.2. Description 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 provided in a location (e.g., another store) different from the pharmacy where the visiting patient is. 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 the medication instruction task has a priority order, the display content may be changed to prompt the medication instruction pharmacist to make a selection according to the priority order.
[0044] 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 according to the selection information (S16). The specific contents of the call-related processing can be constructed in various ways, but two examples are provided in the embodiment. In the first example, a call waiting screen and a call screen are provided (e.g., screen 30 and screen 40, see Fig. 5B and Fig. 6A), and a screen transition is made such as call waiting → call execution. In the second example, a screen that integrates a call waiting function and a call function (e.g., screen 60, see Fig. 7) is used.
[0045] 2.3.1. First Example (Screens 30 and 40) To explain the first example, in the embodiment, as an example, the server 2c displays the screen 30 (see FIG. 5B) for the selected medication instruction task on the pharmacist terminal 3c2 according to the selection information (S16), and puts the terminal 3c2 in a call standby state (see S17). At this point, the acceptance has not yet been decided, and the task can be canceled by pressing the "Back" button on the screen 30. The medication instruction pharmacist checks the memo and the image F (e.g., audit image G, prescription image H, medication information image J, etc., and also medication notebook images and dispensing record images can be adopted) on the screen 30 (see S18a). The medication history is also checked, but the medication instruction pharmacist may check it by accessing the server 2b (electronic medication history system) himself (see S18b), or as a modified example, the servers 2b and 2c may be linked to display the medication history on the screen 30. After that, if the medication instruction can be started, a connection operation is performed with the intention of accepting the task (see S19). The connection operation in the embodiment is an operation of clicking the "Patient Call / Start Call" button on the screen 30 in Fig. 5B. In response to the connection operation, the pharmacist terminal 3c2 transmits a connection instruction (or any connection information such as access information) (see S20).
[0046] In the embodiment, as an example, when the 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, the server 2c sends the medication instruction notification and patient identification information (e.g., reception number) to the receipt computer terminal 3a. A specific example of the notification method will be described in the section "3.2. Example of notification function" below. In the embodiment, as an example, the pharmacy clerk calls the visiting patient with a specific reception number according to the medication instruction notification, guides the patient to the location of the patient terminal 3c1 (e.g., an arbitrary desk in an open space near the counter, a booth with a partition, or a private room), and the pharmacy clerk (or the visiting patient) performs a "call start operation" on the patient terminal 3c1 (see S22). The call start operation is, for example, pressing a call start button displayed on the screen of the patient terminal 3c1 (e.g., the "patient call / call start" button on the screen 30). As a result, the pharmacist terminal 3c2 confirms the task acceptance. A plurality of patient terminals 3c1 may be installed in the same pharmacy. In this case, the medication instruction notice includes terminal designation information (indication of which patient terminal 3c1 the notice should be sent to).
[0047] Next, in the embodiment, as an example, the server 2c executes a call process (see S23a, S23b). In this process, the server 2c connects the pharmacist terminal 3c2 that has accepted the medication instruction task and the patient terminal 3c1 so that they can communicate with each other. During the connection, a screen 40 (call screen: see FIG. 6A) is displayed on the pharmacist terminal 3c2, and a screen 42 (call screen: see FIG. 6B) is displayed on the patient terminal 3c1.
[0048] 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).
[0049] 2.3.2. Second example (Screen 60) In the embodiment, various arbitrary screens and processes can be adopted without being limited to the above-mentioned first example. In the second example, a screen 60 (see FIG. 7) is used instead of the above-mentioned 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 the screen 60 is maintained.
[0050] To explain the second example, in the embodiment, as an example, 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 the embodiment, as an example, the screen 60 is in a call waiting state in the initial state (corresponding to S17). The screen 60 is provided with each of the functions of the screens 30 and 40. In the second example, the screen 60 can execute processes and tasks corresponding to each of steps S17, S18a, S19, and S20 in the first example.
[0051] Here, in the second example, when the "Patient Call / Start Call" button (button 61) is clicked on the screen 60 in 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) goes into a call waiting state. At this time, the following processes (x2-1) and (x2-2) are executed. (x2-1) The selfie camera starts up and waits for a call to begin. (x2-2) The "patient call / start call" button (button 61) changes to an "end call" button. In other words, button 61 is an "operation button for starting / ending a call." (x3) The patient terminal 3c1 starts a call, which means that the call is started (corresponding to steps S23a and S23b). The medication instruction pharmacist can provide online medication instruction through the 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).
[0052] In this second example, the medication instruction pharmacist can also 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).
[0053] 2.3.3. Call End After the process illustrated in the first or second example above, when the medication instruction via online call is 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.
[0054] 2.4. Steps S27 to S31 (Processing after Medication Instructions) Thereafter, in an embodiment, as an example, the server 2c displays guidance information (e.g., accounting guidance, accounting information, voucher number, etc.) on the patient terminal 3c1 (see S27). The voucher number may be printed from a ticket issuing machine connected to the patient terminal 3c1. Upon receiving the guidance information, the visiting patient moves to the counter or the like in accordance with the information (see S28). A notification may be sent to the medical receipt computer terminal 3a together with or instead of the patient terminal 3c1.
[0055] In response to the end of the call processing (disconnection S26), the server 2c transmits a "medication instruction completion notice" to the receipt computer terminal 3a (see S29) at the same time as or before or after displaying the guidance information (S27, S28). After that, the pharmacy clerk prepares for the payment (see S30), and the visiting patient completes the payment and receives the prescribed medicine (see S31).
[0056] 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 to the operation of a pharmacy store, making it possible to effectively utilize human resources outside the store (pharmacists at other stores), and improving the business response capabilities of the pharmacy store. By dealing face-to-face at a pharmacy store, various advantages (e.g., peace of mind in face-to-face administrative procedures and medication instruction, ability to receive and manage the original prescription, ability to directly hand over the prescribed medicine, etc.) can be obtained. Such various advantages of dealing with a pharmacy store and improved business response capabilities can be achieved at the same time. Conventionally, in cases where medication instruction was handled by a pharmacist from the headquarters or another store spending time and money to go to support during congestion, etc., but according to the embodiment, there is an advantage in that such time and costs can be saved by effectively introducing online medication instruction. Preferably, the information processing system of the embodiment is introduced without making any major changes to store operations (more preferably, without any changes to basic store operations).
[0057] In the embodiment, as an example, in the request process S13 or the call process S23a, the pharmacist terminal 3c2 displays an inspection image G or the like as an example of the image F (see Figs. 4A, 5A to 6A, and 7). This improves convenience when confirming a request or making a call.
[0058] 3. Examples of terminal functions, etc. 3.1. Examples of login and screen transitions Please refer to Fig. 3. In the embodiment, as an example, the server 2c provides an online medication instruction service in the form of a Web application. As an example, each terminal 3 in the pharmacy store logs in with a store account that has been registered in advance. When the dispensing room mode is selected on the subsequent mode selection screen, the functions of the image terminal 3cc1 (e.g., display of screen 10, etc.) are provided, and when the counter mode is selected, the functions of the patient terminal 3c1 (e.g., display of screen 42, etc.) are provided.
[0059] Each terminal 3 outside the store (e.g., other pharmacy stores, etc.) logs in with a preregistered and set pharmacist account. This provides the functions of the pharmacist terminal 3c2 (e.g., display of screens 20, 30, 40, notification 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 displayed in a list, and related information may be displayed.
[0060] 3.2. Example of notification function In FIG. 3, "notification" is shown, which means the notification function of the terminal 3. In the 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, or the like. Specifically, the pharmacist terminal 3c2 may be able to access the OS settings, message or alarm setting function, and the like in each terminal 3 in the pharmacy store. The notification function may be set by using any communication function between the terminals 3, or may be provided through a web application of the server 2c.
[0061] Specifically, in the embodiment, at least the following three patterns are adopted as examples of using the notification function by the pharmacist terminal 3c2. Each pattern includes a notification (for example, sounding a notification sound or displaying a message). · First pattern: Patient call · Start of call · Pattern 2: Calling a pharmacist (e.g., contacting a pharmacist regarding a medical problem) · Third pattern: Accounting contact
[0062] The first pattern of notification is performed, for example, when a "Patient Call / 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.
[0063] In the second and third pattern notifications, as an example, a message is displayed together with a notification sound, and the timing of display is, for example, when the "Call pharmacist" or "Notice of accounting" button is pressed on screen 30 (see FIG. 5B) described later. Note that the third pattern notification (notice of accounting) after the medication instruction completion operation (S25) corresponds to the medication instruction completion notification (S29).
[0064] In the first and third patterns, as an example, the notification function is activated on an arbitrary clerk terminal (e.g., the receipt computer terminal 3a) at the reception desk, etc. In some cases, any other terminal (e.g., an electronic medical history terminal) at an adjacent counter may be used. In the second pattern of calling a store pharmacist (e.g., when a question is raised, etc.), as an example, the notification function may be activated on an arbitrary terminal in the dispensing room (e.g., the medical history terminal 3b1 or the image terminal 3cc1).
[0065] In the embodiment, it is possible to set which notification is to be made at each terminal 3 in order to correspond to the above first to third patterns. For example, notification conditions may be set so that an arbitrary terminal at the counter (e.g., the receipt computer terminal 3a, etc.) can receive notifications of the first and third patterns, and an arbitrary terminal in the dispensing room (e.g., the medical history terminal 3b1 or the image terminal 3cc1) can receive notifications of the second pattern. When receiving multiple different notifications (e.g., the first and third patterns) at the same terminal 3, it is preferable to differentiate the notification contents (e.g., alarm sounds, etc.), so that the notification contents (e.g., alarm sounds, etc.) can also be set to multiple different contents. In addition, the alarm sound may be selectable between loop playback and non-loop playback.
[0066] 3.3. Example of image terminal screen FIG. 4A shows an example of a screen 10 displayed on the image terminal 3cc1. The screen 10 is an example of an image transmission screen for transmitting an image F. A pharmacist in a dispensing room inputs patient identification information (e.g., reception number) via the screen 10, clicks the "take image (photograph)" button, attaches an image F, writes a memo 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 designation function, and when the checkbox is checked and the send button is pressed, the priority is reflected in the transmitted information. It is preferable that the image F is clear enough to allow accurate visual recognition of information on the object being photographed (e.g., shape, color, pattern, letters, numbers, symbols, etc.). For example, it is preferable that an inspection image G is actually photographed in a state where prescription drugs are arranged on a tray or the like in an easy-to-see manner.
[0067] FIG. 4B shows examples of screens 11 to 13 used for status confirmation in the embodiment. The image terminal 3cc1 can display screen 11 (status confirmation screen), and when the "taken image list" button is pressed, the screen transitions to screen 12 (image list screen). On screen 12, images F that have already been sent (e.g., audit image G, etc.) are displayed in a list. A filtering function such as a sending date (e.g., the current day) can also be used. In cases where an online medication instruction was initially planned but it is desired to change to face-to-face medication instruction, the corresponding medication instruction task may be canceled by specifying a desired image F and pressing a cancel button. Status buttons ST are also provided on screen 12. 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 check box that switches on and off each time it is clicked may be used. For example, when the "search" button is clicked with all buttons (all four) of the status buttons ST turned on, images of all statuses are displayed. For example, if you search with everything except "Received" turned off, it is possible to narrow down the display to only images whose status is "Received." For example, if you turn on the "Pharmacist Confirmed" button and click the "Search" button, it is possible to narrow down the display to "Images F already opened on a pharmacist terminal" (i.e., audit images that have been confirmed by a pharmacist, etc.). By pressing the "Message" button, screen 13 (message window) opens and it is possible 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 terminal screen 3.4.1. Request Reception Screen The screen 20 in FIG. 5A is displayed on the pharmacist terminal 3c2 by the request process (S13 in FIG. 2). The screen 20 is a request receiving screen, and is a screen for receiving a request for a medication instruction task. The screen layout of the screen 20 displays each medication instruction task in tiles as an example. In the embodiment, as an example, the medication instruction tasks 21 and 22 are presented together with an image F. Specifically, in the embodiment, as an example, as shown in FIG. 5B, the medication instruction tasks 21 and 22 are presented together with an audit image G, etc. (for example, a thumbnail display of the whole image). In the example of FIG. 5A, the medication instruction task 21 corresponding to reception number 55 (for example, an audit image G1, etc. is attached as image F) and the medication instruction task 22 corresponding to another reception number 56 (for example, an audit image G2, etc. is attached as image F) are illustrated. The status button ST described in FIG. 4B is also provided on the screen 20. When a desired medication instruction task (eg, medication instruction task 21) is selected (clicked), the screen transitions to screen 30 in FIG. 5B.
[0069] As an example, various display switching menus may be provided on the screen 20, etc., which may enable the medication instruction tasks to be narrowed down and displayed or sorted. The display switching menu may include, for example, one or more of the following menus (M1) to (M5), or may be a combination of these. (M1) Display by requesting pharmacy or by rank (M2) Ranking by request time (M3) Display order by reception number (M4) Display by priority (e.g. "urgent", "later", "standard", etc.) (M5) Filter and display only requests that are specified for you
[0070] 3.4.2. First Example of Call-Related Screen Q The dashed line Q in FIG. 3 indicates a call-related screen related to the call function, specifically including screens 30 and 40. Screen 30 in FIG. 5B is an example of a call waiting screen. As an example, the medication instruction task 21 (reception number: 55) is selected. In the window selection menu, "window 1" is selected as an example, which means that the patient terminal 3c1 installed at window 1 is specified as the call connection destination. In FIG. 5B, the audit image G1 is displayed as an example of image F (in this example, the second of three images is displayed), and next to it is a memo field, and the status display (cancelled, held, completed) of this medication instruction task is also displayed. "Hold" is a waiting for contact to resume remotely, not at the store, after being interrupted due to a question inquiry, etc. The "pharmacist call" button can send a message and a notification to the image terminal 3cc1, and the "accounting contact" button can send a message and a notification to the receipt computer terminal 3a. The pharmacist call can be used, for example, for a question inquiry. When the "Patient Call / Start Call" button is pressed, a message is sent to the patient terminal 3c1 and a medication instruction notification (see S21 in Fig. 2) is issued. At the same time, a notification is also sent to any terminal used by a clerical staff member, etc. (e.g., medical receipt terminal 3a). When the patient terminal 3c1 responds (connection is started), the screen transitions to screen 40 in Fig. 6A.
[0071] The screen 40 in Fig. 6A is an example of a call screen of the pharmacist terminal 3c2. The screen 40 includes a patient call button, an image sharing screen for an audit image, etc., a call end button, and a call start and end time and user record. Buttons for turning on a background control function (e.g., background blur function) or audio subtitles, etc. may also be provided.
[0072] In the embodiment, as an example, the above-mentioned image F may be displayed on a call waiting screen (e.g., screen 30) or a call screen (e.g., screen 40). In Fig. 5B and Fig. 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 Fig. 5B and Fig. 6A).
[0073] The screen 40 in FIG. 6A is a call screen of the pharmacist terminal 3c2 connected by the call process (S23a). As an example, the pharmacist terminal 3c2 that selected the medication instruction task 21 (reception number: 55) is connected to the patient terminal 3c1 linked to the corresponding patient identification information (e.g., reception number 55) so that they can make a call. The main display area 40a displays the visiting patient (reception number: 55) captured by the camera of the 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 the screen 40.
[0074] 3.4.2. Second Example of Call-Related Screen Q The call-related screen Q may be integrated into one screen 60 (see FIG. 7). The screen 60 is a screen that can be used for both call waiting and calling. As with the screen 30, the screen 60 provides, for example, a "Back" button (cancel function), a memo entry field, an "Image confirmation" function (e.g., any image F such as an audit image G, a prescription image H, or a drug information image J can be confirmed), a "Pharmacist call" function (question inquiry function), a "Patient call / start call" function, an "Accounting contact" function, and a medication instruction status function. As with the screen 40 (see FIG. 6A), the screen 60 provides a main display area 40a, a sub-display area 40b, and an "Image sharing" function.
[0075] The screen 60 further provides a thumbnail area 62, an enlarged display area 63, and an annotation function 63a (e.g., selecting a writing pen, writing and erasing) as image confirmation functions. When an arbitrary thumbnail image is selected from the thumbnail area 62 (in FIG. 7, the audit image G1 is selected as an example), the selected image is enlarged and displayed in the enlarged display area 63 on the right side of the screen 60. When the "Image Share" button is then clicked, the image is shared on the patient terminal 3c1. The annotation function 63a can be, for example, a button-like radio button, and arbitrary drawing (e.g., figure drawing, pen drawing, character input, etc.) is possible on the image in the enlarged display area 63. The image with the drawing combined is also shared on the patient terminal 3c1. When the "Call Screen Enlargement" button is clicked even during image sharing, the patient's face shown on the patient terminal 3c1 is enlarged and displayed in the enlarged display area 63. Generally, the patient's face is enlarged at the time of the first greeting, and after that, the audit image, etc. can be shared to provide medication instruction.
[0076] 3.5. Example of patient device screen Screen 42 in FIG. 6B is an example of a screen of patient terminal 3c1 (e.g., window 1) connected by call processing (S23b). A medication instruction pharmacist captured by the camera of pharmacist terminal 3c2 is displayed in main display area 42a. A self-image (visiting patient) captured by the self-camera is displayed in sub-display area 42b.
[0077] 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 showing the face of the pharmacist may be additionally displayed. As the shared image, any one of the images F can be shared.
[0078] 4. Variations in Request Processing In an embodiment, as an example, multiple pharmacist terminals 3c2 may be installed at "different locations" or at the "same location." The "different locations" may be other pharmacy stores (which may be chain stores, etc.), or may be any location not limited to pharmacy stores. The number of locations where the pharmacist terminals 3c2 are installed may be any number of two or more, and may be comprehensively installed in, for example, multiple chain stores. The "same location" is, for example, within the same building. As for the "same location," as an example, a "medication instruction center" may be set up and multiple pharmacists may provide online medication instructions within this center.
[0079] 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 not, or allocating, etc.). The individual specific situation may be, for example, "the current situation, state, environment, attributes, geography, time, designation (agreement), evaluation, history, etc.," regarding the "prescription, pharmacist, location of the terminal (store, etc.), or visiting patient, 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.
[0080] (B1) Examples of the help history include the store to which each pharmacist (using the pharmacist terminal 3c2) belongs, or the help history of other stores. For example, past help history (e.g., the number of times or cumulative time of help shifts at other stores), whether the store is nearby (e.g., the closer the distance, the higher the priority, or within a specified distance, etc.), or whether the store is a pharmacy in front of 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 designation. For example, the input items of the image 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 under predetermined arbitrary conditions (e.g., shift setting or schedule setting between multiple stores with different workloads). This shift setting, etc., can be said to be an online version of help work at a real store. Bulk requests can also be adopted.
[0081] (C1) The contents of a prescription for a patient visiting a pharmacy are considered as an example. For example, the ease of requesting a prescription may be determined according to the prescription contents. For example, 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 patient in the acute phase of a single episode of a common cold, etc.) in order to increase the turnover rate. Prescription information, etc. may be shared between the servers 2a and 2c. (C2) Information, symptoms, or medical history of a visiting patient may be considered as an example. As in (C1) above, a process may be adopted to automatically pick up individual patients, symptoms, or medical history that are easy to request from other stores. The servers 2a, 2b, and 2c may share visiting patient information, etc.
[0082] (D1) The situation or external environment of the installation location where each pharmacist terminal 3c2 is installed is considered. The installation location may be each pharmacy store other than the own store, or a medication instruction center. The external environment or store situation of each pharmacy store (where each pharmacist terminal 3c2 is installed) is considered as an example. The external environment may be, for example, weather information or traffic congestion status of each store area or medication instruction center area obtained from the Internet. For example, there is a tendency that the number of visitors is higher 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 vacancy status, or any situation (e.g., temporary closure, etc.) in each store or medication instruction center. Based on these, each medication instruction task may be allocated to avoid, for example, load concentration. 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 that stores in an emergency (e.g., stores in the area where the emergency occurred or nearby) are avoided and normal stores (e.g., stores relatively far from the area where the emergency occurred) are given priority. (D2) The workload, activity, or evaluation of each pharmacist is an example. 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 be used.
[0083] Two or more of the above (B1) to (D2) can be combined with each other. For example, the data management unit 2c1 of the server 2c may store and manage each of the above (B1) to (D2), and the medication instruction task may be allocated based on the stored data of the data management unit 2c1. Depending on the individual specific situation (e.g., the above (B1) to (D2)), for example, when a suitable candidate for request is not found (or the task cannot be currently requested), or when a process for determining whether online medication instruction is appropriate / inappropriate is performed and the result is inappropriate, the fact may be notified to any terminal (e.g., the receipt computer terminal 3a or the image terminal 3cc1, etc.).
[0084] 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, a task request may be made to one pharmacist terminal 3c2 depending on an individual specific situation.
[0085] 5. Counting process In the embodiment, as an example, the server 2c may further execute a counting process. The counting process can be executed 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 by data communication.
[0086] In the embodiment, as an example of the tallying process, the allocation status of medication instruction tasks 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 nominated, and may include two or more of these. After the task is nominated, the acceptance and refusal 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, collectively or by store. Evaluations of each pharmacist may be recorded based on the task allocation status. The tallying process can be executed, for example, by the data management unit 2c1 in the server 2c, but is not limited thereto, and may be executed, for example, by any database system (not shown) outside the server 2c.
[0087] 6. Modifications, etc. 6.1. Changes in business flow, etc. Various modifications can be made to the business flow and system processing in Fig. 2. For example, in the embodiment, in the identification process S12b, the server 2c acquires 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 this is not limiting. For example, as a variation of the identification process, the identification process may be realized by "any subject" inputting patient identification information (e.g., reception number) from "any terminal" to the server 2c at "any timing".
[0088] For example, computer management may be adopted in step S0. As computer management, for example, when a visiting patient desires 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 an operation of a terminal (e.g., receipt computer terminal 3a) by a pharmacy clerk or the like. Alternatively, when a visiting patient desires online medication instruction, presses a confirmation button on a storefront 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).
[0089] For example, the server 2c may obtain "information indicating that online medication instruction is available for the visiting patient." The server 2c may store this "information" in a table or the like, and when online medication instruction is "available," may execute a request process S13 or the like, or send any notification to the medical receipt computer terminal 3a, image terminal 3cc1, or the like. For example, the "desire" for online medication instruction for each visiting patient (e.g., for each reception number) may be recorded and managed in a predetermined column of the table (can also be used for managing cancellations, etc.). Data management may be performed by the server 2c in cooperation with another server 2 (e.g., server 2a or server 2b).
[0090] In the embodiment, after the request process (S13), some system processes or business procedures (S15 to S22) are performed, and then the connection process (S23a, S23b) is executed. However, this is only an example, and the processes between the request process and the connection process can be changed arbitrarily. For example, the response confirmation operation (S22) may be omitted, and in this case, the pharmacist terminal 3c2 may first enter a call connection state and wait for the patient terminal 3c1 to take a seat. As another example, each process related to call waiting (S17, etc.) may be omitted, and in this case, for example, the call process may be executed immediately in response to the task selection operation (S15), or, for example, a confirmation message display (e.g., "Do you want to connect?" or a countdown display (call connection after the countdown ends) may be adopted. In these cases, the screen layout of the screen 20 (request reception screen) may be designed so that the details of each medication instruction task can be confirmed, or detailed information can be confirmed by any operation of the screen 20 (e.g., detailed information pops up when the cursor is placed over it).
[0091] In addition, steps S22 and S30 shown in the dashed frame Z in Fig. 2 are exemplified by the receipt computer terminal 3a as an example of hardware, but are not limited to this. At least one of the processes of steps S22 and S30 may be performed by a terminal other than the receipt computer terminal 3a.
[0092] 6.2. Cancellation and history management of medication instruction tasks The server 2c may be able to switch the online medication instruction from "Yes" to "No" at the time (during) or after the request processing S13. Each terminal 3 (e.g., the receipt computer terminal 3a, the image terminal 3cc1, the patient terminal 3c1, the pharmacist terminal 3c2, etc.) may be able to switch. The history of the switching may be saved.
[0093] 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 an arbitrary terminal 3 the implementation history of online medication instruction, or a recommendation notification (regardless of image or sound, etc.) based on the history.
[0094] 6.3. Priority Designation Function The priority specification function (e.g., a "visit later" checkbox, etc.) may be displayed not only on the image terminal 3cc1 but also on any screen of some terminals 3 (e.g., 3a, 3c2). For example, a priority specification menu, etc. may be provided, and multiple types of priorities (e.g., "urgent (or emergency)", "later", "standard", or time specification (e.g., 11:00), etc.) may be set. For example, an example of using "later" is when a patient visits the pharmacy after checking in and going out for a while before returning.
[0095] 6.4. Image F Capture Device It is preferable that the image F is an easy-to-view, clear image of the object to be imaged (e.g., 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 (e.g., a smartphone or tablet terminal), a fixing device for the terminal (e.g., a bendable arm), and a placement section (e.g., a tray, etc.) on which the object to be imaged (e.g., prescription drugs, etc.) is placed may be prepared. The imaging terminal can transmit the image F to the imaging terminal 3cc1, for example, by wireless communication. Note that if the imaging terminal 3cc1 is a terminal with a camera, it may also function as the imaging terminal.
[0096] In addition, the inspection image may be captured by "an inspection device installed in a dispensing room." There are various types of known inspection devices, and they may be, for example, a stand-alone device, or may be, for example, a terminal of a dispensing inspection system (also called a dispensing inspection support system, a drug inspection support system, an inspection support system, a dispensing weighing inspection system, a medical drug prescription inspection system, etc.). The image terminal 3cc1 may receive the inspection image data from the inspection device and transmit it to the server 2c.
[0097] 6.5. Variations of each terminal 3 The patient terminal 3c1 may be realized by a terminal (e.g., a smartphone) of a visiting patient. The visiting patient may access the server 2c on his / her own terminal via a browser or by installing an app, and may use his / her own terminal as the patient terminal 3c1 to receive online medication instructions in the pharmacy. Patient accounts may be managed by the server 2c.
[0098] 6.6.Other In the embodiment, each server 2 may adopt 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 a request from a client (each terminal 3). Each server 2 is not limited to a physical server (e.g., on-premise or data center use), but may be a virtual server, a container, or a "dynamically allocated computing resource using a serverless architecture". Each server 2 may be built on an infrastructure such as AWS (Amazon Web Services). Each server 2 may be a web application (e.g., see FIG. 3) built on a 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). Some of the multiple servers 2 may be physical servers, and the others may be virtual servers.
[0099] Although the present invention has been described above based on the embodiments, the present invention is not limited to the configurations of the above-mentioned embodiments. 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, and various communication terminals and mobile information terminals such as mobile terminals and tablets. The computer program may be implemented in various computers and various communication terminals and mobile information terminals.
[0100] In the embodiment, 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 it is optional whether the server is the executing entity of each process (or whether it is server-side processing). For example, a part or all of each process of the embodiment may be executed by a client (e.g., terminal 3) (in the case of all processes, it is possible to omit the server by only communicating between terminals 3). In addition, each feature of the above embodiment and modified example can independently constitute an invention, and can also be appropriately combined. It should be noted that the scope of various modifications, applications, and uses made by a person skilled in the art as necessary is also included in the gist (technical scope) of the present invention.
[0101] 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.
[0102] [Appendix 1] An information processing system for providing online medication instructions 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, patient identification information of a patient who visits the pharmacy store is acquired, In the request process, a medication instruction task corresponding to the patient identification information is presented on the pharmacist terminal; In the communication process, the information processing system connects the pharmacist terminal that has been entrusted with the medication instruction task and the patient terminal so that they can communicate with each other.
[0103] [Appendix 2] 2. An information processing system according to claim 1, causing said server to obtain at least one image; An information processing system, wherein the at least one image is an image to be displayed on the pharmacist terminal during the request processing or the call processing.
[0104] [Appendix 3] 3. An information processing system according to claim 2, An information processing system, wherein the at least one image includes one or more images selected from the group consisting of an audit image, a prescription image, a medication information image, a medication notebook image, a dispensing record image, a medicine bag image, a receipt image, a detailed receipt proof image, a reception number image, a test result image, a health check result image, an upper limit management table image, and an equipment output information image.
[0105] [Appendix 4] An information processing system according to claim 2 or 3, An information processing system, wherein the 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 instructions in the call processing.
[0106] [Appendix 5] An information processing system according to any one of Supplementary Note 2 to Supplementary Note 4, In the request process, the medication instruction task is presented together with the at least one image.
[0107] [Appendix 6] An information processing system according to any one of Supplementary Note 2 to Supplementary Note 5, In the call processing, the at least one image is displayed on a call screen of the pharmacist terminal.
[0108] [Appendix 7] An information processing system according to any one of claims 1 to 6, The server further executes a counting process; In the tallying process, the information processing system tallys up the allocation status of the medication instruction task for the pharmacist using the pharmacist terminal.
[0109] [Appendix 8] An information processing system according to any one of claims 1 to 7, In the identification process, Acquire information indicating that the patient visiting the pharmacy has online medication instruction, The request process includes: An information processing system which is carried out when the online medication instruction is provided.
[0110] [Appendix 9] An information processing system according to any one of claims 1 to 8, The server is configured to be able to switch to no online medication instruction during or after the request processing.
[0111] [Appendix 10] An information processing system according to any one of claims 1 to 9, 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 the following (B1) or (B2): (B1) Help history of each pharmacist using each pharmacist terminal at their own store or other stores (B2) A request to designate a pharmacist or store, or a bulk request without designation
[0112] [Appendix 11] An information processing system according to any one of claims 1 to 10, In the request process, the medication instruction task is presented to the pharmacist terminal in accordance with the following (C1) or (C2): (C1) The contents of the prescription of the patient visiting the pharmacy (C2) Information, symptoms, or medical history of the patient visiting the pharmacy
[0113] [Appendix 12] An information processing system according to any one of claims 1 to 11, 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 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
[0114] [Appendix 13] A program for causing a computer to execute each process of the information processing system according to any one of Supplementary Note 1 to Supplementary Note 12.
[0115] [Appendix 14] An information processing method, comprising executing each process of the information processing system according to any one of claims 1 to 12 on a computer. [Explanation of symbols]
[0116] 1: Information processing system 2: Server, 2a: Server (receiver system), 2b: Server (electronic medical history system), 2c: Server (online medication instruction system), 2c1: Data management department, 2d: Server (cash register system) 3: Terminal, 3a: Terminal (receipt computer 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: Screen, 20: Screen (Request reception screen), 30: Screen (Call waiting screen), 40: Screen (Call screen), 42: Screen (Call screen), 60: Screen (Call waiting 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 F: image (at least one image), G, G1, G2: audit image, H: prescription image, J: drug information image, S12b: identification process, S13: request process, S23a, S23b: call process
Claims
1. An information processing system for providing online medication instructions 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, patient identification information of a patient who visits the pharmacy store is acquired, In the request process, a medication instruction task corresponding to the patient identification information is presented on the pharmacist terminal; In the communication process, the information processing system connects the pharmacist terminal, at which the presented medication instruction task has been selected, and the patient terminal so that they can communicate with each other.
2. 2. The information processing system according to claim 1, causing said server to acquire at least one image; An information processing system, wherein the at least one image is an image to be displayed on the pharmacist terminal during the request processing or the call processing.
3. 3. The information processing system according to claim 2, An information processing system, wherein the at least one image includes one or more images selected from the group consisting of an audit image, a prescription image, a drug information image, a medicine notebook image, a dispensing record image, a medicine bag image, a receipt image, a detailed receipt proof image, a reception number ticket image, a test result image, a health check result image, an upper limit management table image, and an equipment output information image.
4. 3. The information processing system according to claim 2, An information processing system, wherein the 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 instructions in the call processing.
5. 3. The information processing system according to claim 2, In the request process, the medication instruction task is presented together with the at least one image.
6. 3. The information processing system according to claim 2, In the call processing, the at least one image is displayed on a call screen of the pharmacist terminal.
7. 2. The information processing system according to claim 1, The server further executes a counting process; In the tallying process, the information processing system tallys up the allocation status of the medication instruction task for the pharmacist using the pharmacist terminal.
8. 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 instruction, The request process includes: An information processing system which is carried out when the online medication instruction is provided.
9. 2. The information processing system according to claim 1, The server is configured to be able to switch to no online medication instruction during or after the request processing.
10. 2. The information processing system according to claim 1, 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 his / her own store or at other stores (B2) A request to designate a pharmacist or store, or a bulk request without designation
11. 2. The information processing system according to claim 1, In the request process, the medication instruction task is presented to the pharmacist terminal in accordance with (C1) or (C2) below. (C1) The contents of the prescription of the patient (C2) Information, symptoms, or medical history of the patient visiting the pharmacy
12. 2. The information processing system according to claim 1, 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 location where each pharmacist terminal is installed (D2) The workload, activity or evaluation of each pharmacist using each pharmacist terminal
13. A program for causing a computer to execute each process of the information processing system according to any one of claims 1 to 12.
14. 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 12.
Citation Information
Patent Citations
Server for supporting remote medical care and medication guidance
JP2021140619A
Server for supporting remote medical care and medication guidance
JP2021140735A
Medical care support device, medical care support method, and program
JP2023011214A
Medicine delivery support system, medicine delivery support method, server device, and prescription acceptance device
JP2024004012A
Medication instruction support device, medication instruction support method, and medication instruction support program
JP7323664B1
Cited By
Information processing system, program, and information processing method
JP7752456B1