Pharmacy business support system

Abstract

To provide a pharmacy business support system that can, for a pharmacy group, streamline personnel deployment across the entire group and is cost-effective.SOLUTION: A pharmacy business support system 1 includes request content sending means by which a requesting terminal 2a sends a server 3 request contents including requesting store identification information that identifies a requesting store and requested store identification information that identifies a requested store, notification information sending means by which the server 3 or the requesting terminal 2a sends notification information indicating that a request has been made from the requesting store to a requested terminal 2b or an apparatus installed in the requested store, remote connection information sending means by which the server 3 sends the requested terminal 2b remote connection information for connecting to the requesting terminal 2a remotely, and remote connection means by which the requested terminal 2b remotely connects to the requesting terminal 2a based on the remote connection information received from the server 3.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to a pharmacy business support system that supports temporary support work for pharmacy business between stores of the same pharmacy group. [Background technology]

[0002] A pharmacy group is a business entity that operates multiple dispensing pharmacies, and is also called a pharmacy chain. Many pharmacy groups have introduced computer systems that support the input of prescriptions, dispensing, and medication instruction to patients, etc., to improve the efficiency of their operations. For example, Patent Document 1 discloses a medication instruction support system that supports medication instruction work.

[0003] Incidentally, one of the issues facing pharmacy groups in recent years is the management of personnel allocation. In the course of daily operations, some stores may temporarily become extremely short-staffed due to sudden vacancies or overcrowding, while other stores may have excess personnel during the same time period on the same day. Therefore, pharmacy groups are looking for a system that allows temporary support between stores. For example, Patent Document 2 discloses a system in which medical staff at a remote center collectively performs some of the work of internal staff at a hospital or other facility as a service provided to small hospitals and clinics. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 7019227 [Patent Document 2] Patent Publication No. 2022-170215 Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the system described in Patent Document 2, the remote center performs all operations on behalf of the other stores, so when it is introduced to a pharmacy group, it is not possible to utilize spare staff at other stores, resulting in inefficient personnel allocation for the entire pharmacy group. In addition, whether the medical staff at the remote center are internal or external personnel, new personnel costs will increase, making it difficult to utilize spare staff at other stores, and it cannot be said to be cost-effective.

[0006] The present invention has been made in consideration of the above-mentioned problems, and its purpose is to provide a pharmacy business support system that enables a pharmacy group to efficiently allocate personnel across the entire group, and is highly cost-effective. [Means for solving the problem]

[0007] In order to achieve the above-mentioned object, the present invention provides a pharmacy business support system in which a requesting terminal installed in a store that requests pharmacy business, a request receiving terminal installed in a store that receives the pharmacy business, and a server are connected via a network, the pharmacy business support system comprising: a request content sending means for the requesting terminal to send request content including requesting store identification information for identifying the requesting store and request receiving store identification information for identifying the request receiving store to the server; a notification information sending means for the server or the requesting terminal to send notification information indicating that a request has been made from the requesting store to the request receiving terminal or a device installed in the request receiving store; a remote connection information sending means for the server to send remote connection information to the request receiving terminal for remotely connecting to the requesting terminal; and a remote connection means for the request receiving terminal to remotely connect to the requesting terminal based on the remote connection information received from the server. According to the present invention, the staff of a store with surplus staff can support the pharmacy business on a computer system of a store that is temporarily short of staff, thereby making it possible to efficiently allocate personnel across the entire pharmacy group, and the cost-effectiveness of introducing the system is high.

[0008] The present invention further includes an account information storage means for storing account information including login information for an account to log in to the pharmacy business support system, a store remote connection information storage means for storing store remote connection information including the remote connection information for each store, a remote connection request transmission means for receiving the login information and transmitting a remote connection request including the login information and the request source store identification information to the server, and a login information authentication means for authenticating the login information received from the request destination terminal based on the account information when the server receives the remote connection request from the request destination terminal, and the remote connection information transmission means may transmit the remote connection information related to the request source store identification information to the request destination terminal when authentication of the login information by the login information authentication means is successful, and the remote connection means may start the remote connection without displaying the remote connection information received from the server. This enables remote connection to other stores while keeping the remote connection information secret from the user. Therefore, the pharmacy business support system of the present invention can be introduced without lowering the security level even when using the remote connection function provided by the OS, so there is no need to build a special remote connection function, and the cost-effectiveness of introducing the system is high.

[0009] The present invention further comprises an account authority information storage means for storing account authority information indicating the stores for which the account has authority to make a remote connection, and an account authority confirmation means for, when the server receives the remote connection request from the request destination terminal, confirming based on the account authority information whether the account related to the login information received from the request destination terminal has authority to make a remote connection to the store related to the request source store identification information, and the remote connection information transmission means may transmit the remote connection information to the request destination terminal when the login information authentication means has successfully authenticated the login information and the account authority confirmation means has confirmed the authority of the account. This makes it possible to limit the stores that can be remotely connected according to the position of the personnel, thereby making it possible to efficiently allocate personnel throughout the pharmacy group and making the introduction of the system cost-effective.

[0010] In addition, the pharmacy work in the present invention may be a prescription input work, a scanner device that captures the prescription is connected to the requesting terminal, the request content sending means, upon acquiring a prescription image obtained by imaging the prescription from the scanner device, automatically sends the prescription image together with the requesting store identification information and the request destination store identification information to the server, and the notification information sending means, upon receiving the prescription image together with the requesting store identification information and the request destination store identification information from the requesting terminal, may send the notification information to the request destination terminal or a device installed in the request destination store. This allows a user at the requesting store to request a prescription input work simply by having the scanner device scan the prescription, thereby reducing the burden on the user and improving the cost-effectiveness of introducing the system.

