JP7376761B1 - Programs, systems and methods - Google Patents

Abstract

The present invention provides a program, system, and method for suppressing the inappropriate use of electronic prescriptions that may occur due to the conversion of prescriptions into data. [Solution] In a prescription management system in which a prescription management server, an electronic prescription DB server, a medical institution server, a patient terminal, and a pharmacy terminal are connected to a communication line by wire or wirelessly, the prescription management server includes: An acquisition process for acquiring prescription data, a processing process for processing the prescription data to change the display mode, and an output process for outputting the prescription data are executed. In the output process, the prescription data is output in a manner depending on the acquisition manner or output destination. [Selection diagram] Figure 5

Description

Application of Article 30, Paragraph 2 of the Patent Act On July 11, 2020, the online medical treatment and medication guidance system “CLINICS” website https://clinics-app. Published on July 11, 2020 on the app distribution service "Google Play" https://play.com/. google. com/store/apps/details? id=life. medley. Published on clinics On July 11, 2020, the app distribution service “App Store” https://apps. apple. Published at com/jp/app/id1106261604 On October 28, 2020, Medley Co., Ltd.'s "Tech Blog" https://developer.com/jp/app/id1106261604 medley. Published at jp/entry/2022/10/28/153818 [Publications, etc.]

TECHNICAL FIELD The present invention relates to programs, systems, and methods.

Patent Document 1 discloses a technique for transmitting image data of a paper-issued prescription to a pharmacy. Patent Document 2 discloses a technique for transmitting an electronically issued prescription to a pharmacy.

Japanese Patent Application Publication No. 2015-95169 Japanese Patent Application Publication No. 2022-37989

As prescriptions are converted into data, various problems can arise.

According to one aspect of the present invention, a program is provided. This program causes the computer to execute an acquisition process for acquiring prescription data, a processing process for processing the prescription data to change the display mode, and an output process for outputting the prescription data. In the output process, the prescription data is output in a manner depending on the acquisition manner or output destination.

According to such an aspect, it is possible to suppress the occurrence of problems that may occur due to converting prescriptions into data.

1 is a diagram showing the overall configuration of a prescription management system 1. FIG. 1 is a diagram showing a hardware configuration of a prescription management server 10. FIG. 4 is a diagram showing the hardware configuration of a patient terminal 40. FIG. FIG. 3 is a diagram showing the functional configuration of a control section of each device. FIG. 3 is an activity diagram showing an example of management processing. It is a figure showing an example of information stored in electronic prescription DB. 2 is a diagram showing an example of a screen of the prescription management system 1. FIG. It is a figure showing an example of the flow of processing. It is a figure showing an example of displayed prescription data. It is a figure which shows another example of displayed prescription data. FIG. 7 is an activity diagram showing another example of management processing. FIG. 3 is a diagram showing an example of a read paper prescription. It is a diagram showing an example of information stored in a paper prescription DB. 2 is a diagram showing an example of a screen of the prescription management system 1. FIG. It is a figure showing an example of displayed prescription data. FIG. 7 is an activity diagram showing another example of management processing. It is a figure showing an example of displayed prescription data. FIG. 2 is a diagram illustrating an example of a schedule in which medication guidance can be provided. It is a figure showing an example of displayed pharmacy information. 2 is a diagram showing a functional configuration of a control unit 11 of a prescription management server 10. FIG. It is a figure which shows an example of the displayed reservation screen.

Embodiments of the present invention will be described below with reference to the drawings. Various features shown in the embodiments described below can be combined with each other.

By the way, the program for implementing the software appearing in this embodiment may be provided as a non-transitory computer-readable recording medium, or may be downloaded from an external server. The program may be provided in a manner that allows the program to be started on an external computer and the function thereof is realized on the client terminal (so-called cloud computing).

Furthermore, in this embodiment, the term "unit" may include, for example, a combination of hardware resources implemented by circuits in a broad sense and software information processing that can be concretely implemented by these hardware resources. . In addition, various types of information are handled in this embodiment, and these information include, for example, the physical value of a signal value representing voltage and current, and the signal value as a binary bit collection consisting of 0 or 1. It is expressed by high and low levels or quantum superposition (so-called quantum bits), and communication and calculations can be performed on circuits in a broad sense.