[0011] In addition, the present invention further comprises a request information storage means for storing request information including the request contents, and a request information display means for displaying the request information in response to a request from the requesting terminal or the request receiving terminal, and the request content transmission means may execute a reading process of the two-dimensional barcode for obtaining information on the prescription when the two-dimensional barcode is printed on the prescription, and transmit the reading result of the two-dimensional barcode to the server as the request contents. This allows the user of the request receiving store to estimate the load for processing the request, making it easier to determine whether to accept the request and who should do the work, and the like, and the cost-effectiveness of introducing the system is high. Effect of the Invention

[0012] The present invention makes it possible for a pharmacy group to efficiently allocate personnel throughout the group, thereby providing a highly cost-effective pharmacy business support system. [Brief description of the drawings]

[0013] [Figure 1] Diagram showing an overview of pharmacy business support system 1 [Diagram 2] An example of data used in pharmacy business support system 1 [Diagram 3] Flowchart showing the process flow of the pharmacy business support system 1 [Figure 4] An example of the scan monitor screen 70 and the request destination store setting screen 80 [Diagram 5] An example of the request management screen 90 [Figure 6] Examples of the request destination store selection screen 100 and the input store selection screen 110 [Figure 7] Examples of the request notification screen 120 and the instruction list screen 130 [Figure 8] An example of a remote connection screen 140 DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] The pharmacy business support system in an embodiment of the present invention is a system suitable for a pharmacy group that operates multiple dispensing pharmacies, and supports temporary support work for pharmacy business between stores of the same pharmacy group. In the following, a store that requests pharmacy business will be referred to as a requesting store, and a store that is requested to perform pharmacy business will be referred to as a requested store. The requesting store and requested store are not limited to stores where patients visit, but also include each department of the head office.

[0015] Although the pharmacy business to be handled is not particularly limited, in the embodiment of the present invention, the prescription input business will be described as an example. The computer system that supports the prescription input business may be the pharmacy business support system in the embodiment of the present invention, or may be a separate system. In the case of a separate system, the configuration may be a cloud configuration using a cloud service, or an on-premise configuration in which a server is installed in each store. Furthermore, in the case of an on-premise configuration, it may be a client-server type configured with a client terminal and a server, or a standalone type configured with a single computer.

[0016] In the embodiment of the present invention, a remote connection function provided by an OS (short for "Operating System") is used. One example is the "Remote Desktop" provided by Microsoft Windows (registered trademark), but is not limited to this.

[0017] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. Fig. 1 is a diagram showing an overview of a pharmacy business support system 1. As shown in Fig. 1, in the pharmacy business support system 1, a request source terminal 2a (terminal 2) installed in a store that requests pharmacy business, a request destination terminal 2b (terminal 2) installed in a store that receives a request for pharmacy business, and a server 3 are connected via a network 6.

[0018] The terminal 2 and the server 3 each include a CPU (short for "Central Processing Unit") as a control unit, memory as a main storage unit, an HDD (short for "Hard Disk Drive") or flash memory as an auxiliary storage unit, an LCD display as a display unit, a keyboard, mouse, or touch panel display as an input unit, a LAN (Local Area Network) cable as a wired communication unit or a wireless module as a wireless communication unit, and a speaker for outputting sound.

[0019] The HDD or flash memory serving as the auxiliary storage unit stores the OS (short for "Operating System"), application programs, data necessary for processing, etc. The control units of the terminal 2 and the server 3 read out the OS and application programs from the auxiliary storage unit and store them in the main storage unit, and while accessing the main storage unit, control other devices and execute the processing described below.

[0020] The terminal 2 is, for example, a tablet terminal, a smartphone, a notebook PC (short for "Personal Computer"), a desktop PC, etc. The server 3 is, for example, a server computer installed in a data center or the like, a virtual server used by a cloud service, etc., and may be realized in one housing or multiple housings. The network 6 is, for example, a VPN (Virtual Private Network), etc., and a secure communication environment is constructed in the entire pharmacy business support system 1.

[0021] A program for causing terminal 2 to function as part of pharmacy business support system 1 is installed in the auxiliary storage unit of terminal 2. A program for causing server 3 to function as part of pharmacy business support system 1 is installed in the auxiliary storage unit of server 3, and a database for storing data used by pharmacy business support system 1 is also constructed.

[0022] The requesting terminal 2a may be connected to a scanner 4 that is installed in the requesting store and scans a printed matter such as a prescription. When the scanner 4 scans the prescription, it generates a prescription image in which the prescription is imaged and transmits it to the requesting terminal 2a. The file format of the prescription image may be a still image file format such as a JPEG file, or a document file format such as a PDF file. The requesting terminal 2b may be connected to a multifunction machine 5 that is installed in the requesting store and has a facsimile function for receiving the prescription image, etc. by facsimile communication and a printer function for printing the prescription image, etc. The scanner 4 installed in the requesting store may be a scanner device with a scanner function such as a multifunction machine. The requesting store may be a facsimile device with a printer function.

[0023] FIG 2 is an example of main data used in pharmacy business support system 1, and shows the table layout of a database constructed in server 3. Store table 10 shown in FIG 2(a) is a table that stores store information. Data items included in store table 10 include store code 11, which is an internal code that uniquely identifies a store, store name 12, which is the name of the store, etc. The primary key of store table 10 is store code 11.

[0024] Account table 20 shown in FIG. 2(b) is a table that stores account information including login information for logging in to pharmacy business support system 1. Data items included in account table 20 are account ID 21, which is an internal code that uniquely identifies a user's account, user ID 22, which is one piece of login information, user name 23 indicating the name of the user, password 24, which is one piece of login information, business authority 25 indicating whether or not the user has authority to support pharmacy business, default store 26, which is the store code of a store treated as the default when performing operations or displaying, etc. The primary key of account table 20 is account ID 21. Password 24 is desirably hashed and stored.

[0025] 2(c) stores account authority information indicating whether each account has authority to remotely connect to each store. Data items included in the account authority table 30 include an account ID 31, which is the same as the account ID 21 described above, a store code 32, which is the same as the store code 11 described above, and the like. The primary key of the account authority table 30 is a composite key of the account ID 31 and the store code 32. For example, if an account "A" has authority to remotely connect to three stores "X", "Y", and "Z", the account authority table 30 stores three pieces of data: (1) account ID 31 is "A" and store code 32 is "X", (2) account ID 31 is "A" and store code 32 is "Y", and (3) account ID 31 is "A" and store code 32 is "Z".

[0026] The store remote connection table 40 shown in FIG. 2(d) stores store remote connection information including remote connection information for remotely connecting to each store. The data items included in the store remote connection table 40 are a store code 41, which is the same as the above-mentioned store code 11, an IP address 42 (= fixed IP address), which is one of the remote connection information, a remote connection user name 43, which is one of the remote connection information, and a remote connection password 44, which is one of the remote connection information. The main key of the store remote connection table 40 is the store code 41. It is preferable that the remote connection password 44 is encrypted and stored. The administrator of the pharmacy business support system 1 assigns an IP address 42 to the terminal 2 of a store that allows remote connection, and sets a remote connection user name 43 and a remote connection password 44 as the qualification information for the remote connection function provided by the OS.

[0027] The remote connection information is information for connecting to the terminal 2 of another store, and if a user knows the remote connection information, the user can connect to the terminal 2 of another store from his / her own smartphone, laptop, etc. Therefore, it is desirable to keep the remote connection information secret from the user. Therefore, the pharmacy business support system 1 provides a mechanism that enables remote connection to another store while keeping the remote connection information secret from the user.

[0028] The request table 50 shown in FIG. 2(e) stores request information including the request contents of the pharmacy work. The data items included in the request table 50 are a request ID 51 that uniquely identifies the request information, a requesting store 52 that is a store code indicating a store that requests the pharmacy work, a requesting store 53 that is a store code indicating a store to which the pharmacy work is requested, an inputting store 54 that is a store code indicating a store in which the pharmacy work is being input, a prescription image 55 that indicates the file name of the prescription image (including the file path as necessary), a scan date and time 56 that indicates the date and time when the prescription was scanned, a scan number 57 that indicates the number of prescription images, a code reading result 58 that indicates the reading result of the two-dimensional barcode included in the prescription image, a patient name 59 that indicates the name of the patient related to the prescription, and an end flag 60 that indicates whether the input work has been completed. In this embodiment, since the request and the prescription correspond one-to-one, the request ID 51 uses information that uniquely identifies the prescription (= prescription ID). Note that instead of the patient name 59, a patient number that uniquely identifies the patient may be used.

[0029] Fig. 3 is a flowchart showing the flow of processing in the pharmacy business support system 1. In each step shown in Fig. 3, the control units of the request source terminal 2a, the server 3, and the request destination terminal 2b execute processing while communicating with each other.

[0030] As shown in FIG. 3, the requesting terminal 2a acquires a prescription image from the scanner 4 (step S1) and transmits the prescription image together with the request contents to the server 3 (step S2). The requesting terminal 2a transmits at least the requesting store identification information (= the store code of the requesting store, etc.) for identifying the requesting store to the server 3 as one of the request contents. The requesting store identification information is pre-stored in the storage unit of the requesting terminal 2a, or has been received from the server 3 when logging in to the pharmacy business support system 1 (= before step S1). In addition, the requesting terminal 2a may transmit the request destination store identification information (= the store code of the request destination store, etc.) for identifying the request destination store together with the server 3 as one of the request contents, or may transmit it to the server 3 separately from the request destination store identification information in the process described later. Furthermore, the request contents may include the scan date and time and the number of scans.

[0031] There are two methods for transmitting the request contents and the prescription image: "automatic transmission" and "manual transmission." In the automatic transmission, the requesting terminal 2a automatically transmits the request contents and the prescription image to the server 3 when the scanner 4 scans the prescription and generates the prescription image. When multiple prescriptions are scanned continuously, the requesting terminal 2a automatically transmits all the prescription images acquired from the scanner 4 together with the request contents to the server 3. In the manual transmission, when the scanner 4 scans the prescription and generates the prescription image, the user checks the contents on the display unit of the requesting terminal 2a and executes them manually via the input unit. Specifically, the requesting terminal 2a accepts the selection of a prescription from the user on a scan monitor screen described later, and transmits the request contents and the prescription image related to the selected prescription to the server 3. The transmission method is preset on a setting screen (not shown) and stored in the memory unit of the requesting terminal 2a or the server 3.