Further, a circuit in a broad sense is a circuit realized by at least appropriately combining a circuit, a circuit, a processor, a memory, and the like. That is, application specific integrated circuits (ASIC), programmable logic devices (for example, simple programmable logic devices (SPLD), complex programmable logic devices (COMPLEX), etc. Programmable Logic Device (CPLD), and field This includes a field programmable gate array (FPGA) and the like.

1. Hardware Configuration In this section, the hardware configuration of the prescription management system according to this embodiment will be described.

FIG. 1 is a diagram showing the overall configuration of a prescription management system 1. As shown in FIG. FIG. 1 shows an overview of each device included in the prescription management system 1, the users who use each device, and the information processed in each device. Each outline will be explained from time to time with reference to other figures.

The prescription management system 1 is an information processing system that manages prescriptions issued during medical treatment at a medical institution. A prescription is a document issued by a doctor who has examined the patient at a medical institution to prescribe a drug, and used by a pharmacist for dispensing the drug, and describes the type of drug, its dosage, administration method, etc. The prescription management system 1 includes a communication line 2, a prescription management server 10, an electronic prescription DB server 20, a medical institution server 30, a patient terminal 40, and a pharmacy terminal 50. Note that the prescription management system 1 may include two or more patient terminals 40 and two or more pharmacy terminals 50, but only one is shown in FIG. 1. The communication line 2 includes the Internet, etc., and mediates the exchange of data between devices connected to the communication line. Each device included in the prescription management system 1 is connected to the communication line 2 by wire or wirelessly.

The patient terminal 40 is a terminal used by a patient receiving medical treatment at a medical institution. The pharmacy terminal 50 is a terminal used by a pharmacist who dispenses medicines at a pharmacy. Each terminal is, for example, an information processing terminal such as a desktop computer, a notebook computer, a tablet terminal, or a smartphone.

The prescription management server 10 is an information processing device that executes processing for managing prescriptions. The electronic prescription DB server 20 is an information processing device that controls a database that stores electronic prescriptions. An electronic prescription is an electronic version of prescription information. The medical institution server 30 is an information processing device that constitutes a medical institution system, and executes processing related to medical services. It is assumed that the prescription management system 1 uses electronic prescriptions, and the medical institution server 30 issues electronic prescriptions.

FIG. 2 is a diagram showing the hardware configuration of the prescription management server 10. The prescription management server 10 includes a control section 11, a storage section 12, a communication section 13, and a bus 14. The bus 14 electrically connects each part of the prescription management server 10.

(Control unit 11)
The control unit 11 is, for example, a central processing unit (CPU) not shown. The control unit 11 is a computer that implements various functions related to the prescription management system 1 by reading predetermined programs stored in the storage unit 12. That is, information processing by software stored in the storage unit 12 is specifically implemented by the control unit 11, which is an example of hardware, so that it can be executed as each functional unit included in the control unit 11. These will be explained in more detail in the next section. Note that the control section 11 is not limited to a single control section, and may be implemented so as to have a plurality of control sections 11 for each function. It may also be a combination thereof.

(Storage unit 12)
The storage unit 12 stores various information defined by the above description. This may be used, for example, as a storage device such as a solid state drive (SSD) that stores various programs related to the prescription management system 1 executed by the control unit 11, or as a temporary storage device related to program calculations. It can be implemented as a memory such as a random access memory (RAM) that stores information (arguments, arrays, etc.) necessary for the process. The storage unit 12 stores various programs, variables, etc. related to the prescription management system 1 executed by the control unit 11.

(Communication Department 13)
The communication unit 13 is configured to be capable of transmitting various electrical signals from the prescription management server 10 to external components. Furthermore, the communication unit 13 is configured to be able to receive various electrical signals from external components to the prescription management server 10. More preferably, the communication unit 13 has a network communication function, so that various information can be communicated between the prescription management server 10 and external devices via the communication line 2.

The electronic prescription DB server 20 and the medical institution server 30 have the same hardware configuration as the prescription management server 10. Note that the control units of the electronic prescription DB server 20 and the medical institution server 30 will be described with reference numerals 21 and 31, respectively, to distinguish them from the control unit 11 of the prescription management server 10.

FIG. 3 is a diagram showing the hardware configuration of the patient terminal 40. The patient terminal 40 includes a control section 41 , a storage section 42 , a communication section 43 , an input section 44 , an output section 45 , and a bus 46 . The bus 46 electrically connects each part of the patient terminal 40. The control unit 41, the storage unit 42, and the communication unit 43 are the same hardware as the control unit 11, the storage unit 12, and the communication unit 13 shown in FIG. 2, although their specs, models, etc. may be different.

(Input section 44)
The input unit 44 has one or more input interfaces such as keys, buttons, a touch screen, a mouse, etc., and accepts input from a user.
(Output section 45)
The output unit 45 has an output device such as a display and a speaker, and displays visual information such as a screen, image, icon, text, etc. generated in a form that can be viewed by the user on the display surface, and outputs sound including audio. Output.

The pharmacy terminal 50 has the same hardware configuration as the patient terminal 40. Note that the control section and input section of the pharmacy terminal 50 will be described with reference numerals 51 and 54 to distinguish them from the control section 41 and input section 44 of the patient terminal 40. It is assumed that the input unit 44 of the patient terminal 40 includes an imaging device such as a digital camera. Furthermore, the input unit 54 of the pharmacy terminal 50 is equipped with a reading device (scanner) that reads images from paper.

2. Functional Configuration This section describes the functional configuration of this embodiment. As described above, the information processing by the software stored in the storage section of each device is specifically implemented by the control section, which is an example of hardware, so that each functional section included in the control section can be executed.

FIG. 4 is a diagram showing the functional configuration of the control section of each device. The control unit 11 of the prescription management server 10 includes a server display unit 111, a DB control unit 112 (DB:Database), an authentication unit 113, a data acquisition unit 114, a data processing unit 115, a data output unit 116, It includes a terminal determining section 117 and a prescription determining section 118. The control unit 21 of the electronic prescription DB server 20 includes a DB control unit 211 and an authentication unit 212. The control unit 31 of the medical institution server 30 includes a server display unit 311, a DB control unit 312, an authentication unit 313, and a business processing unit 314. The control unit 41 of the patient terminal 40 includes a first user display unit 411, a first operation reception unit 412, and an image reading unit 413. The control unit 51 of the pharmacy terminal 50 includes a second user display unit 511, a second operation reception unit 512, and an image reading unit 513.

The server display unit 111 of the prescription management server 10 executes processing for displaying a system screen related to the prescription management system 1 on each terminal. The server display unit 111 performs processing such as generating and transmitting an HTML (Hyper Text Markup Language) file, and causes the patient terminal 40 to display a web page showing a system screen. Note that the server display unit 111 may perform processing such as generating and transmitting display data of an application for using the prescription management system 1.

The DB control unit 112 controls inputting and outputting data to and from various databases. The authentication unit 113 executes processing related to user authentication. The data acquisition unit 114 executes acquisition processing to acquire prescription data indicating a prescription. The manner in which prescription data is acquired (hereinafter referred to as "acquisition manner") includes, for example, a manner in which data indicating an electronic prescription is acquired from the electronic prescription DB server 20 (the acquisition manner is "electronic prescription"), and a manner in which data indicating an electronic prescription is acquired from the electronic prescription DB server 20. 40 or the pharmacy terminal 50 (the acquisition mode is "paper prescription scan data").

The data processing unit 115 executes a processing process to process the acquired prescription data. The data output unit 116 executes an output process to output processed prescription data. The terminal determining unit 117 determines whether the prescription data is output to the patient terminal 40 or the pharmacy terminal 50. The prescription determining unit 118 determines whether the prescription data is acquired as electronic prescription data or scanned data of a paper prescription.

The DB control unit 211 of the electronic prescription DB server 20 controls inputting and outputting of data to and from the electronic prescription database. Authentication unit 212 executes processing related to user authentication. The server display unit 311 of the medical institution server 30 executes processing for displaying a system screen related to the medical institution's system on each terminal. The DB control unit 312 controls inputting and outputting data into and out of various databases related to the medical institution's system. The authentication unit 313 executes processing related to user authentication. The business processing unit 314 executes various processes related to medical business.

The first operation receiving unit 412 of the patient terminal 40 controls the display on the display, which is a display means included in the patient terminal 40. The first user display unit 411 displays, for example, a screen of a web page or an application transmitted from the server display unit 111 on a display unit. The first operation accepting unit 412 accepts operations performed by the patient. The image reading unit 413 generates scan data by reading the paper prescription using the imaging device of the input unit 44 .

The second user display unit 511 of the pharmacy terminal 50 controls the display on the display, which is a display means included in the pharmacy terminal 50. The second user display unit 511 displays, for example, a screen of a web page or an application transmitted from the server display unit 111 on a display unit. The second operation accepting unit 512 accepts operations performed by a pharmacist. The image reading unit 513 generates scan data by reading the paper prescription using the reading device of the input unit 44 .

3. Information Processing This section describes information processing that a program causes a computer to execute in this embodiment. The prescription management system 1 includes a processor capable of executing a program to perform each step (each process) described below. The prescription management system 1 executes management processing for managing prescription data. First, management processing when an electronic prescription is issued will be described below.

Note that both the patient using the patient terminal 40 and the pharmacist using the pharmacy terminal 50 are registered as users of the prescription management system 1, and can use the prescription management system 1 by logging in using user authentication information. It is now available for use. Therefore, in the prescription management system 1, it is possible to know who the user is using each terminal from the user authentication information, and also to know the user information (name, etc.) registered by the user. It has become.

Further, the user identification information may be different or unified in the prescription management server 10, the electronic prescription DB server 20, and the medical institution server 30. Assume that even if the user identification information is different, it can be determined that the users are the same person based on the conversion table. In this embodiment, in order to make the explanation easier to understand, it is assumed that patient identification information is unified by "patient ID".

FIG. 5 is an activity diagram showing an example of management processing. The activity shown in FIG. 5 is started when a patient is examined at a medical institution and the doctor performs an operation to input prescription information. First, the medical institution server 30 receives input of prescription information from a doctor (A11). Next, the medical institution server 30 generates an electronic prescription including the input prescription information and information such as the medical institution and patient name stored in the medical institution system (A12).

The medical institution server 30 transmits information included in the generated electronic prescription (hereinafter referred to as “electronic prescription information”) to the electronic prescription DB server 20. Furthermore, in this embodiment, the medical institution server 30 transmits information (hereinafter referred to as "medical information") regarding the medical institution where the patient to whom the electronic prescription has been issued has been examined, to the electronic prescription DB server 20. The electronic prescription DB server 20 stores the transmitted electronic prescription information and medical information in the electronic prescription DB by the DB control unit 211 (A13).

FIG. 6 is a diagram showing an example of information stored in the electronic prescription DB. The electronic prescription DB1 shown in FIG. 6 stores the drug type, dosage, administration method, date of issue, medical institution name, doctor name, patient name, patient ID, etc. as electronic prescription information. Furthermore, the electronic prescription DB 1 stores medical examination results, medical records, hospital locations, doctor information, etc. as medical information. In this way, electronic prescription information and medical information are accumulated in the electronic prescription DB server 20.

Note that medical information may be stored in the prescription management server 10 instead of the electronic prescription DB server 20. In that case, the prescription management server 10 has a medical information DB for storing medical information, and stores the medical information in the medical information DB. The electronic prescription information stored in the electronic prescription DB server 20 and the medical information stored in the prescription management server 10 are associated with each other by a patient ID. Further, as will be described in detail later, paper prescription information including scan data obtained by optically reading a paper prescription and digitizing it is also stored in the electronic prescription DB server 20.

Next, it is assumed that the patient performs an operation on the patient terminal 40 to obtain an electronic prescription to submit to the pharmacy.
FIG. 7 is a diagram showing an example of a screen of the prescription management system 1. On the system screen G1 shown in Figure 7, enter the character string "Search for a prescription.", "Patient name", "Patient ID", "Medical institution name", "Issuance date" and "Record date". Input fields C11, C12, C13, C14, and C15 and a prescription data display button B11 are displayed. User information registered by the patient may be displayed in advance in the "patient name" and "patient ID.""Patientname" and "patient ID" are information for searching both electronic prescription information and paper prescription information. "Medical institution name" and "issue date" are mainly information for searching electronic prescription information. On the other hand, the "record date" is information for searching paper prescription information, and will be described in detail later.

When the display button B11 is operated with at least the patient name or patient ID input, the first operation reception unit 412 of the patient terminal 40 accepts the operation as a prescription request operation, and the information on the input items is sent to the patient terminal 40. Request data requesting output of the included prescription data is transmitted to the prescription management server 10 (A21). When the display button B11 is operated, the first operation reception unit 412 transmits request data whose output destination is the own terminal (patient terminal 40). The prescription management server 10 requests prescription data by having the data acquisition unit 114 transfer the request data sent from the patient terminal 40 to the electronic prescription DB server 20 (A22).

The electronic prescription DB server 20 uses the DB control unit 211 to read out the electronic prescription including information on the items indicated by the transmitted request data (A23). The DB control unit 211 transmits prescription data indicating the read electronic prescription to the prescription management server 10. The prescription management server 10 causes the data acquisition unit 114 to execute an acquisition process to acquire the transmitted prescription data (A31: acquisition step).

Next, the prescription management server 10 uses the terminal determination unit 117 to determine the output destination of the prescription data (A32: first determination step). When the request data of the prescription data indicates an output destination, the terminal determination unit 117 determines the output destination as the output destination of the prescription data. Here, the terminal determination unit 117 determines that the output destination is the patient terminal 40, which is the output destination indicated by the transmitted request data.

Subsequently, the prescription management server 10 uses the prescription determination unit 118 to determine the acquisition mode of prescription data (A33: second determination step). For example, the prescription determination unit 118 inquires of the electronic prescription DB server 20 whether information indicated by the output prescription data is stored. If the prescription data indicates electronic prescription information, a reply indicating that the prescription data is stored is received from the electronic prescription DB server 20, so the prescription determining unit 118 determines that the acquisition mode of the prescription data is an electronic prescription. Further, if the prescription data does not indicate electronic prescription information, a reply is received from the electronic prescription DB server 20 indicating that it is not stored, so the prescription determining unit 118 determines that the prescription data acquisition mode is a paper prescription. do. In the example of FIG. 5, the prescription determining unit 118 determines that the acquisition mode is an electronic prescription.

Note that the determination method in the second determination step is not limited to this. For example, when the electronic prescription DB server 20 outputs prescription data, it adds flag information indicating that the prescription data is an electronic prescription. Then, if the flag information is added to the output prescription data, the prescription determining unit 118 determines that the prescription data acquisition mode is an electronic prescription, and if the flag information is not added, the prescription determining unit 118 determines that the prescription data acquisition mode is an electronic prescription. It may be determined that the data acquisition mode is a paper prescription.

Next, the prescription management server 10 causes the data processing unit 115 to execute a processing process for processing the acquired prescription data (A34: processing step). The processing will be explained with reference to FIG. 8.

FIG. 8 is a diagram showing an example of the processing flow. The data processing unit 115 first determines whether the result (first determination result) of the first determination step of A32 shown in FIG. 5 is the patient terminal 40 or the pharmacy terminal 50 (S11). If it is determined in S11 that it is the patient terminal 40, the data processing unit 115 determines whether the result of the second determination step in A33 (second determination result) is a paper prescription or an electronic prescription (S12).

If the data processing unit 115 determines that the prescription is a paper prescription in S12, the data processing unit 115 performs original processing on the acquired prescription data as a processing process (S13). Original document processing is processing that indicates that the prescription indicated by the prescription data is an original document. In this embodiment, the data processing unit 115 performs processing to insert the character string "original" into the prescription indicated by the prescription data as original processing.

If the data processing unit 115 determines that the prescription data is an electronic prescription in S12, the data processing unit 115 performs copying processing and processing of adding general medical information to the acquired prescription data as processing processing (S14). Copy processing is processing that indicates that the prescription indicated by the prescription data is not the original. In this embodiment, the data processing unit 115 performs a process of inserting the character string "copy" into the prescription indicated by the prescription data as a copy process.

Through the above processing, it is possible to distinguish that the prescription data that has undergone original processing is the original, and that the prescription data that has undergone copy processing is not the original. In addition, prescription data indicating an electronic prescription before copy processing is data that can be used as an original, but prescription data indicating an electronic prescription after copy processing is written as "copy". It is no longer used as an original document, and it is effectively no longer an original document.

Note that the data processing unit 115 may process the above character string into a watermark (a character string or the like made semi-transparent so that the background can be seen through). In this case, it is desirable that the watermark be visible even when displayed on a display. Further, the data processing unit 115 may represent the original document by not processing it. Even in this case, it is possible to distinguish that unprocessed prescription data is the original, and that copy-processed prescription data is not the original. In this embodiment, the above-mentioned original processing will be described so as to be easily distinguishable.

General medical information is medical information that can be understood by ordinary people such as patients, and is, for example, information such as hospital location and doctor information among the medical information shown in FIG. The data processing unit 115 accesses the electronic prescription DB server 20 (or accesses the medical information DB of its own device if medical information is stored in the prescription management server 10) and retrieves general medical information from the electronic prescription DB 1. Processing to read and add the read general medical information is performed as a processing process.

If it is determined in S11 that it is the pharmacy terminal 50, the data processing unit 115 determines whether the result of the second determination step in A33 (second determination result) is a paper prescription or an electronic prescription (S21).

When the data processing unit 115 determines that the prescription is a paper prescription in S21, the data processing unit 115 performs copy processing on the acquired prescription data (S22).

If the data processing unit 115 determines that it is an electronic prescription in S21, the data processing unit 115 performs original processing and processing for adding specialized medical information to the acquired prescription data (S23). The specialized medical information is information related to specialized medical care that can only be understood by a specialist such as a pharmacist, and is, for example, information such as medical examination results and medical records among the medical information shown in FIG. 6. The data processing unit 115 accesses the electronic prescription DB server 20, reads specialized medical information from the electronic prescription DB 1, and performs processing to add the read specialized medical information.

The data processing unit 115 completes the processing after executing S13, S14, S22, and S23. Next, the prescription management server 10 outputs the prescription data processed in A34 by the data output unit 116 (A35: output step). The data output unit 116 here outputs the prescription data to the patient terminal 40 determined to be the output destination in A32. The patient terminal 40 displays the prescription indicated by the output prescription data on the first user display unit 411 (A41).

FIG. 9 is a diagram showing an example of displayed prescription data. On the system screen G2 shown in FIG. 9, an electronic prescription D21, general medical information E21, and a send to pharmacy button B21 are displayed. The electronic prescription D21 is an image of the electronic prescription indicated by the output prescription data. A character string D22 "copy" has been processed and added to the electronic prescription D21. In this way, in the example of FIG. 9, prescription data that has been subjected to the processing (copy processing + addition of general medical information) of S14 shown in FIG. 8 is displayed.

Here, suppose that the patient terminal 40 takes a screenshot of the system screen G2 and sends a captured image generated by the screenshot to the pharmacy terminal 50 by the patient's operation. In this case, the pharmacy terminal 50 displays the transmitted captured image, but since the captured image includes the character string D22 "copy", the pharmacist can confirm that the captured image is not the original of the prescription. I understand.

When the patient confirms that the electronic prescription is to be submitted to the pharmacy based on the contents of the displayed electronic prescription, the patient operates the send to pharmacy button B21. It is assumed that the destination pharmacy is set in advance or selected on a selection screen (not shown). In that case, the patient terminal 40 receives the operation as a prescription request operation by the first operation reception unit 412, and transmits request data requesting the displayed prescription data to the prescription management server 10 (A21). When the send button B21 is operated, the first operation receiving unit 412 sends the request data to the pharmacy terminal 50 as the output destination.

After this, the processes from A22 to A33 shown in FIG. 5 are executed. In this case, the output destination of the prescription data is determined to be the pharmacy terminal 50 in A32 (first determination step). Then, in the processing process of A34, the first determination result is the pharmacy terminal 50, and the second determination result is the electronic prescription, so the data processing unit 115 performs S23 (original document processing and adding specialized medical information) shown in FIG. processing). Then, the data output unit 116 outputs the processed prescription data to the output destination pharmacy terminal 50 (A35). The pharmacy terminal 50 displays the output prescription data on the second user display section 511 (A42).

FIG. 10 is a diagram showing another example of displayed prescription data. On the system screen G3 shown in FIG. 10, an electronic prescription D31 and specialized medical information E31 are displayed. The electronic prescription D31 is an image of the electronic prescription indicated by the output prescription data. A character string D32 "original" has been processed and added to the electronic prescription D31. In this way, in the example of FIG. 10, prescription data on which the processing process (original document processing + specialized medical information addition) of S23 shown in FIG. 8 has been executed is displayed.

Note that a prescription request operation may be performed at the pharmacy terminal 50 in the same manner as at the patient terminal 40. In that case, the pharmacy terminal 50 performs the same process as A21 (prescription request operation) and transmits request data whose output destination is the own terminal (pharmacy terminal 50) (A43). As a result, the prescription data shown in FIG. 10 is output and displayed. Since this prescription data represents the original, it can be printed and a copy stored in the pharmacy, for example.

Next, management processing when a paper prescription is digitized will be explained.
FIG. 11 is an activity diagram showing another example of management processing. The activity shown in FIG. 11 is started when a patient is examined at a medical institution, the patient receives a paper prescription, and performs an operation to read the paper prescription with the patient terminal 40. In the case of the patient terminal 40, an operation of photographing a paper prescription using an imaging device is performed as a reading operation. First, the patient terminal 40 reads a paper prescription using the image reading unit 413 (A51) and generates scan data (A52).