[0032] FIG. 4 shows an example of a scan monitor screen 70 and a request destination store setting screen 80. The scan monitor screen 70 shown in FIG. 4(a) is a screen for confirming and manually transmitting a prescription image acquired from the scanner 4 or the like. The scan monitor screen 70 is configured with a request destination store display section 71 for displaying the store name of the request destination store, a prescription dispensing date display section 72 for displaying the prescription dispensing date, a prescription list display section 73 for displaying a list of prescription data, a photo read button 74, an image confirmation button 75, a send button 76, a close button 77, and the like. Display items of the prescription list display section 73 are a number 73a, patient / medical information 73b, read time 73c, transmission date and time 73d, number of sheets 73e, and the like. The patient / medical information 73b is a patient's name, date of birth, name of a medical institution, name of a medical department, and the like.

[0033] When the requesting terminal 2a acquires a prescription image, it assigns a serial number for each dispensing date, and stores the prescription image and data such as patient and medical information, read date and time, and number of sheets in its own storage unit. When the requesting terminal 2a transmits a prescription image, it stores the transmission date and time in its own storage unit. Then, when the requesting terminal 2a receives an instruction to display the scan monitor screen 70, it displays the information of the requested store stored in the storage unit on the requested store display unit 71, and displays the scan data stored in the storage unit on the prescription list display unit 73.

[0034] If there is no information about the requested store stored in the memory unit, the requesting terminal 2a displays "Requested store" on the requested store display unit 71. Also, for example, if "Store No. 4" is stored in the memory unit as information about the requested store, the requesting terminal 2a displays "Requested store (Store No. 4)" on the requested store display unit 71, as shown in FIG. 4(a).

[0035] The photo read button 74 is used when reading a photo of a prescription taken by a camera in a store where a scanner 4 is not installed. When a user presses the photo read button 74, the requesting terminal 2a displays a specified folder window, accepts a file selection of the photo of the prescription, and displays the selected file as a prescription image. The requesting terminal 2a accepts input of patient and medical information as necessary, assigns a serial number, and stores data such as the patient and medical information, the read date and time, and the number of sheets, as well as the prescription image, in the memory unit.

[0036] The image confirmation button 75 is used when confirming the prescription image. When the user selects the desired data on the prescription list display section 73 and presses the image confirmation button 75, the requesting terminal 2a displays the prescription image of the selected data. Note that when the user double-clicks the desired data on the prescription list display section 73, the requesting terminal 2a may display the prescription image of that data.

[0037] The send button 76 is used when the sending method is set to "manual sending" and the prescription image is sent manually to the server 3. When the user selects the desired data on the prescription list display area 73 and presses the send button 76, the requesting terminal 2a sends the request contents and prescription image of the selected data to the server 3. Note that when the user right-clicks the desired data on the prescription list display area 73 and selects "send prescription" from the right-click menu, the requesting terminal 2a may send the request contents and prescription image of that data to the server 3.

[0038] 4(b) is a screen for setting a request destination store in advance. The request destination store setting screen 80 is composed of a set store display section 81 that displays the set store, a store name list display section 82 that displays a list of store names, a cancel button 83, a clear button 84, a register button 85, etc.

[0039] When the requesting terminal 2a receives an instruction to display the requested store setting screen 80, it acquires information from the store table 10 from the server 3 and displays it in the store name list display unit 82. When the user presses the cancel button 83, the requesting terminal 2a closes the requested store setting screen 80 and returns to the scan monitor screen 70. When the user presses the clear button 84, the requesting terminal 2a clears the display in the set store display unit 81 and deletes the information of the requested store stored in the memory unit. When the user selects one of the stores in the store name list display unit 82 and presses the register button 85, the requesting terminal 2a displays the selected store in the set store display unit 81 and stores it in the memory unit as a requested store.

[0040] Here, the process of reading a two-dimensional barcode included in a prescription image will be described. Some prescriptions have a two-dimensional barcode printed thereon for obtaining prescription information. The two-dimensional barcode is, for example, a QR code (registered trademark). Prescription information includes prescription contents, patient information such as the patient's name and date of birth, and medical information such as the name of the hospital. When this two-dimensional barcode is printed on the prescription, the request destination terminal 2b executes a process of reading the two-dimensional barcode and transmits the reading result of the two-dimensional barcode to the server 3.

[0041] The storage unit of the requesting terminal 2a or the server 3 stores a patient table (not shown) that links a patient number, which is uniquely assigned to each patient, with patient information such as the patient's name and date of birth. If a two-dimensional barcode is included in the prescription image acquired by the scanner 4, the requesting terminal 2a analyzes the two-dimensional barcode. If the analysis of the two-dimensional barcode is successful, the requesting terminal 2a searches the patient table to confirm whether or not patient information acquired by the two-dimensional barcode exists.

[0042] The code reading result is "O" if the analysis of the two-dimensional barcode is successful and the patient information exists in the patient table (= in the case of a patient whose data has already been registered), "△" if the analysis of the two-dimensional barcode is successful but the patient information does not exist in the patient table (= in the case of a new patient), and "X" if the analysis of the two-dimensional barcode fails or the two-dimensional barcode is not included in the prescription image from the scanner 4. The requesting terminal 2a transmits the code reading result to the server 3 as part of the request. Also, if the analysis of the two-dimensional barcode is successful, that is, if the code reading result is "O" or "△", the patient's name, etc. (patient information) can be obtained from the two-dimensional barcode, so the requesting terminal 2a transmits the patient's name, etc. (patient information) to the server 3 as part of the request.