FIG. 12 is a diagram showing an example of a read paper prescription. On the system screen G4 shown in FIG. 12, a prescription image E41 and a prescription data recording button B41 are displayed. The prescription image E41 is an image showing the paper prescription F41 read in A51. If there is no problem with the displayed prescription image E41, the patient operates the record button B41. Through this operation, the patient terminal 40 transmits the read data including the generated scan data to the prescription management server 10 (so-called upload). The prescription management server 10 uses the DB control unit 112 to store scan data and the like indicated by the transmitted (uploaded) read data in the paper prescription DB as paper prescription information (A53).

FIG. 13 is a diagram showing an example of information stored in the paper prescription DB. The paper prescription DB 2 shown in FIG. 13 stores scan data of paper prescriptions, recording date and time, patient name, and patient ID as paper prescription information. By storing this information, a paper prescription is recorded. The medical information stored in the electronic prescription DB1 shown in FIG. 8 is not stored in the paper prescription DB2.

Note that, for example, the prescription management server 10 executes OCR (Optical Character Recognition) processing on the scan data of the paper prescription and converts the read items (name of drug, name of medical institution, date of issue, etc.) into the paper prescription. The DB control unit 112 may store the information in the paper prescription DB 2. Even in that case, since only the information written on the paper prescription is stored, no medical information is stored in the paper prescription DB 2.

Next, it is assumed that the patient performs an operation on the patient terminal 40 to obtain scan data of a paper prescription to present to the pharmacy.
FIG. 14 is a diagram showing an example of a screen of the prescription management system 1. On the system screen G5 shown in Figure 14, enter the character string "Search for a prescription.", "Patient name", "Patient ID", "Medical institution name", "Issuance date" and "Record date". Input fields C51, C52, C53, C54, and C55 and a display button B51 are displayed.

The "recorded date" input field C55 is an input field for inputting the date on which the scan data of the paper prescription was uploaded as a search condition. "Medical institution name" and "issue date" are normally information used to search for electronic prescription information, but if this information is stored in the paper prescription DB2 by the above-mentioned OCR processing, the paper It also serves as information for searching prescription information. The system screen G5 is the same screen as the system screen G1 shown in FIG. In this way, in the prescription management system 1, both electronic prescription information and paper prescription information can be searched from the same search screen.

When the display button B51 is operated with at least a patient name or patient ID input, the first operation reception unit 412 of the patient terminal 40 accepts the operation as a prescription request operation, and the information on the input items is sent to the patient terminal 40. Request data requesting output of the included prescription data is transmitted to the prescription management server 10 (A61). When the display button B51 is operated, the first operation reception unit 412 transmits request data whose output destination is the own terminal (patient terminal 40).

The prescription management server 10 uses the data acquisition unit 114 to read, as prescription data, paper prescription information including information on the items indicated by the request data transmitted from the patient terminal 40 (A62). The prescription management server 10 causes the data acquisition unit 114 to execute an acquisition process to acquire the read prescription data (A31).

Next, the prescription management server 10 uses the terminal determination unit 117 to determine the output destination of the prescription data (A32: first determination step). Here, the terminal determination unit 117 determines that the output destination is the patient terminal 40, which is the output destination indicated by the transmitted request data. Subsequently, the prescription management server 10 uses the prescription determination unit 118 to determine the acquisition mode of prescription data (A33: second determination step).

For example, the prescription determination unit 118 inquires of the electronic prescription DB server 20 whether information indicated by the output prescription data is stored as described above, and based on the answer, determines whether the prescription data acquisition mode is an electronic prescription or It is determined that it is a paper prescription. In addition, when the electronic prescription DB server 20 adds flag information indicating that the prescription data is an electronic prescription, the prescription determination unit 118 determines whether the prescription data is acquired in an electronic prescription or a paper prescription depending on whether the flag information is added. It may be determined that it is a prescription. In the example of FIG. 11, the prescription determining unit 118 determines that the prescription data acquisition mode is a paper prescription.

Next, the prescription management server 10 causes the data processing unit 115 to execute a processing process to process the acquired prescription data (A34). In the example of FIG. 11, the first determination result is the patient terminal 40, and the second determination result is a paper prescription, so the data processing unit 115 performs S13 (original document processing) shown in FIG. 8 as a processing process.

The data output unit 116 outputs the prescription data to the patient terminal 40 determined to be the output destination at A32. The patient terminal 40 displays the prescription indicated by the output prescription data on the first user display unit 411 (A71).

FIG. 15 is a diagram showing an example of displayed prescription data. A prescription image E61 and a send to pharmacy button B61 are displayed on the system screen G6 shown in FIG. 15. The prescription image E61 is an image showing the paper prescription F41 (the paper prescription shown in FIG. 12) indicated by the output prescription data. The character string F62 "original" has been processed and added to the prescription image E61. In this way, in the example of FIG. 15, prescription data on which the processing process (original document processing) of S13 shown in FIG. 8 has been executed is displayed.

When the patient confirms that the electronic prescription is to be submitted to the pharmacy based on the contents of the displayed electronic prescription, the patient operates the send to pharmacy button B61. In the example of FIG. 11, the patient terminal 40 transfers the output prescription data as is to the pharmacy terminal 50 (A72). The pharmacy terminal 50 displays the transferred prescription data on the second user display section 511 (A73). In this case, the second user display section 511 displays a prescription image E61 shown in FIG. 15. The pharmacist knows that this prescription is an original because the prescription image E61 includes the character string F62 "original".

Paper prescriptions may also be digitized at pharmacies. Management processing in that case will be explained.
FIG. 16 is an activity diagram showing another example of management processing. The activity shown in FIG. 16 is started when the pharmacist receives a paper prescription submitted by a patient and performs an operation to read the paper prescription with the pharmacy terminal 50. In the case of the pharmacy terminal 50, an operation of scanning a paper prescription with a reading device (scanner) is performed as a reading operation.

A81 (reading a paper prescription), A82 (generating scan data) by the pharmacy terminal 50, and A83 (storing paper prescription information) by the prescription management server 10 are performed in the same manner as A51, A52, and A53 shown in FIG. be exposed. Further, A91 (prescription request) by the pharmacy terminal 50 and A92 (reading of paper prescription information) by the prescription management server 10 are also performed in the same manner as A61 and A62 shown in FIG. 11. In A91, the pharmacy terminal 50 transmits request data whose output destination is its own terminal (pharmacy terminal 50).

As a result, the first determination result becomes the pharmacy terminal 50, and the second determination result becomes a paper prescription, so the data processing unit 115 performs S22 (copy processing) shown in FIG. 8 as a processing process. The data output unit 116 outputs the prescription data to the pharmacy terminal 50 determined as the output destination in A32. The pharmacy terminal 50 displays the prescription indicated by the output prescription data on the second user display unit 511 (A93).

FIG. 17 is a diagram showing an example of displayed prescription data. A prescription image E71 is displayed on the system screen G7 shown in FIG. The prescription image E71 is an image showing the paper prescription F71 indicated by the output prescription data. A character string F72 "copy" has been processed and added to the prescription image E71. In this way, in the example of FIG. 17, prescription data that has been subjected to the processing (copy processing) of S22 shown in FIG. 8 is displayed.

For example, a pharmacist may print out the displayed prescription data and paste it in a patient's medicine notebook as information indicating the history of prescribed medicines. In this case, since the character string F62 "copy" is included, it is known that the printed prescription is a copy, and it is possible to avoid mistaking it for the original.

As described above, in the prescription management system 1, the data acquisition unit 114 executes an acquisition process to acquire prescription data indicating a prescription. Further, the data processing unit 115 processes the prescription data acquired by the data acquisition unit 114 to change the display mode. Further, the data output unit 116 executes an output process of outputting the prescription data acquired by the data acquisition unit 114. The data output unit 116 outputs the prescription data in a manner depending on the acquisition manner or output destination of the prescription data.

For example, first, the terminal determination unit 117 executes a first determination process to determine whether the output destination of prescription data is a patient terminal or a pharmacy terminal. When the output destination is the patient terminal 40, the data output unit 116 outputs in the first mode, and when the output destination is the pharmacy terminal 50, it outputs in the second mode different from the first mode.

For example, when the second determination result is a paper prescription, when the first determination result is the patient terminal 40, the output is performed in a manner that shows the original (the first manner in this case), and the first determination result is When it is the pharmacy terminal 50, the output is performed in a mode showing a copy (second mode in this case). In addition, when the second determination result is an electronic prescription, when the first determination result is the patient terminal 40, output is performed in a mode showing a copy (the first mode in this case), and the first determination result is an electronic prescription. When it is the terminal 50, output is performed in a manner that shows the original (second manner in this case). In this way, by outputting prescription data in a manner according to the output destination, the prescription data can be used as an original document, increasing convenience, and in some cases, prescription data cannot be used as an original document, thereby preventing inconvenience. It is possible to suppress the use of appropriate prescription data.

Furthermore, when paper prescriptions and electronic prescriptions coexist, the true prescription is paper in the case of a paper prescription, and electronic data in the case of an electronic prescription. When you send the image data of an electronic prescription to a pharmacy like a paper prescription, or print an electronic prescription and submit it to a pharmacy like a paper prescription, the pharmacy confirms what the genuine prescription (original) is. It takes time and effort. In this embodiment, since it is possible to determine whether the prescription data is an original or a copy depending on the output mode, the effort required for such confirmation is reduced compared to a case where the output mode is uniform.

Additionally, if the same user receives medical treatment at different medical institutions, one medical institution may issue an electronic prescription. Other medical institutions may issue paper prescriptions. Even in such a case, the prescription management system 1 can manage prescription data indicating either an electronic prescription or a paper prescription.

Additionally, when different medical institutions use different apps, one app allows users to print and submit a prescription imported into the app, while another app allows users to print an electronic prescription and send it to the pharmacy first. This may cause user confusion. Therefore, by using the prescription management system 1, the output format of prescription data is determined by the same rules regardless of which medical institution issues the prescription, and by looking at the output prescription data, you can tell whether it is an original or a copy. Therefore, user confusion is suppressed.

In addition, the prescription determining unit 118 executes a second determining process for determining whether the prescription data is acquired as electronic prescription data or scanned data of a paper prescription. Then, the data output unit 116 outputs in a third mode when the prescription data indicates a paper prescription, and outputs in a fourth mode different from the third mode when the prescription data indicates an electronic prescription. In the present embodiment, when the output destination is the patient terminal 40, the data output unit 116 sets the third mode to indicate that the paper prescription indicated by the prescription data is the original, and the electronic prescription indicated by the prescription data to the patient terminal 40. Output is performed using the fourth mode, which indicates that the document is not the original.

For example, when the output destination is the patient terminal 40 and the second determination result is a paper prescription, the prescription data processed in S13 shown in FIG. If the second determination result is an electronic prescription, the prescription data processed into a form (fourth form) indicating a copy is output in S14. According to such an aspect, inappropriate use of electronic prescriptions can be suppressed while improving the convenience of paper prescriptions.

In addition, as described above, by outputting the prescription data in a manner depending on the acquisition manner or output destination of the prescription data, it is possible to convert the prescription data into data, compared to the case where the prescription data is always output in the same manner. It is possible to suppress the occurrence of problems that may occur (such as inappropriate use of electronic prescriptions). Further, by using the prescription management system 1, users (patients and pharmacists) can manage both electronic prescriptions and paper prescriptions.

Furthermore, when the output destination is the pharmacy terminal 50 and the prescription data indicates an electronic prescription, the data output unit 116 performs an output process of adding first medical information regarding the medical institution where the patient has been examined to the prescription data. Run as . For example, in the example of FIG. 8, in S23 where the first determination result is the pharmacy terminal 50 and the second determination result is an electronic prescription, the first medical information is added. The first medical information is, for example, specialized medical information E31 shown in FIG. 10. On the other hand, when the output destination is the pharmacy terminal 50 and the prescription data indicates a paper prescription, the data output unit 116 executes a process in which medical information is not added to the prescription data as an output process. For example, in the example of FIG. 8, no medical information is added in S22 where the first determination result is the pharmacy terminal 50 and the second determination result is a paper prescription.

Furthermore, when the output destination is the patient terminal 40, as well as when the output destination is the pharmacy terminal 50, when the prescription data indicates an electronic prescription, the data output unit 116 adds the first medical information to the prescription data. do. For example, in the example of FIG. 8, in S14 where the first determination result is the patient terminal 40 and the second determination result is an electronic prescription, the first medical information is added. The first medical information in this case is, for example, general medical information E21 shown in FIG. 9. On the other hand, when the output destination is the patient terminal 40 and the prescription data indicates a paper prescription, the data output unit 116 does not add medical information to the prescription data. For example, in the example of FIG. 8, no medical information is added in S13 where the first determination result is the patient terminal 40 and the second determination result is a paper prescription.

When prescription data indicating an electronic prescription is acquired, the electronic prescription DB 1 stores not only electronic prescription information but also related medical information (examination results, medical records, hospital location, doctor information, etc.) from the medical institution server 30. has been done. Therefore, the data processing unit 115 can easily add medical information. On the other hand, when prescription data indicating a paper prescription is acquired, the paper prescription DB 2 stores only electronic prescription information and no medical information. Therefore, if medical information is to be added, a new burden will be placed on the hospital or user side. Therefore, by not adding medical information when the prescription data indicates a paper prescription, it is possible to suppress an increase in the workload due to information addition, compared to the case where medical information is always added.

Further, when the output destination is the patient terminal 40, the data output unit 116 executes a process of adding third medical information regarding the medical institution where the patient received medical treatment to the prescription data as an output process. The third medical information is, for example, general medical information E21 shown in FIG. 9. On the other hand, when the output destination is the pharmacy terminal 50, the data output unit 116 executes a process of adding fourth medical information different from the third medical information to the prescription data as an output process. The fourth medical information is information regarding medical institutions. The fourth medical information is, for example, specialized medical information E31 shown in FIG. 10.

According to this aspect, patients are provided with information that they can understand without specialized knowledge, such as general medical information E21, and pharmacies are provided with information that requires specialized knowledge, such as specialized medical information E31, but are not required for dispensing or medication guidance. Provides useful information. In other words, medical information suitable for each patient and pharmacy can be provided.

<Other embodiments>