[0043] Returning to the explanation of Fig. 3, when the server 3 receives the request contents and the prescription image from the requesting terminal 2a, it registers them as new request information in the request table 50 (step S3). The server 3 stores the prescription image in a specified folder and with a specified file name in the memory section, then automatically assigns a request ID 51, stores the file name of the prescription image (including the file path as necessary) in the prescription image 55, and stores the request contents in the requesting store 52, the requested store 53 (NULL if not set in advance), the scan date and time 56, the number of scans 57, the code reading result 58, and the patient name 59. The request information registered in the request table 50 can be confirmed on the request management screen.

[0044] FIG. 5 is an example of a request management screen 90. The request management screen 90 shown in FIG. 5 is a screen for checking a list of request information and managing requests. The request management screen 90 is composed of a request information list display section 91 that displays a list of request information, a batch request deletion button 95, a batch request registration button 96, a batch input registration button 97, a search button 98, and the like. The display items of the request information list display section 91 are data selection 91a, prescription ID 91b, request origin store 91c, request destination store 91d, inputting store 91e, prescription image 91f, scan date and time 91g, number of sheets 91h, code reading result 91i, patient name 91j, end check 91k, and the like. A check box 92 is arranged in the data selection 91a, an edit button 93 is arranged in the request destination store 91d, inputting store 91e, and prescription image 91f, and a check button 94 is arranged in the end check 91k.

[0045] When the terminal 2 receives an instruction from the user to display the request management screen 90, it transmits a request to obtain request information to the server 3. The server 3 obtains data from the request table 50 and transmits it to the terminal 2. The terminal 2 displays the data received from the server 3 in the request information list display area 91. Here, the functions of the bulk request deletion button 95 and the search button 98 will be explained, and the functions of the other buttons will be described later.

[0046] When the user checks the checkboxes 92 in the data selection 91a for the desired data and presses the batch request deletion button 95, the terminal 2 transmits a request to delete the data to the server 3. The server 3 deletes the data for which the deletion request is received from the terminal 2 from the request table 50.

[0047] When the user presses the search button 98, the terminal 2 displays a search screen (not shown), accepts the selection of search conditions (store name, etc.), and transmits the search conditions to the server 3. The server 3 searches the request table 50 based on the search conditions received from the terminal 2, and transmits the search result data to the terminal 2. The terminal 2 displays the search result data received from the server 3 in the request information list display unit 91. When the terminal 2 accepts an instruction from the user to display the request management screen 90, it may display a search screen (not shown) and accept the selection of search conditions.

[0048] As shown in FIG. 5, the terminal 2 displays the code reading result 91i in the request information list display section 91 of the request management screen 90. As described above, for prescriptions with a code reading result of "◯", the patient's patient information data has already been registered, so it can be assumed that the load of the prescription input work is low. For prescriptions with a code reading result of "△", the patient's patient information data has not been registered, so it can be assumed that the load of the prescription input work is higher than that of prescriptions with a code reading result of "◯". For prescriptions with a code reading result of "X", the prescription contents, patient information, medical information, etc. have not all been digitized, so it can be assumed that the load of the prescription input work is higher than that of prescriptions with a code reading result of "◯" or "△". In this way, the user of the request destination store can estimate the load for processing the request, making it easier to determine whether to accept the request and who should work on it.

[0049] Returning to the explanation of FIG. 3, the requesting terminal 2a accepts input of the requested store from the user (step S4) and transmits requested store identification information for identifying the requested store to the server 3 (step S5). The server 3 updates the request information based on the requested store identification information received from the requesting terminal 2a (step S6). If the requested store identification information has been set in advance before step S1, the requesting terminal 2a transmits the requested store identification information to the server 3 in step S2, and the server 3 stores the requested store identification information in the requested store 53 in the request table 50 in step S3, so that the processing of steps S4 to S6 is not necessary.

[0050] When the user presses the edit button 93 for the requested store 91d for the desired data on the request management screen 90 in Figure 5, or checks the check box 92 in the data selection 91a for the desired data and presses the bulk request registration button 96, the requesting terminal 2a displays the requested store selection screen.

[0051] Fig. 6 shows an example of a request destination store selection screen 100 and an inputting store selection screen 110. The request destination store selection screen 100 shown in Fig. 6(a) is a screen for selecting a request destination store, and is composed of a store name list display section 101 that displays a list of store names, a cancel button 103, a select button 104, etc. A check box 102 is arranged at the left end of each row in the store name list display section 101.

[0052] When the user checks the check box 102 in the row of the desired store name on the request destination store selection screen 100 and presses the select button 104, the requesting terminal 2a transmits the prescription ID of the data selected on the request management screen 90 and the store code (=request destination store identification information) of the request destination store selected on the request destination store selection screen 100 to the server 3. The server 3 searches the request ID 51 in the request table 50 with the prescription ID received from the requesting terminal 2a, and stores the store code received from the requesting terminal 2a in the request destination store 53.

[0053] Returning to the explanation of FIG. 3, the server 3 transmits notification information indicating that a request has been made from the requesting store to the terminal 2 (=requested terminal 2b) of the store related to the requested store 53 in the request table 50 updated in step S6 (step S7). The requested terminal 2b outputs the notification information received from the server 3 (step S8) and notifies the user of the requested store that a request for pharmacy business support has been made. Note that if the requested store identification information has been set in advance before step S1, the server 3 stores the requested store identification information in the requested store 53 in the request table 50 in step S3, and then immediately executes the process of step S7.

[0054] Fig. 7 shows an example of a request notification screen 120 and an instruction list screen 130. The request notification screen 120 shown in Fig. 7(a) is a screen for notifying that a request for support of pharmacy operations has been received, and is composed of a message display section 121, a confirmation button 122, etc.