<Addition of medical information>
When the output destination is the pharmacy terminal 50 (or the patient terminal 40), the data output unit 116 may execute a process of adding medical information to the prescription data as an output process when the prescription data indicates a paper prescription. good. In that case, the data output unit 116 may add second medical information, which has a smaller amount of information than the first medical information, to the prescription data. The second medical information, like the first medical information, is information regarding the medical institution where the patient was examined.

For example, the data output unit 116 adds both dedicated medical information and general medical information as first medical information, and adds only general medical information as second medical information. Even in this case, compared to the case where medical information with the same amount of information as the first medical information is added, it is possible to suppress an increase in the workload due to information addition since it is not necessary to add dedicated medical information.

<Display schedule>
The server display unit 111 may display, for example, on the patient terminal 40 the dates when the pharmacist can provide medication guidance. Medication guidance by pharmacists includes online medication guidance and face-to-face guidance at pharmacies. Online medication guidance means that a pharmacist uses the patient terminal 40 to explain to the patient how to take medicine. Therefore, if the prescription data acquired by the data acquisition unit 114 indicates an electronic prescription, the server display unit 111 displays the first date for which online medication guidance from the pharmacy is available, and if the prescription data indicates a paper prescription , a process may be executed to display the second schedule for which face-to-face instruction at the pharmacy is possible (display step).

FIG. 18 is a diagram showing an example of a schedule in which medication guidance can be given. In FIG. 14, a system screen G8 is displayed that shows dates on which medication guidance is available. In FIG. 14(a), a schedule E81 indicating a first date for which online medication guidance is available is displayed on the system screen G8. In FIG. 14(b), the system screen G8 displays a schedule E82 indicating the second dates (dates when the pharmacy is open) for which face-to-face instruction at the pharmacy is possible. In the example of FIG. 14, the server display unit 111 displays only the schedule of one pharmacy, but it may display the schedule of two or more pharmacies.

If an electronic prescription has been issued, online medication guidance can be selected. On the other hand, if paper prescriptions are issued, face-to-face instruction at a pharmacy is required. In the case of face-to-face guidance at a pharmacy, it can only be conducted on days when the pharmacy to which the pharmacist belongs is open. On the other hand, online medication guidance can be provided regardless of whether the pharmacist's pharmacy is open or not, so there are fewer time constraints than face-to-face guidance. Therefore, if online medication guidance is available, it would be more convenient for patients to display the schedule.

According to this aspect, if online medication guidance is available, the first schedule is displayed, and if face-to-face guidance is required, the second schedule is displayed. It is possible to present a schedule more suitable for the patient than in the case of displaying the schedule. Note that, when the acquired prescription data indicates an electronic prescription, the server display unit 111 may display not only the first schedule but also the second schedule according to the patient's selection. This allows patients to receive face-to-face guidance even with electronic prescriptions if they wish.

<Display pharmacy information>
The prescription management server 10 may cause the server display unit 111 to execute a process of displaying pharmacy information on the patient terminal 40. Pharmacy information is information related to a pharmacy, and is information necessary for using a pharmacy, such as the location, contact information, and business hours of the pharmacy. If the prescription data acquired by the data acquisition unit 114 indicates an electronic prescription, the server display unit 111 executes a process of displaying pharmacy information indicating a pharmacy that can provide online medication guidance.

Further, when the prescription data acquired by the data acquisition unit 114 indicates a paper prescription, the server display unit 111 executes a process of displaying pharmacy information indicating a pharmacy that can provide face-to-face medication guidance. The server display unit 111 stores in advance pharmacy information indicating pharmacies that can provide online medication guidance and pharmacy information that indicates pharmacies that can provide face-to-face medication guidance, and displays these information according to the acquisition mode of prescription data. Display. According to this aspect, it is possible to easily find a pharmacy that can provide medication guidance.

The pharmacy information to be displayed is not limited to the above information. For example, the server display unit 111 may display pharmacy information regarding pharmacies that can deliver medicines. In that case, first, the server display unit 111 executes a process of accepting an input of the desired delivery date of the medicine via the patient terminal 40. Then, the server display unit 111 executes a process of displaying pharmacy information regarding pharmacies that can deliver medicines on the input desired delivery date.

FIG. 19 is a diagram showing an example of displayed pharmacy information. The system screen G9 shown in FIG. 19 displays an electronic prescription D91, a desired delivery date input field C91, a patient address input field C92, a display button B91, pharmacy information E91, and a contact button B92. ing. The electronic prescription D91 indicates a prescription of a patient who uses the patient terminal 40. When the display button B91 is operated with the desired delivery date entered in the input field C91 and the address entered in the input field C92, the first operation reception unit 412 of the patient terminal 40 inputs the electronic prescription D91. Request data indicating the information and a request for pharmacy information is transmitted to the prescription management server 10.

The server display unit 111 accepts the input of the desired delivery date indicated by the transmitted request data, and searches for a pharmacy that can deliver the medicine listed in the electronic prescription D91 around the address indicated by the request data. It is assumed that the server display unit 111 stores in advance information on the address of each pharmacy and the types of medicines that can be delivered. The server display unit 111 transmits pharmacy information indicating the searched pharmacy to the patient terminal 40. The pharmacy information E91 is information indicating a pharmacy that can deliver the medicine described in the electronic prescription D91, which is thus displayed. When the patient selects a pharmacy and operates the contact button B92, the contact information of the selected pharmacy is displayed and functions such as calling or emailing the pharmacy are activated. According to this aspect, it is possible to easily find a pharmacy that can deliver medicines.

Note that the server display unit 111 may perform a process of displaying pharmacy information indicating a pharmacy that can provide medication guidance and can deliver medicines on the input desired delivery date. For example, if the acquired prescription data indicates an electronic prescription, the server display unit 111 performs a process of displaying pharmacy information indicating a pharmacy that can provide online medication guidance and can deliver the medicine on the input desired delivery date. Execute. Further, if the acquired prescription data indicates a paper prescription, the server display unit 111 displays pharmacy information indicating a pharmacy that can provide face-to-face medication guidance and can deliver the medicine on the input desired delivery date. Execute processing.

In this case as well, by operating a contact button such as the contact button B92 shown in FIG. 19, the contact information of the pharmacy selected by the patient may be displayed, and functions such as calling or emailing the pharmacy may be activated. According to this aspect, it is possible to easily find a pharmacy that can provide medication guidance and that can deliver medicines.

<Format of prescription data>
The data output unit 116 may perform a transmission process of transmitting the prescription data acquired by the data acquisition unit 114 to a pharmacy terminal as an output process. In the case of an electronic prescription, since it is sent as an original, the pharmacist can hand over to the patient the medicine dispensed based on the electronic prescription indicated by the sent prescription data. In addition, in the case of a paper prescription, it is sent as a copy, but the pharmacist prepares the medication based on the paper prescription indicated by the sent prescription data and sends it to the patient who brings the original paper prescription. Medicines can be delivered.

Here, when the prescription data indicates an electronic prescription, the data output unit 116 causes the first transmission of electronic data in the first format to be performed as a transmission process, and when the prescription data indicates a paper prescription, the data output unit 116 causes the first transmission to be performed as a transmission process using electronic data in the first format. The second transmission using electronic data may be performed as a transmission process. The first format is, for example, a data format used in a system that handles electronic prescriptions, and the first transmission is transmission using a data transmission method used in the same system. On the other hand, the second format is, for example, a facsimile data format, and the second transmission is transmission using a facsimile data transmission method.

Note that other formats include text format, image format, HTML document format, encoding, and the like. Furthermore, transmission methods include email, uploading using a dedicated application program, and the like. These formats and transmission methods are examples of output modes by the data output unit 116. In either case, the data output unit 116 executes the transmission process such that the first format and the second format are different, and the first transmission and the second transmission are performed using different transmission methods.

Some pharmacies do not support electronic prescriptions and can only send prescription data by facsimile, while others support electronic prescriptions and do not have facsimile machines. Therefore, by varying the format and transmission method as described above, prescriptions can be received at more pharmacies.

<Reservation processing>
The prescription management server 10 may execute a reservation process for medication guidance.
FIG. 20 is a diagram showing the functional configuration of the control unit 11 of the prescription management server 10. The control unit 11 includes a reservation processing unit 119 in addition to the units shown in FIG. The reservation processing unit 119 executes a reservation process for medication guidance based on the prescription data acquired by the data acquisition unit 114.