[0055] When the request destination terminal 2b receives the notification information from the server 3, it outputs a notification sound from the speaker and displays a message of the notification information on the message display unit 121. In the example shown in Fig. 7(a), a message "A prescription input request from another store has been received" is displayed on the message display unit 121. When the user presses the confirmation button 122, the request destination terminal 2b stops outputting the notification sound and displays the instruction list screen 130 shown in Fig. 7(b).

[0056] Also, the request destination terminal 2b may output a notification to a task tray according to the OS settings. In this case, when the user double-clicks a specific icon in the task tray, the request destination terminal 2b displays an instruction list screen 130 shown in FIG. 7(b).

[0057] The method of sending the notification information is not limited to these. For example, the server 3 may send a prescription image as notification information to the multifunction device 5 connected to the request destination terminal 2b in the request destination store by facsimile. In this case, the multifunction device 5 notifies the user of the request destination store by printing the prescription image received from the server 3. Also, for example, the server 3 may send an e-mail or a message of a chat tool to the request destination terminal 2b as notification information. In this case, the request destination terminal 2b notifies the user of the request destination store by displaying the e-mail or a message on the display unit. Also, for example, instead of the server 3, the request source terminal 2a may send a prescription image as notification information to the multifunction device 5 by facsimile, or send an e-mail or a message of a chat tool to the request destination terminal 2b as notification information.

[0058] 7(b) is a screen for checking a list of instruction information. The instruction list screen 130 is composed of an instruction information list display section 131 for displaying a list of instruction information, a list update button 132, a log button 133, etc. The list update button 132 is a button for updating the contents of the instruction information, and the log button 133 is a button for checking the log of each instruction information.

[0059] Returning to the explanation of Fig. 3, the request destination terminal 2b accepts input of the store being input from the user (step S9) and transmits information about the store being input to the server 3 (step S10). The server 3 updates the request information based on the information received from the request destination terminal 2b (step S11).

[0060] When the user presses the edit button 93 of the store being input 91e for the desired data on the request management screen 90, or checks the check box 92 of the data selection 91a for the desired data and presses the batch input registration button 97, the request destination terminal 2b displays the store being input selection screen 110 shown in Fig. 6(b). The store being input selection screen 110 is a screen for selecting the store being input, and is composed of a store name list display section 111 that displays a list of store names, a cancel button 113, a select button 114, etc. A check box 112 is arranged at the left end of each row of the store name list display section 111.

[0061] When the user checks the check box 112 in the row of the desired store name on the current store selection screen 110 and presses the select button 114, the request destination terminal 2b transmits to the server 3 the prescription ID of the data selected on the request management screen 90 and the store code of the current store selected on the current store selection screen 110. The server 3 searches the request ID 51 in the request table 50 for the prescription ID received from the request destination terminal 2b, and stores the store code received from the request destination terminal 2b in the current store input 54.

[0062] Returning to the explanation of Fig. 3, the request destination terminal 2b accepts input of login information for logging in to the pharmacy business support system 1 and the connection destination store (= the store of the request source terminal 2a) (step S12), and transmits the login information to the server 3 (step S13). The login information for logging in to the pharmacy business support system 1 is different from the remote connection information for remotely connecting to the request source terminal 2a.

[0063] Fig. 8 is an example of a remote connection screen 140. The remote connection screen 140 shown in Fig. 8 is a screen for inputting a connection destination store and login information. The remote connection screen 140 is composed of a connection destination store list display section 141 that displays a list of options for connection destination stores, a user ID input box 142 for inputting a user ID, which is one piece of login information, a password input box 143 for inputting a password, which is one piece of login information, a remote connection button 144, an end button 145, etc. Note that, instead of the user ID, a user name may be used as login information, but the following description will be given assuming that the user ID is used as login information.

[0064] When the request destination terminal 2b receives an instruction from the user to display the remote connection screen 140, it acquires information on the store table 10 from the server 3 and displays it on the connection destination store list display section 141. When the user selects a desired connection destination store on the connection destination store list display section 141, inputs a user ID and password in the user ID input box 142 and password input box 143, and presses the remote connection button 144, the request destination terminal 2b transmits information identifying the connection destination store (= store code of the connection destination store) and login information (= user ID and password) to the server 3.

[0065] Returning to the explanation of Fig. 3, the server 3 authenticates the login information received from the request destination terminal 2b (step S14). Specifically, the server 3 searches the user ID 22 in the account table 20 using the user ID received from the request destination terminal 2b as a search condition, checks whether the password received from the request destination terminal 2b matches the password 24 in the account table 20, and determines that the authentication is successful if they match.

[0066] Next, when the authentication of the login information is successful, the server 3 checks whether the user's account has the authority to remotely connect to the destination store (step S15). Specifically, the server 3 acquires the account ID 21 in the account table 20 related to the user ID 22 authenticated in step S14, searches the account ID and store code 32 in the account authority table 30 using the account ID 21 in the account table 20 and the store code of the destination store received from the request destination terminal 2b as search conditions, and determines that the user has the authority if data exists.

[0067] Next, when the server 3 confirms that there is an authority to perform remote connection, it transmits remote connection information for remotely connecting to the terminal 2 (=requesting terminal 2a) of the destination store to the requested terminal 2b (step S16). Specifically, the server 3 searches the store code 41 in the store remote connection table 40 using the store code of the destination store received from the requested terminal 2b as a search condition, obtains the IP address 42, the remote connection user name 43, and the remote connection password 44, and transmits them as remote connection information to the requested terminal 2b.