It is assumed that the reservation processing unit 119 stores in advance information on the address of each pharmacy and the types of medicines for which medication guidance can be given. The reservation processing unit 119 causes the patient terminal 40 to display a reservation screen for making a reservation for medication guidance based on the acquired prescription data.
FIG. 21 is a diagram showing an example of a displayed reservation screen. The system screen G10 shown in FIG. 21 includes an electronic prescription D101 or a paper prescription F101, an input field C101 for the desired reservation date, an input field C102 for the patient's address, a display button B101, pharmacy information E101, and a reservation button. B102 is displayed.

When the display button B101 is operated with the desired reservation date entered in the input field C101 and the address entered in the input field C102, the first operation reception unit 412 of the patient terminal 40 displays the prescription data and the entered data. Request data indicating the information and a request for pharmacy information is transmitted to the prescription management server 10. The reservation processing unit 119 receives the input of the desired reservation date indicated by the transmitted request data, and searches for a pharmacy that can provide instructions on taking the medicine indicated by the prescription data.

Here, if the prescription data indicates an electronic prescription, the reservation processing unit 119 searches for a pharmacy that can provide online medication guidance or a pharmacy that can provide face-to-face guidance, and if the prescription data indicates a paper prescription, it searches for a pharmacy that can provide face-to-face guidance. Search only for pharmacies that allow this. When searching for a pharmacy that allows face-to-face guidance, the reservation processing unit 119 searches from pharmacies around the patient's address indicated by the request data. The reservation processing unit 119 causes the patient terminal 40 to display pharmacy information regarding the searched pharmacy (pharmacy information E101 in FIG. 21).

When the patient operates the reservation button B102, the reservation processing unit 119 executes reservation processing such as displaying a reservation screen of the operated pharmacy, activating a telephone function to call the reservation telephone number, or processing an online reservation. In this way, the reservation processing unit 119 executes the reservation process for face-to-face or online medication guidance when the prescription data indicates an electronic prescription, and executes the reservation process for face-to-face medication guidance when the prescription data indicates a paper prescription. Execute. As mentioned above, if an electronic prescription has been issued, online medication guidance can be selected; if a paper prescription has been issued, face-to-face guidance at a pharmacy is required. Therefore, according to the above aspect, it is possible to make a reservation for medication guidance that can utilize prescription data.

<Acquisition mode>
The acquisition mode is not limited to the above-mentioned electronic prescription or paper prescription scan data. For example, the aspect of the acquisition source may be used as the acquisition aspect, such as whether the prescription data is acquired from the patient terminal 40, the pharmacy terminal 50, the paper prescription DB 2 of the own device, or the electronic prescription DB server 20. . For example, when the output destination is the patient terminal 40 and the acquisition source is the electronic prescription DB server 20, the prescription data indicates an electronic prescription. The prescription is output in a manner that indicates that it is not the original.

Furthermore, when the output destination is the patient terminal 40 and the acquisition source is the patient terminal 40, the pharmacy terminal 50, or the paper prescription DB 2, the prescription data indicates a paper prescription. Therefore, output is performed in the third mode described above (a mode indicating that the prescription is the original). In addition, when the output destination is the pharmacy terminal 50, the data output unit 116 outputs data in the opposite mode (a third mode when the acquisition source is the electronic prescription DB server 20, and a third mode when the acquisition source is the patient terminal 40 or the pharmacy terminal 50). Sometimes output is performed in the fourth mode). In these cases as well, inappropriate use of electronic prescriptions can be suppressed while improving the convenience of paper prescriptions.

<Output mode>
The output mode of the data output unit 116 is not limited to the above-mentioned modes (original processing mode, copy processing mode, adding medical information mode, non-processing mode, and watermarking mode). For example, the data output unit 116 may be configured to process a character string, symbol, or code that is known to be an original, or may be configured to process a character string, symbol, or code that is recognized to be a copy.

Further, the data output unit 116 may vary the output mode by embedding audio data in the prescription data. The data output unit 116 changes the output mode by, for example, embedding a voice indicating that the document is an original or a voice indicating that it is a copy. In either case, it is known whether the prescription indicated by the prescription data is an original or a copy, so compared to the case where the prescription data is always output in the same format, there are problems that may occur when converting prescriptions into data (inappropriate electronic prescriptions). use) can be suppressed.

<Other configurations, etc.>
The configuration shown in FIG. 1 etc. is an example, and other aspects may be adopted as long as there are no inconveniences in implementation. For example, one device may be distributed among two or more devices, or may be replaced by a cloud computing system. Furthermore, the functions of one device may be realized by being distributed among two or more devices, or the functions of two or more devices may be realized centrally by one device. Further, the operation performed by one function may be performed by two or more functions in a distributed manner, or two or more functions may be integrated into one function. In short, as long as each necessary function is realized in the prescription management system 1 as a whole, the device that realizes those functions may have any configuration.

The output destination of information or data (hereinafter referred to as "information etc.") may be another device, a display, a storage unit (including a built-in storage unit and an external storage unit), etc. Acquisition of information etc. includes a mode of acquiring information etc. generated by the own device in addition to a mode of acquiring information etc. transmitted from another device. The table in which parameters are associated is not limited to the table shown in the figure, and the number of parameters may be decreased or increased. Furthermore, information corresponding to the parameters may be obtained using a mathematical expression, conditional expression, or the like, without using a table.

Although the aspect of the embodiment described above is an information processing system such as the prescription management system 1 that includes an information processing device such as the prescription management server 10, it may be an information processing method. The information processing method includes steps for each process executed by the information processing system. Moreover, the aspect of the embodiment described above may be a program. The program causes the computer to perform the steps of each process performed by a similar information processing system.

<Additional notes>
Furthermore, each aspect described below may be provided.

(1) A computer is caused to execute an acquisition process for acquiring prescription data, a processing process for processing the prescription data to change the display mode, and an output process for outputting the prescription data, and in the output process, , a program that outputs the prescription data in a manner according to an acquisition manner or an output destination.

According to such an aspect, it is possible to suppress the occurrence of problems that may occur due to converting prescriptions into data.

(2) The program according to (1) above causes the computer to execute a first determination process for determining whether the output destination of the prescription data is a patient terminal or a pharmacy terminal; A program that performs the output in a first mode when the destination is the patient terminal, and performs the output in a second mode different from the first mode when the output destination is the pharmacy terminal.

According to such an aspect, it is possible to suppress the use of inappropriate prescription data while increasing the convenience of the prescription data.

(3) The program according to (1) or (2) above causes the computer to execute a second determination process for determining whether the acquisition mode of the prescription data is an electronic prescription or scanned data of a paper prescription; In the output process, when the prescription data indicates a paper prescription, the output is performed in a third mode, and when the prescription data indicates an electronic prescription, the output is performed in a fourth mode different from the third mode. ,program.

According to such an aspect, the convenience of paper prescriptions can be improved and inappropriate handling of electronic prescriptions can be suppressed.

(4) In the program according to any one of (1) to (3) above, a second determination is made in the computer to determine whether the acquisition mode of the prescription data is an electronic prescription or scanned data of a paper prescription. When the process is executed and the acquired prescription data indicates an electronic prescription, the first date for which online medication guidance from the pharmacy is available is displayed, and when the prescription data indicates a paper prescription, face-to-face guidance from the pharmacy is possible. A program for executing processing for displaying a second schedule.

According to such an aspect, a more suitable schedule can be presented to the patient.

(5) In the program according to any one of (1) to (4) above, a first determination process for determining whether the output destination of the prescription data is a patient terminal or a pharmacy terminal; A second determination process is executed to determine whether the acquisition mode of the prescription data is an electronic prescription or scanned data of a paper prescription, and in the output process, when the output destination is a pharmacy terminal, the prescription data is electronic. When indicating a prescription, first medical information regarding the medical institution where the patient was examined is added to the prescription data, and when the prescription data indicates a paper prescription, no information is added to the prescription data, or the first medical information is added to the prescription data. The program adds second medical information having a smaller amount of information than the first medical information to the prescription data, the second medical information being information regarding the medical institution.

According to such an aspect, it is possible to suppress an increase in workload due to information addition.

(6) In the program described in (2) above, in the output process, when the output destination is the patient terminal, third medical information regarding the medical institution where the patient received medical treatment is added to the prescription data. , when the output destination is the pharmacy terminal, fourth medical information different from the third medical information is added to the prescription data, and the fourth medical information is information regarding the medical institution.

According to this aspect, medical information suitable for each patient and pharmacy can be provided.

(7) In the program according to any one of (1) to (6) above, a second determination is made in the computer to determine whether the acquisition mode of the prescription data is an electronic prescription or scanned data of a paper prescription. and a process of displaying pharmacy information on a patient terminal, where the pharmacy information is information related to a pharmacy, and when the acquired prescription data indicates an electronic prescription, it indicates a pharmacy that can provide online medication guidance. , If the acquired prescription data indicates a paper prescription, the program indicates a pharmacy that can provide face-to-face medication guidance.

According to this aspect, it is possible to easily find a pharmacy that can provide medication guidance.

(8) In the program according to any one of (1) to (7) above, the computer receives an input of a desired delivery date for medicines via a patient terminal, and the input desired delivery date. A program for displaying pharmacy information about pharmacies that can deliver medicines.

According to this aspect, it is possible to easily find a pharmacy that can deliver medicines.

(9) In the program according to any one of (1) to (8) above, a second determination is made in the computer to determine whether the acquisition mode of the prescription data is an electronic prescription or scanned data of a paper prescription. The output process is a transmission process for transmitting the obtained prescription data to a pharmacy terminal, and when the prescription data indicates an electronic prescription, a first transmission using electronic data in a first format is performed. is performed as the transmission process, and when the prescription data indicates a paper prescription, a second transmission using electronic data in a second format is performed as the transmission process, and the first format and the second format are different; Or, the program, wherein the first transmission and the second transmission have different transmission methods.

According to this aspect, prescriptions can be received at more pharmacies.

(10) In the program according to any one of (1) to (9) above, a second determination is made in the computer to determine whether the acquisition mode of the prescription data is an electronic prescription or scanned data of a paper prescription. and a reservation process for medication guidance based on the acquired prescription data, and when the prescription data indicates an electronic prescription, a reservation process for face-to-face or online medication guidance is executed; A program that executes a reservation process for face-to-face medication guidance when a prescription is indicated.

According to this aspect, it is possible to make a reservation for medication guidance that can utilize prescription data.

(11) The system includes an acquisition processing unit that acquires prescription data indicating a prescription, a processing unit that processes the acquired prescription data to change a display mode, and outputs the acquired prescription data. and an output processing section that performs the output in a manner according to an acquisition manner or an output destination of the prescription data.

According to such an aspect, it is possible to suppress the occurrence of problems that may occur due to converting prescriptions into data.

(12) An acquisition process in which the computer controlling the system acquires prescription data indicating a prescription, a processing process in which the acquired prescription data is processed to change the display mode, and the acquired prescription data is output. and in the output processing, the output is performed in a manner according to an acquisition manner or an output destination of the prescription data.

According to such an aspect, it is possible to suppress the occurrence of problems that may occur due to converting prescriptions into data.
Of course, this is not the case.
Furthermore, the embodiments and modifications described above may be implemented in any combination.

Finally, although various embodiments according to the present invention have been described, these are presented as examples and are not intended to limit the scope of the invention. The new embodiment can be implemented in various other forms, and various omissions, substitutions, and changes can be made without departing from the gist of the invention. The embodiments and their modifications are included within the scope and gist of the invention, as well as within the scope of the invention described in the claims and its equivalents.

1: Prescription management system 2: Communication line 10: Prescription management server 11: Control unit 20: Electronic prescription DB server 21: Control unit 30: Medical institution server 31: Control unit 40: Patient terminal 41: Control unit 50: Pharmacy terminal 51 : Control unit 100 : Information processing system 111 : Server display unit 112 : DB control unit 113 : Authentication unit 114 : Data acquisition unit 115 : Data processing unit 116 : Data output unit 117 : Terminal determination unit 118 : Prescription determination unit 119 : Reservation Processing section 211: DB control section 212: Authentication section 311: Server display section 312: DB control section 313: Authentication section 314: Business processing section 411: First user display section 412: First operation reception section 413: Image reading section 511 : Second user display section 512 : Second operation reception section 513 : Image reading section

Claims (5)

to the computer,
an acquisition process for acquiring prescription data and storing it in a database;
a request reception process for accepting an output request to output the prescription data stored in the database to a terminal;
a first determination process of determining whether the output destination of the prescription data is a patient terminal or a pharmacy terminal based on the output destination indicated by the output request received in the request reception process ;
a second determination of determining whether the acquisition mode of the prescription data stored in the database is an electronic prescription or scanned data of a paper prescription , based on information as to whether the prescription data stored in the database is an electronic prescription; processing and
a processing process of processing the prescription data stored in the database to change the display mode of the prescription indicated by the prescription data;
an output process for outputting prescription data indicating a prescription in a display mode changed by the processing process;
run the
In the processing process, the display mode is changed to a mode indicating that the prescription is the original based on the acquisition mode determined in the second determination process and the output destination determined in the first determination process ; changing the display mode to include a mode indicating that the prescription is a copy;
program. The program according to claim 1,
The prescription data includes medical information regarding a medical institution where the patient received treatment;
to the computer;
In the output processing,
If the output destination of the prescription data stored in the database is determined to be the patient terminal in the first determination process, third medical information among the medical information stored in the database is added to the prescription data. add,
If the output destination is determined to be the pharmacy terminal in the first determination process, fourth medical information different from the third medical information among the medical information stored in the database is added to the prescription data. execute the process,
program. The program according to claim 2,
to the computer;
Executes processing to display pharmacy information stored in advance on the patient terminal,
The pharmacy information includes information regarding pharmacies regarding medication guidance that can be provided,
If the acquisition mode of the acquired prescription data is determined to be an electronic prescription in the second determination process, a pharmacy that can provide online medication guidance from the pharmacy information is indicated;
If the acquisition mode of the acquired prescription data is determined to be a paper prescription in the second determination process, a pharmacy that can provide face-to-face medication guidance from the pharmacy information is indicated;
program. A system,
an acquisition processing unit that acquires prescription data and stores it in a database;
a request reception processing unit that accepts an output request to output the prescription data stored in the database to a terminal;
a first determination processing unit that determines whether the output destination of the prescription data is a patient terminal or a pharmacy terminal based on the output destination indicated by the output request received by the request reception processing unit;
a second determination of determining whether the acquisition mode of the prescription data stored in the database is an electronic prescription or scanned data of a paper prescription , based on information as to whether the prescription data stored in the database is an electronic prescription; a processing section;
a processing unit that processes the prescription data stored in the database to change the display mode of the prescription indicated by the prescription data;
an output processing unit that outputs prescription data indicating a prescription in a display mode changed by the processing unit;
Equipped with
The processing unit sets the display mode to indicate that the prescription is the original based on the acquisition mode determined by the second determination processing unit and the output destination determined by the first determination processing unit. mode , or a display mode including a mode indicating that the prescription is a copy;
system. The computer that controls the system
an acquisition process for acquiring prescription data and storing it in a database;
a request reception process for accepting an output request to output the prescription data stored in the database to a terminal;
a first determination process of determining whether the output destination of the prescription data is a patient terminal or a pharmacy terminal based on the output destination indicated by the output request received in the request reception process ;
a second determination of determining whether the acquisition mode of the prescription data stored in the database is an electronic prescription or scanned data of a paper prescription , based on information as to whether the prescription data stored in the database is an electronic prescription; processing and
a processing process of processing the prescription data stored in the database to change the display mode of the prescription indicated by the prescription data;
an output process for outputting prescription data indicating a prescription in a display mode changed by the processing process;
In the processing process, the display mode is changed to indicate that the prescription is the original based on the acquisition mode determined in the second determination process and the output destination determined in the first determination process. mode , or a display mode including a mode indicating that the prescription is a copy;
Method.