[0068] If the server 3 verifies that the authentication of the login information in step S14 has failed or that the user does not have the authority to make a remote connection, the server 3 transmits a message to the request destination terminal 2b indicating that a remote connection is not possible.

[0069] Based on the remote connection information received from the server 3, the request destination terminal 2b remotely connects to the request source terminal 2a using the remote connection function provided by the OS, and executes the prescription input process through the remote connection together with the request source terminal 2a (step S17). Here, the request destination terminal 2b starts the remote connection by background processing without displaying the remote connection information received from the server 3 on the display unit. This enables remote connection to other stores while keeping the remote connection information secret from the user.

[0070] The request destination terminal 2b receives input of the end of the work from the user (step S18), and transmits information of the end of the work to the server 3 (step S19). The server 3 updates the request information based on the information received from the request destination terminal 2b (step S20).

[0071] 5, the request destination terminal 2b sends an update request for the prescription ID and end flag of the desired data to the server 3. The server 3 searches the request ID 51 in the request table 50 using the prescription ID received from the request destination terminal 2b as a search condition, and updates the end flag 60 to "end".

[0072] As described above, the pharmacy business support system 1 in this embodiment includes a request content transmission means by which the request source terminal 2a transmits request content including request destination store identification information for identifying the request destination store and request source store identification information for identifying the request source store to the server 3, a notification information transmission means by which the server 3 or the request source terminal 2a transmits notification information indicating that a request has been made from the request source store to the request destination terminal 2b or a device (= a device having a facsimile function such as the multifunction device 5) installed in the request source store, a remote connection information transmission means by which the server 3 transmits remote connection information for remotely connecting to the request source terminal 2a to the request destination terminal 2b, and a remote connection means by which the request destination terminal 2b remotely connects to the request source terminal 2a based on the remote connection information received from the server 3. This allows staff from a store with surplus staff to support pharmacy business on the computer system in a store that is temporarily short-staffed, thereby making personnel allocation throughout the pharmacy group more efficient and improving the cost-effectiveness of introducing the system.

[0073] The pharmacy business support system 1 further includes an account information storage means (account table 20) in which the server 3 stores account information including login information for a user to log in to the pharmacy business support system 1, a store remote connection information storage means (store remote connection table 40) in which the server 3 stores store remote connection information including remote connection information for each store, a remote connection request transmission means in which the request destination terminal 2b receives login information for an account to log in to the pharmacy business support system 1 and transmits the login information and a remote connection request including the request source store identification information to the server 3, and a login information authentication means in which the server 3 authenticates the login information received from the request destination terminal 2b based on the account information when the login information authentication means successfully authenticates the login information, and the remote connection information transmission means transmits remote connection information related to the request source store identification information to the request destination terminal 2b when the login information authentication means successfully authenticates the login information, and the remote connection means may start the remote connection without displaying the remote connection information received from the server 3. This enables remote connection to other stores while keeping the remote connection information secret from the user. Therefore, the pharmacy business support system 1 can be introduced without lowering the security level even when using the remote connection function provided by the OS, so there is no need to build a unique remote connection function, making the system introduction cost-effective.

[0074] The pharmacy business support system 1 further includes an account authority information storage means (account authority table 30) for storing account authority information indicating the stores for which the account has authority to make a remote connection in the server 3, and an account authority confirmation means for confirming, when the server 3 receives a remote connection request from the request destination terminal 2b, whether or not the account related to the login information received from the request destination terminal 2b has authority to make a remote connection to the store related to the request source store identification information based on the account authority information, and the remote connection information transmission means may transmit the remote connection information to the request destination terminal 2b when the login information authentication means has successfully authenticated the login information and the account authority confirmation means has confirmed the authority of the account. This makes it possible to limit the stores that can be remotely connected according to the position of the personnel, thereby making it possible to streamline the personnel allocation of the entire pharmacy group and making the introduction of the system cost-effective.

[0075] In addition, the pharmacy work in this embodiment is a prescription input work, and a scanner device (= a device having a scanner function) that captures the prescription is connected to the requesting terminal 2a, and when the request content transmitting means obtains a prescription image obtained by imaging the prescription from the scanner device, it automatically transmits the prescription image together with the requesting store identification information and the request destination store identification information to the server 3, and when the notification information transmitting means receives the prescription image together with the requesting store identification information and the request destination store identification information from the requesting terminal 2a, it may transmit the notification information to the request destination terminal 2b or a device installed in the request destination store. As a result, a user of the requesting store can request the prescription input work by simply having the scanner device scan the prescription by setting the request destination store identification information in advance and setting the method of transmitting the prescription image to "automatic transmission", which reduces the burden on the user and increases the cost-effectiveness of introducing the system.

[0076] Furthermore, the pharmacy business support system 1 further comprises a request information storage means (request table 50) in which the server 3 stores request information including the request contents, and a request information display means in which the server 3 displays the request information in response to a request from the requesting terminal 2a or the request receiving terminal 2b, and the request content transmission means may execute a two-dimensional barcode reading process in the case where a two-dimensional barcode for acquiring prescription information is printed on the prescription, and transmit the reading result of the two-dimensional barcode to the server 3 as the request contents. This allows the user of the request receiving store to estimate the load for processing the request, making it easier to judge whether to accept the request and who should do the work, and the like, and thus the cost-effectiveness of introducing the system is high.

[0077] In the flowchart shown in FIG. 3, the registration of the store 54 being entered in the request table 50 (steps S9 to S11) and the update of the end flag 60 (steps S18 to S20) are performed based on input by the user of the requested store, but these processes may also be performed automatically by the server 3 at an appropriate time without input by the user of the requested store.

[0078] For example, when the computer system supporting prescription input work is the pharmacy business support system 1 in the embodiment of the present invention, when the request receiving terminal 2b remotely connects to the requesting terminal 2a and transmits to the server 3 a request to start prescription input of the prescription ID corresponding to the request ID 51, the server 3 updates the inputting store 54 in the request table 50 with the store code related to the request receiving terminal 2b. Also, when the request receiving terminal 2b is remotely connected to the requesting terminal 2a and transmits to the server 3 a request to end prescription input of the prescription ID corresponding to the request ID 51, the server 3 updates the end flag 60 in the request table 50 to "end".

[0079] Also, for example, if the computer system that supports the prescription input task is a system separate from the pharmacy business support system 1 in the embodiment of the present invention, the server 3 updates the input store 54 in the request table 50 with the store code related to the request destination terminal 2b when it sends the remote connection information to the request destination terminal 2b. When the request destination terminal 2b ends the remote connection of the request source terminal 2a, it sends information about the end of the task to the server 3, and the server 3 updates the end flag 60 in the request table 50 to "end".

[0080] In this way, the server 3 automatically registers the stores 54 currently being entered in the request table 50 and updates the completion flag 60 at an appropriate time, thereby reducing the work procedures of the user at the requesting store, reducing the burden on the user and making the system introduction cost-effective.

[0081] Although the preferred embodiment of the pharmacy business support system according to the present invention has been described above with reference to the attached drawings, the present invention is not limited to such an embodiment. It is clear that a person skilled in the art can come up with various modified or revised examples within the scope of the technical ideas disclosed in this application, and it is understood that such modified or revised examples also naturally belong to the technical scope of the present invention. [Explanation of symbols]

[0082] 1. Pharmacy business support system 2. Terminal 2a: Requesting terminal 2b: Requested terminal 3. Server 4. Scanner 5……Multifunction device 6. Network 10.……Store table 20...Account table 30...Account authority table 40: Store remote connection table 50: Request table 70: Scan monitor screen 80: Request store setting screen 90...Request Management Screen 100.....Request store selection screen 110...Current store selection screen 120...Request notification screen 130...Instruction list screen 140...Remote connection screen

Claims

1. A pharmacy business support system in which a request source terminal installed in a store that requests pharmacy business, a request destination terminal installed in a store that receives the pharmacy business, and a server are connected via a network, a request content transmission means for transmitting to the server request content including request source store identification information for identifying the request source store and request destination store identification information for identifying the request destination store; a notification information transmission means for transmitting notification information indicating that a request has been made from the request source store to the request destination terminal or a device installed in the request destination store by the server or the request source terminal; a remote connection information transmitting means for transmitting, to the request destination terminal, remote connection information for remotely connecting to the request source terminal by the server; a remote connection means for remotely connecting the request destination terminal to the request source terminal based on the remote connection information received from the server; A pharmacy business support system comprising:

2. The server has an account information storage means for storing account information including login information for logging in to the pharmacy business support system by an account; a store remote connection information storage means for storing store remote connection information including the remote connection information for each store; a remote connection request transmitting means for transmitting, to the server, a remote connection request including the login information and the request source store identification information, the remote connection request transmitting means for transmitting, to the server, the login information, the remote connection request including the request source store identification information, a login information authentication means for authenticating the login information received from the request destination terminal based on the account information when the server receives the remote connection request from the request destination terminal; Further comprising: the remote connection information transmitting means transmits the remote connection information relating to the request source store identification information to the request destination terminal when the authentication of the login information by the login information authenticating means is successful; The remote connection means starts the remote connection without displaying the remote connection information received from the server. The pharmacy business support system according to claim 1 .

3. an account authority information storage means for storing account authority information indicating a store for which the account has authority to make a remote connection; an account authority confirmation means for confirming, when the server receives the remote connection request from the request destination terminal, whether or not the account related to the login information received from the request destination terminal has authority to make a remote connection to a store related to the request source store identification information, based on the account authority information; Further comprising: The remote connection information transmitting means transmits the remote connection information to the requested terminal when the login information authenticating means has successfully authenticated the login information and the account authority has been confirmed by the account authority confirming means. The pharmacy business support system according to claim 2 .

4. The pharmacy work is a prescription input work, A scanner device for capturing the prescription is connected to the requesting terminal, When the request content transmission means acquires a prescription image obtained by imaging the prescription from the scanner device, the request content transmission means automatically transmits the prescription image together with the request source store identification information and the request destination store identification information to the server; The notification information transmission means, when receiving the prescription image together with the request source store identification information and the request destination store identification information from the request source terminal, transmits the notification information to the request destination terminal or a device installed in the request destination store.

4. The pharmacy business support system according to claim 1, wherein the pharmacy business support system is a system for providing a pharmacy service to a patient.

5. The server has a request information storage means for storing request information including the request content; a request information display means for displaying the request information in response to a request from the request source terminal or the request destination terminal; Further comprising: The request content transmission means, when a two-dimensional barcode for acquiring information on the prescription is printed on the prescription, executes a process of reading the two-dimensional barcode and transmits the result of reading the two-dimensional barcode to the server as the request content. The pharmacy business support system according to claim 4.

Images