JP2007122183A - Prescription operation management system, method and program and medicine taking program running on cellular phone - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To easily register announcement mail transmission in a server which announces medicine taking, and to transmit the announcement mail of hospital visit in announcing medicine taking on a date necessary for taking medicine described in a prescription. <P>SOLUTION: This prescription operation management system is provided with an identification code preparing means for preparing an identification code for recording content to be added to a prescription; an identification code reading means for reading the prepared identification code; a mail preparing and transmitting means for preparing or adding a medicine taking schedule history DB based on information recorded in the read identification code, and for preparing and transmitting the medicine taking information mail for announcing medicine taking at the date of taking medicine based on the medicine taking schedule history DB; a mail monitor receiving and analyzing means for transmitting a mail to guide the omission of medicine taking when it is decided that the medicine is not taken within a time; and a hospital visit announcing means for transmitting the announcement mail of hospital visit when it is decided that the hospital visit is necessary from the result of medicine taking. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a prescription operation management system, method, and program for managing a prescription of a patient's prescription and the like, and a medication program operating on a mobile phone. The present invention relates to a prescription operation management system, a method and a program, and a medication program that operates on a mobile phone.

  Traditionally, prescriptions are received at dispensing pharmacies or departments in hospitals that handle drugs where they are delivered to patients. The method of taking the medicine, such as when to take the delivered medicine and how many times a day, is described in a medicine bag delivered to the patient, and the patient is taking the medicine based on the display. In addition, when the drug was delivered, the pharmacist explained the method of taking it orally. Even if the patient forgot to take it or did not take it as stated in the prescription, the hospital could not know it.

  Until now, as a technique related to administration of medication that prompts not to forget to take medication, Patent Document 1 discloses notification of medication by e-mail from a pharmacy terminal to a user terminal used by a patient. If you do not receive a reply e-mail informing you that you have taken a certain amount of time, resend the e-mail for notification of taking the above-mentioned, and if you receive a notification that you have taken it, manage the history including the time of taking it Thus, a technique for preventing a patient from forgetting to take a drug has been proposed.

Further, Patent Document 2 manages medications that must be taken at regular intervals using a medication management device connected to a network, and takes the medications to be taken at regular intervals for the patients prescribed at regular intervals. There has been proposed a technique for calling attention by sending an e-mail for prompting.
JP 2004-062513 A JP 2004-281276 A

  However, in the medicine administration management technique described in Patent Document 1, it is necessary to manually register the contents of the medicine in the prescription, and there is a high possibility of mistakes. Further, even when the patient wants to know the contents of the prescription, it is troublesome because it is necessary to log in to the medication history management server via the network once. The dose management method described in Patent Document 2 is a technique that only supports drugs that need to be taken at regular intervals, and is not compatible with other general drugs.

  The present invention has been made in view of the above-described circumstances, and by registering a notification e-mail notification that prompts for taking by simply adding a QR code to a prescription and reading the QR code, receiving the dosing result, Calculate the next dosing time based on the results and send an e-mail, and then send an e-mail when the patient's remaining amount of medicine is low to encourage a visit to the prescription operation management system, method and program on the mobile phone The purpose is to provide a taking program that works.

  In order to achieve the above object, a prescription operation management system according to the present invention is a system in which a patient terminal used by a patient and a prescription operation management server that manages the administration of medicines according to the prescription are connected via a communication network. The prescription operation management server creates an identification code creating means for creating an identification code including at least an identifier for identifying a prescription and an e-mail address, and creates an information mail related to the prescription, and mail distribution registration is performed. Email creation and transmission means for sending the information email at the registered date and time with respect to the email address, the dose information patient terminal, the identification code reading means for reading the created identification code, and the read Obtain the information recorded in the identification code and register the delivery of the information mail in the prescription management server And mail delivery registration means for performing, characterized in that a mail transmitting and receiving means for transmitting and receiving mail.

  According to the present invention, at the time of issuing a prescription, at least the prescription ID for specifying the prescription and the e-mail address of the patient can be recorded in the QR code. Since the patient's e-mail address can be acquired, registration to an e-mail delivery service that prompts the user to take medicine can be easily performed without making a manual mistake. In addition, the type of medicine and its medication information can be acquired from the prescription ID, and it is possible to provide an extremely fine service regarding medication use.

  Preferably, the mail delivery registration means has a function of transmitting the contents of the acquired identification code by mail or notifying the prescription operation management server using a predetermined method. To do.

  According to the present invention, the patient terminal registers the delivery of the mail related to the prescription in the prescription operation management server by transmitting the identification code acquired using the mail transmission function as it is or by modifying a predetermined part. be able to. In addition, because the prescription operation management server and a predetermined method can be used to activate mail distribution registration by launching a program that operates on the patient terminal, the patient can easily prescribe the medicine prescribed by the prescription. You can receive emails regarding your taking.

  Preferably, the identification code is configured to include at least one information of the type of medicine to be prescribed, the method of taking the medicine, the number of days of taking the medicine delivered by the corresponding prescription, and the next visit date.

  According to the present invention, it is possible to acquire information such as the type of medicine recorded on the prescription and the number of days taken by simply reading the identification code, and can be notified at the time of mail delivery registration, so the prescription information is acquired from the server. The trouble to do is not generated.

  Furthermore, the reception of the reply mail for the dose information mail is monitored, and if received, the mail monitoring reception analysis means for extracting the received date and time, and the extracted date and time or the reply mail was not received , A dosage schedule registration means for registering in a dosage schedule database for storing a patient's dosage schedule and history, and a hospital notice means for sending a notification email for the next visit based on the patient's medication history information It is also preferable to comprise so that.

  According to the present invention, the arrival date of reply mail and the date and time of taking it from the reply mail that arrived can be extracted, and the extracted medication date and time can be stored as a patient's medication history, and the next visit can be notified by the patient's medication history Since the notification mail can be transmitted, the doctor can continuously diagnose the patient, and the patient can be safely referred to the hospital.

  In addition, it is preferable that the reply mail is transmitted by selecting necessary information from a screen displayed by specifying and accessing a URL described in the medication information mail.

  According to the present invention, information such as the date and time required for reply mail can be guided to the URL of the WEB browsing screen that can be easily selected from the WEB browsing screen, so that the patient creates the mail from scratch. It becomes possible to register the date and time when he / she took it and easily reply to the mail. Also, by selecting the dose time, it is easier to use and less error-prone than typing with the keyboard or the number buttons on your mobile phone.

  More preferably, the mail monitoring reception analyzing means sends an e-mail indicating that forgetting to drink has occurred when a reply mail is not received within a predetermined time or when a reply mail that has not been taken is received. Configure to notify.

  According to the present invention, since it is possible to notify the patient that forgetting to drink has occurred, it is possible to prompt further arousal, and the doctor in charge can make a diagnosis taking into account forgetting to drink Become.

  Further, the prescription operation management server provides an interface for canceling the delivery of the dose information mail on the WEB browsing screen, and the dose mail delivery destination registration means designates the dose information email release interface of the WEB browse screen from the patient terminal. It is also preferable that the delivery of the dose information mail is canceled when it is done.

  According to the present invention, since the patient can cancel the medication information mail from the outside using the Internet or the like, it is possible to omit the trouble of making a phone call and manage the administration of the medicine that is easy for the patient to use. It becomes.

  More preferably, the prescription operation management server is configured to include a medicine dosage history display unit that acquires a history of past medicine dosage and creates a list thereof.

  According to the present invention, since the patient's past medication status can be known, the doctor in charge of the patient can use the list as a reference for diagnosis, and the patient can be diagnosed in more detail. Become.

  In addition, the mail monitoring reception analysis means is configured to extract the date and time of taking from the received reply mail, calculate the next time and date of taking according to the extracted time and drug information, and notify the patient by e-mail It is also preferable to do this.

  According to the present invention, depending on the drug, the next dose time can be calculated and notified according to the date and time when the patient took the drug, etc. It is possible to deal with drugs and to give patients an appropriate prescription.

  More preferably, the prescription operation management server includes a personal schedule provided with a column for registering information on whether or not a patient is present or whether or not to visit a patient, and a personal schedule that registers whether or not a patient is present or allowed to visit in the personal schedule. Registration means, and the visit notification means is configured to determine an optimal visit date for taking the medicine with reference to the personal schedule.

  According to the present invention, the optimal visit date for taking the medicine can be determined from the patient's schedule, so that the patient can be diagnosed without forgetting.

  Furthermore, it is preferable that the prescription operation management server is configured to be able to refer to or refer to and modify the personal schedule table from the outside via a communication network.

  According to the present invention, the patient can refer to the personal schedule from the outside using the Internet or write the schedule, so that the patient and the hospital can visit the next visit date based on the patient's schedule. It is possible to formulate a future diagnosis plan.

  Moreover, it is preferable that the said visit notification means is comprised so that a patient's visit reservation may be made based on the said personal schedule.

  According to the present invention, since the patient can decide the next visit date without being aware of it, the burden on the patient is reduced.

  In addition, the visit notification means creates a list of dates and time zones that can be scheduled for visits, sends them to the patient by e-mail, extracts the dates and time zones described in the reply e-mail from the patient, and It is also preferred to be configured to register in personal calendars and hospital schedules.

  According to the present invention, since the patient can easily select a date and time that is convenient for the patient and the hospital, the burden on the patient is reduced.

  In addition, the prescription management server calculates the average amount of drugs required for a new prescription, the amount of drugs held by the patient, and the amount of drugs stored in the hospital or pharmacy, thereby calculating the amount of drugs. It is also preferable to provide a medicine inventory management means for performing the ordering process.

  According to the present invention, since it is possible to perform inventory management of medicines including the remaining amount of patients who are already taking, more accurate inventory management can be performed, and lack of medicines and excess medicines can be prevented.

  In order to achieve the above object, a medication notification program that operates on a mobile phone according to the present invention is a program related to taking a medicine that operates on a mobile phone, and stores the information when the medication information mail is received. In addition, the notification processing for taking a warning at the scheduled date and time and the forget-to-drink notification processing for giving a warning about forgetting to drink when a predetermined time elapses from the scheduled date and time are operated on the mobile phone. And

  According to the present invention, when the prescription operation management server cannot receive the medication information mail due to other factors such as its own failure, network failure, email reception failure, out of service area when the email is delivered, etc. However, as long as the power of the mobile phone is turned on, it is possible to prompt the patient to take the medicine, which increases convenience.

  In order to achieve the above object, a prescription operation management method according to the present invention includes an identification code creating step for creating an identification code including at least an identifier for identifying a prescription and an email address, and an identification for reading the created identification code. A code reading step, an information recorded in the read identification code, an email delivery registration step for performing email delivery registration, an information email relating to the prescription, and an information email delivery registration performed A mail creation and transmission step of transmitting the created information mail to the electronic mail address at a registered date and time.

  To achieve the above object, a prescription operation management program according to the present invention is a program that operates on a computer that manages a medication schedule described in a patient's prescription, and includes at least an identifier for identifying a prescription and an e-mail. An identification code creating process for creating an identification code including an address, an identification code reading process for reading the created identification code, and an email for acquiring information recorded in the read identification code and registering delivery of the email A delivery registration process, and an email creation transmission process for creating an information email related to the prescription and sending the created information email at the date and time of registration to the email address where the delivery registration of the information email has been performed Is operated on a computer.

  According to the present invention, by recording the prescription and patient information in the identification code, it becomes possible to retrieve the information simply by reading the identification code, and the information described in the prescription is input into a computer that performs processing. It is no longer necessary to perform human processing that is likely to cause mistakes. In addition, prescription information can be easily viewed on a mobile phone or the like using the Internet, and the troublesome operation of logging in to the server from the patient terminal to obtain prescription information is not necessary.

  Embodiments of the present invention will be described below. FIG. 1 shows a fixed / portable terminal that can be connected to a network by a prescription operation management server 2 constituting a prescription operation management system 1 according to the first embodiment of the present invention, a patient's personal computer, a PDA (Personal Digital Assistance), or the like. 5 shows a functional block diagram of a pharmacy terminal 3 and a mobile phone 7 connected to a network in a department that handles medicine in a hospital, a dispensing pharmacy, and the like. In FIG. 1, the prescription operation management system 1 is configured to be connected to a prescription operation management server 2, a fixed / mobile terminal 5, and a pharmacy terminal 3 via a communication network 4. Connected via a base station. In the above, the fixed / mobile terminal 5 and the mobile phone 7 are owned by the patient, and the patient can select which one to use. Alternatively, this system operation may be determined to be performed by the mobile phone 7. In the present embodiment, it is assumed that the patient communicates with the prescription operation management server 2 using the mobile phone 7.

  Here, the prescription operation management server 2 is managed and operated by a hospital that performs medical treatment for a patient, or a drug department or pharmacy of a hospital that manages drugs according to a prescription written by a doctor, or a service provider. Further, the fixed / mobile terminal 5 and the pharmacy terminal 3 are a plurality of terminals used for viewing their own schedules and the like and transmitting / receiving mails via the communication network 4. The cellular phone 7 is a cellular phone capable of browsing mail and WEB, and communicates with the prescription operation management server 2 via the cellular network 6 and further via the communication network 4 for HTTP (HyperText Transfer Protocol) communication for browsing the email and WEB. Is to do. However, the mobile network 6 uses a unique protocol.

  The prescription operation monitoring server 2 includes a transmission / reception unit 12 for transmitting / receiving data via the communication network 4, a central processing unit 13 for processing data received from the transmission / reception unit 12, and various other processes, It comprises a storage unit 14 for storing data, an input unit 15 for inputting / outputting data to / from the central processing unit 13 and a display unit 16. The input unit 15 and the display unit 16 are parts having a man-machine interface function.

  Further, the central processing unit 13 is a transmission / reception processing means (function) 131 that exchanges data with the transmission / reception unit 12, and an input / output processing means (function) 132 that exchanges data with the input unit 15 or the display unit 16. , Information registration / collection means (function) 133 for registering and collecting information such as patients and medicines received via the input / output processing means (function) 132 or the transmission / reception processing means 131, and prescription information database (DB) QR code providing means (function) 134 having a function of converting the content of the prescription into a QR code with reference to 153 and giving the content, and a function of extracting the content stored in the QR code, a prescription information database (DB) 153 or From the information extracted by the QR code assigning means 134 from the QR code assigned to the prescription and printed, the corresponding prescription Medication mail creation / transmission means (function) 135 having a function of creating and transmitting an email containing information on drug administration to an e-mail address or mobile phone e-mail address used on the corresponding patient's Internet The mail monitoring reception analyzing means (function) 136 having a function of monitoring the arrival of a reply to the mail concerning the taking of the transmitted medicine and analyzing the information such as whether or not the patient has taken from the reply mail when it arrives. Visit notification means (function) 137 having the function of investigating and determining the scheduled visit date of the corresponding patient based on the accumulation of information such as whether or not the reply mail has been taken, the drug delivered by the patient by the prescription The dosage schedule history registration for registering the dosage schedule and the history indicating the result in the dosage schedule history database (DB) 154 Means (function) 138, and a dose-mail delivery destination registration means (function) 139 for registering the email address of the patient for delivery arouse mail taking the date and time of taking the drug. In this embodiment, a QR code is used as an identification code for identifying a prescription and an e-mail address.

  The storage unit 14 also stores a patient information database (DB) 151 that stores patient-specific information such as the patient's address, name, telephone number, and mail address, the drug name of the drug described in the prescription, and the dose of the drug Drug information database (DB) 152 for storing the method of the prescription information database (DB) 153 for storing the QR code, the content of the prescription, etc. It consists of a dosing schedule history database (DB) 154 that stores a dosing schedule for each patient and a dosing history as a dosing result.

  Similarly, the fixed / mobile terminal 5, the pharmacy terminal 3, and the mobile phone 7 are respectively connected via the communication network 4, and in the case of the mobile phone 7, a transmission / reception unit 52 for transmitting and receiving data via the mobile network 6, 32, 72, central processing units 53, 33, 73 for processing data from the transmitting / receiving units 52, 32, 72, and an input unit 55 for inputting / outputting data to / from the central processing units 53, 33, 73. , 35, 75 and display units 56, 36, 76.

  Further, the fixed / mobile terminal 5 and the mobile phone 7 have mail receiving means 57 and 77 for receiving mail from the prescription operation management server 2, respectively. Further, the mobile phone 7 records a medication notification process 78 for giving a warning at a scheduled dosing date and time, a forgetting to drink notification process 79 for giving a forgetting to drink when a predetermined time has elapsed from the scheduled dosing date and time, and recorded in the prescription. QR code reading means 80 for reading the contents of the QR code, and mail delivery registration means 81 for performing registration for the mail delivery performed by the prescription operation management server 2 when the time of taking is reached. Further, the pharmacy terminal 3 includes a QR code reading unit 37 for reading the QR code recorded in the prescription, and an e-mail distribution registration unit 38 for performing registration for e-mail distribution performed by the prescription operation management server 2 when the time of taking is reached. Have. However, in this embodiment, it is assumed that QR code reading and mail delivery registration are performed by the fixed / mobile terminal 5 or the mobile phone 7 which is a patient terminal.

  The communication network 4 connects the prescription operation management server 2, the fixed / mobile terminal 5, the pharmacy terminal 3, and the mobile network 6 by using a dedicated communication network or a predetermined communication protocol for a line borrowed from a communication carrier. It is a communication network. For example, it is possible to use lines such as ADSL (Asymmetric Digital Subscriber Line), FTTH (Fiber To The Home), CATV (Community Antenna TeleVision), and wide area LAN (Local Area Network). The mobile network 6 is a network provided by a mobile communication carrier, and can send and receive e-mails, browse the web on the Internet, and the like via the communication network 4.

  FIG. 2 shows an outline of the operation of the prescription operation management system 1 in the present embodiment. The outline of the operation will be described below with reference to the sequence chart shown in FIG. The prescription is created for the patient by the doctor when the patient is diagnosed or treated at the hospital (S21a). It is desirable to create this electronically using a personal computer or the like. An ID is assigned to the created prescription. For the created prescription, a QR code in which a predetermined description item of the prescription is recorded is created, added to the prescription, and recorded. For example, printing is performed by a QR code compatible printer (S22a). The doctor hands over the prescription on which the QR code is printed to the patient (S23a).

  The patient who received the prescription from the doctor in charge or the nurse in charge (S21b) obtains the QR code recording contents recorded in the prescription using the QR code reading means 80 of the fixed / mobile terminal 5 or the mobile phone 7. (S22b). Next, the mail distribution registration means 81 requests mail distribution registration to the prescription operation management server 2 using at least the prescription ID and the e-mail address from the acquired contents (S23b). Alternatively, when a prescription is received from a patient using a terminal installed in the pharmacy, the QR code reading means 37 in the pharmacy terminal 3 reads the QR code, and the mail delivery registration means 38 makes a mail delivery request. It is also possible to configure. Similarly, when a prescription is received from a patient using a terminal installed in a hospital, the QR code is read by the QR code reading means 140 and mail delivery registration means is requested by the mail delivery registration means (not shown). Is also possible.

  Here, although not shown in the drawings, registration of delivery of notifications prompting taking by e-mail is registered for delivery to patients who do not wish to deliver, e-mail addresses, patients who do not have mobile phone 7, etc. At the stage of pre-preparing so as not to perform the process, work such as blanking the e-mail address part in the QR code is performed.

  The prescription operation management server 2 that has received the mail delivery request extracts from the prescription ID received from the prescription information DB 153 such as the type of medicine taken by the patient and the number of days delivered, and the information is already stored in the patient's taking schedule history DB 154. If it exists, add it, and if it does not, create a new one and insert the scheduled medication date and time. (S24a).

  Next, a process of searching for a medication schedule in the created schedule history DB 154 and sending an email at a specified time so that a medication information email is automatically sent to the email address extracted from the QR code as scheduled. And a dosing information mail is transmitted on time (S25a). The patient who has received the dose information mail (S24b) may return whether or not the dose has been taken or may not return the email (S25b). When the reply is made (S26b), the reply mail is received (S26a). The prescription operation management server 2 investigates the contents of the reply mail and extracts whether or not the medicine has been taken and the date and time when the medicine was taken (S27a).

  When taking the medicine, the date and time when the corresponding medicine was taken is written in the scheduled dosage history DB 154 (S28a). If it is not taken or is not shown in this drawing, but a reply mail is not received even after a predetermined time has passed, a notice of forgetting to drink is transmitted (S29a). When the patient does not take the medicine or does not send a reply mail, the patient receives a notice mail about forgetting to drink (S27b). Next, it is determined whether or not it is necessary to visit (S2Aa). If there is a need to visit, a notification mail for the visit is created and immediately transmitted (S2Ba). The patient receives an email notification about the visit (S28b). It is determined whether or not the process is completed with all the prescription information possessed by the patient (S2Ca). If the medicine is still being taken, the process returns to step S25a until the above process is finished. repeat.

  FIG. 3 shows a data configuration example of the patient information DB 151 that stores patient information. The patient information DB 151 includes a patient name, a patient address, a phone number including a mobile phone number, an e-mail address including a mobile e-mail address, and a prescription indicating information on a prescription related to a drug that the patient is currently taking. A pointer, a pointer to the patient's scheduled medication history DB 154, a scheduled visit date, and the like are stored, and the prescription pointer for the prescription ID of the prescription medicine and one or more medications currently being taken The medication ID of the medication is stored.

  FIG. 4 shows a data configuration example of the drug information DB 152 related to the drug taken by the patient. The drug information DB 152 stores the drug name and the method of taking it as information for each drug ID. As a method of taking, for example, taking every 8 hours every day, taking 3 times a day after every meal, taking once only before breakfast, and the like.

  FIG. 5 is a data configuration example of a prescription information DB 153 that stores prescription information in which information on medicines that a patient takes is described. The prescription is managed for each ID, and a QR code ID is stored for each ID. The contents of the prescription in this embodiment are recorded the patient name, the patient's mobile mail address, the drug name, the period of taking the medicine, the next visit date, etc. The above contents are also given to the QR code to be given included. In other words, the above-mentioned contents can be found only by reading the QR code assigned to the prescription and recorded.

  FIG. 6 shows an example of the data structure of the dosing schedule history DB 154 that stores the scheduled date and time of taking the drug and the history of whether or not the drug was taken at the scheduled date and time. The patient ID that identifies the patient is linked to the drug ID and drug name of the drug that the patient is currently taking, and the scheduled time and result of the drug are saved for each day. Yes. In the present embodiment, a prescription is created in the dosing schedule history DB 154, the contents are read out with a QR code, and a new prescription is added or added when a mail delivery requesting a dose is requested. It may be configured to be created at the time when is created.

  The prescription operation management system 1 in the first embodiment is configured as described above, and the operation thereof will be described below using a flowchart and the like.

[1. Registration of information]
FIG. 7 is a flowchart showing a processing procedure of an operation for registering information used in the prescription operation management server 2. Patient information, which is information related to a patient, drug information related to a drug, and prescription information related to a prescription are directly registered using a keyboard and a screen connected to the input unit 15 and the display unit 16 of the prescription operation management server 2 in advance. This operation is performed by the information registration / collection means 133.

  An operator such as a system administrator inputs using the keyboard, the input unit 15 notifies the central processing unit 13 of the input, inputs the ID and password, and logs in to the system. Then, registration of medicine and prescription information is requested using a screen and a keyboard (S71b). Receiving the request (S71a), the information registration / collection means 133 creates an input screen for patient, medicine, and prescription information and displays it on the screen handled by the operator through the display unit 16 (S72a).

  The operator inputs information on the patient, medicine, and prescription using the keyboard while viewing the screen (S72b). The input information is notified to the information registration / collection means 133 via the input unit 15 (S73b). The information registration / collection means 133 registers the inputted patient information, medicine information, and prescription information in the patient information DB 151, medicine information DB 152, and prescription information DB 153, respectively (S74a). Next, the information registration / collection means 133 determines whether all necessary information has been registered (S75a), and if not registered, returns to step S72a and repeats the process until the registration of all information is completed. When the registration process of all information is completed (yes route in S75a), the registration completion is notified by outputting it on the screen (S76a), and the operator views the registration completion screen displayed on the screen (S74b). It turns out that the registration is complete.

[2. QR code assignment]
When a prescription is created, a QR code is created and printed by a printer and recorded on the prescription. The processing procedure of the operation will be described with reference to the flowchart of FIG. This operation is performed by the QR code providing unit 134.

  First, a QR code ID is assigned to the input prescription ID in descending order, ascending order, or other methods (S81). The contents recorded in the QR code are acquired from the inputted prescription ID (S82). The contents include a prescription ID, a patient name, a drug name, a drug taking period (for several days), a next visit date, a mail address of the patient's mobile phone 7, and the like. The mail address of the mobile phone 7 may be a normal Internet mail address of the patient. From the acquired contents, the prescription ID, the e-mail address of the patient and other predetermined information are recorded as QR codes and recorded in the prescription (S83).

[3. QR code reading]
The prescription given to the patient is submitted to the in-hospital pharmacy department or an external dispensing pharmacy, and the drug to be taken is purchased. Reading the QR code will be described with reference to a flowchart showing the processing procedure of the operation shown in FIG. This operation is performed by the QR code reading procedure 80 in the patient terminal 7. In this embodiment, the QR code is read by the patient terminal 7, but is configured to be read when a prescription is received at a terminal installed in the pharmacy or a terminal set in the pharmacy department of the hospital. You may do it. When the delivery of the medicine is performed in the hospital, it can be performed by the QR code reading means 140 in the prescription operation management server 2. Even in the case of a pharmacy terminal, the QR code reading means 37 can be used in the pharmacy terminal. In this embodiment, the prescription operation management server 2 is installed in the hospital network, but may be installed outside the hospital network.

  The patient who has received the prescription reads the QR code recorded on the prescription using a terminal such as a mobile phone 7 owned by the patient, and the prescription ID, patient name, drug name, taking period, and next visit recorded. The mail address of the cellular phone 7 is extracted (S91), and the contents are output (S92). To output is to output to a screen or to a device or software that handles the above information. For example, when the patient terminal is a portable terminal such as a PDA or the cellular phone 7, it is possible to start a program that operates using the output information as a parameter.

  Next, it is determined whether to register mail delivery (S93). For example, if the patient's e-mail address is recorded as a blank in the QR code, it is determined that mail delivery is not desired or the e-mail address is not owned.

  If the user wishes to deliver a mail for invoking medication, the mail delivery registration routine is started (S94) and the process is terminated.

[4. Mail delivery registration]
Registration of mail delivery for invoking medication is performed according to the flowchart shown in FIG. This operation is performed by the mail delivery registration unit 81 in the patient terminal 7. Alternatively, it may be performed at a terminal installed in a pharmacy or a terminal of a medicine department that accepts a prescription in a hospital. In addition, registration of an e-mail address to which mail is distributed by the prescription operation management server 2 is performed according to the left flowchart of FIG. This operation is performed by the dose mail delivery destination registration unit 139 in the prescription operation management server 2.

  First, the mail distribution registration means 81 in the patient terminal 7 requests the prescription operation management server 2 for mail distribution registration using the extracted prescription ID and the patient's e-mail address as parameters (S101b). Receiving the mail delivery registration request (S101a), the dose mail delivery destination registration unit 139 determines whether the registration is OK (S102a). If the registration is OK, the designated patient's e-mail address is registered as a mail delivery target (S103a), registration OK is transmitted (S104a), and the process is terminated.

  The mail distribution registration means 81 receives the registration OK, displays it on the screen, and ends the processing (S102b). If the registration is not OK (no route in S102a), a registration NG is transmitted (S105a) and the process is terminated. The mail delivery registration means 81 receives the registration NG, displays it on the screen, and ends the processing (S103b).

[5. Creation of taking schedule]
As described above, a schedule for taking a drug is created for each patient based on the content read from the QR code. FIG. 11 is a flowchart showing a processing procedure of an operation for creating data of a dosing schedule history DB 154 for managing a dosing schedule. This operation is performed by the dosing schedule history registration means 138. This operation works when a prescription is accepted. First, the prescription ID and the patient's e-mail address notified from the QR code reading means 37 of the hospital terminal 3 are acquired (S111). From the acquired prescription ID, the patient name, drug name, taking period, next visit date, etc. and the current date and time are acquired (S112). Alternatively, all the data described above may be recorded in the QR code. At that time, there is no need to search by prescription ID.

  Next, it is determined whether or not the data of the medication schedule history DB 154 already exists for the corresponding patient (S113), and if not, based on the contents of the patient and prescription newly extracted in the medication schedule history DB 154 corresponding to the patient. Data is created (S114). If it already exists, the extracted data is added to the data in the existing dosing history DB 154 (S115).

  Next, referring to the drug information DB 152, the method of taking the drug described in the prescription is specified (S116). According to the above-described specified method of taking, the date and time of taking the medicine and the scheduled time of taking are registered in the corresponding patient area of the dosing schedule history DB 154 (S117). Registration is performed by repeating the operation of step S117 in the dosing period (S118). Next, it is determined whether or not the processing for all the medicines described in the prescription has been completed (S119). If not, the process returns to step S116 and the above operations are completed for all the medicines. Repeat until If the processing for all drugs is completed, the processing is terminated. In this way, data on the schedule of taking medicine for the patient is created.

[6. Mail information creation and transmission]
FIG. 12 is a flowchart showing a processing procedure of an operation performed by sending a dosing information mail for informing a patient of a notice of taking a medicine at a scheduled time. The following describes transmission of a medication information mail that guides medication notifications with reference to FIG. The operation shown in FIG. 12 is an operation performed by the taking mail creating / transmitting means 135. This operation can be performed immediately after mail delivery registration is performed.

  First, referring to the already taken medication history DB 154 regarding the medication of the corresponding patient, the planned medication date and time of the patient is extracted for all medications registered in the medication schedule history DB 154 for the number of days taken. (S121). Next, a corresponding time is specified, and a dose information mail for guiding notification of taking the specified drug as shown in FIG. 18 is created (S122). In FIG. 18, the contents are displayed in a frame 181 of the screen. In the case of the mobile phone 7, the screen frame 181 is a frame of the display screen of the mobile phone 7. Next, the date and time for transmitting a “designated time mail registration routine” to be described later is designated as a parameter and started (S123). The above-described operation is performed for all registered drugs over the entire dose period (S124, S125). With this operation, it is possible to transmit a dose information mail for all the drugs when the patient receives a prescription at the scheduled date and time of all dose periods.

  The dosing information mail may be configured as shown in FIG. In this configuration, the URL (Uniform Resource Locator) of the WEB page that prompts a reply to the mail and reduces the reply work is described, and the reply shown in FIG. You can be directed to the URL screen that prompts you. When using the WEB screen shown in FIG. 22 to notify the presence / absence of taking medicine, if the medicine has been taken, “I took it” is selected, and the time is input in the frame 221 and transmitted. If the user did not take the drug, select “I could not take it” and send it in the same way.

  FIG. 13 is a flowchart showing the processing procedure of the “designated time mail registration routine”. FIG. 14 is a configuration example of a specified time mail transmission registration table for performing registration for transmitting mail at a specified time. The operation of the “designated time mail registration routine” will be described with reference to FIG. The time and the mail address of the mail to be transmitted are registered in the designated time mail transmission registration table according to the designated date and time (S131). In this embodiment, the time registration can be arbitrarily registered. However, there is a registration frame every certain time, for example, every 15 minutes, and a configuration in which registration is performed in that frame is also possible.

  FIG. 15 is a flowchart showing a processing procedure of an operation of a “designated time mail transmission routine” for sending mail at a designated time. This “designated time e-mail transmission routine” is configured so that e-mail can be transmitted at a designated time, for example, by starting at a cycle of 200 ms. With reference to FIG. 15, it will be described that a mail is transmitted at a specified time. First, it is determined with reference to the designated time mail transmission registration table shown in FIG. 14 whether there is mail to be transmitted in this cycle when it is activated (S151).

  If there is a mail to be transmitted (yes route in S152), the corresponding mail is immediately transmitted (S153), and the transmission is completed (S154). The above process is performed for all registered mails registered as mails to be transmitted in that cycle, and when all the processes are performed, the process ends (no route in S152). With this operation, the dosing information mail is transmitted at the scheduled time.

[7. Reply mail monitoring and received mail analysis]
FIG. 16 is a flowchart showing the processing procedure of the operation of “mail monitoring reception analysis routine” for monitoring the reception of reply mail and analyzing the contents of the received reply mail. This operation is performed by the mail monitoring reception analysis unit 136. The operation of receiving a reply mail and analyzing the contents of the received mail will be described below with reference to FIG.

  This “mail monitoring reception analysis routine” is started, for example, at a cycle of 200 ms, or is started by interruption processing when mail is received. It should be noted that the above-described activation cycle can be changed.

  When the “mail monitoring reception analysis routine” is started, it determines whether or not there is a received mail (S161). If there is no received mail, the process proceeds to step S165. If there is a received mail, it is determined whether the received mail is a reply mail (S162). If it is not a reply mail, the process returns to step S161 to proceed to the process for the next mail (no route in S162). If it is a reply mail, it is investigated and determined as to which dose information mail the reply mail is (S163). Next, if a reply mail has been received for the corresponding dose information mail and if it has been taken, the date and time when the dose was taken is specified from the mail (S164), and the process returns to step S161 to return to the next mail. Proceed to the process.

  Next, after the processing for all received mails is completed, it is determined whether or not a reply mail has arrived within a predetermined time (S165). This process is a process for detecting that a reply mail has not arrived. If it has not arrived, it is determined that forgetting to drink has occurred, and a forgotten drink mail as shown in FIG. 19 is created and sent immediately, and the fact that the forgotten drink mail has been sent is recorded (S166). It is determined whether the content of the received reply mail is “Not Taken” (S167). If it is “Not Taken”, it is determined that forgetting to drink has occurred and FIG. As shown, a forgotten email is created and sent immediately, and the fact that the forgotten email is sent is recorded (S168).

  Next, it is determined whether or not all reply mails have been processed (S169). If not, the next reply mail is designated (S16A) and the process returns to step S165 to repeat the above operation for all reply mails. Repeat until the process is completed. If all reply mails have been processed, the process ends (yes route in S169).

[8. Notice of Visit]
FIG. 17 is a flowchart showing a processing procedure of an operation of “visit notification routine” for sending a visit notification email for urging a patient to visit when the amount of medicine to be taken decreases or when the number of doses is low. is there. This operation is an operation performed by the visit notification means 137. In addition to the above-mentioned reasons, the visit may come from a doctor's instructions or the person's wishes. In addition, there is a case where it is not necessary to continue to take the medicine even after taking the medicine. In these cases, it is possible to cope with this by adding a step for checking that fact to the flowchart shown in FIG. Can do.

  Hereinafter, the processing procedure of the “visit notification routine” will be described with reference to FIG. This routine is started twice a day, for example, every morning and every night. First, referring to the patient's medication schedule history DB 154 (S171), it is determined whether or not there is a schedule of medication after a predetermined period from now (S172). The fact that there is no plan to take is used as a material to determine that the drug is gone because no new prescription has been received. When there is no plan to take the medicine, it is determined that the corresponding patient needs to visit (S174). Next, when there is a schedule of taking, it is further determined whether the number of times of not taking exceeds a predetermined number (S173). Patients who have not taken the medicine more than the predetermined number of times are determined to need a visit. The fact that the patient did not take many times is because he / she decides that he / she has extra medicine but has a problem with his / her way of taking the medicine and encourages the visit. Although not described in this flowchart, it may be determined that there is a problem in the way of taking even when the number of times of taking is greater than a predetermined number.

  Next, a notification email for a visit as shown in FIG. 20 is created and immediately transmitted to a patient who is determined to need a visit (S175). It is determined whether or not the processing of all patients taking the medicine has been completed (S176). If not, the next patient is designated (S177), and the process returns to step S171 to take all the medicines. The above process is repeated until the process for the patient is completed. When the process for the patient taking all the medicines is completed, the process ends (yes route in S176).

Although a flowchart showing the processing procedure is not shown, the fixed / mobile terminal 5 and the mobile phone 7 have mail receiving means 57 and 77. In the fixed / mobile terminal 5, for example, in order to receive mail, it is possible to check whether mail has arrived by accessing a predetermined mail server using POP (Post Office Protocol) or the like. In the mobile phone 7, a mail reception notice is sent from the mail server directly to the mobile phone 7.
The first embodiment of the present invention is configured and operates as described above.

  According to the present invention, it is possible to send a dose information email notifying the patient that the time for taking a dose has been reached using information related to the dose of the drug included in the QR code recorded in the prescription, Depending on the contents and when reply mail did not arrive, notification of forgetting to drink, notification of forgetting to drink can be sent, and the amount of drugs the patient is taking has decreased You can send a notification email to the hospital when you are not taking the medicine correctly, so that the patient doesn't have to worry about the time to take the medicine, It is possible to take a more detailed response to taking medicine.

  Next, a second embodiment will be described below. In the second embodiment, the patient's personal schedule is prepared for taking medicines, the appointment date can be reserved, and the medicine inventory management and order processing can be performed in different parts. is there.

  FIG. 23 shows a functional block diagram of the prescription operation management system 1 in the second embodiment of the present invention. In addition to the first embodiment, a personal schedule registration unit 141, a drug inventory management unit 142, and a medication history display unit 143 are added to the central processing unit 13. Furthermore, a personal schedule table database (DB) 155 and a drug inventory database (DB) 156 are added in the storage unit 14. The detailed contents and operation of the newly added means and database will be described below.

  FIG. 24 shows an example of the data structure of the personal schedule DB 155 that manages the schedule of the patient's individual date and time. For each patient and for each date, a time zone and a reservation column of the hospital in that time zone, and schedule contents such as “vacant”, “scheduled”, “visit” in that time zone are stored. Data registration will be described later.

FIG. 25 shows a data configuration example of the drug inventory DB 156 that manages drug inventory. The medicine stock DB 156 stores the name of the medicine, the stock status of the medicine, the scheduled arrival date, the scheduled arrival number, and the like for each medicine ID.
[9. Create personal calendar]

  Next, an operation for registering a personal schedule will be described with reference to FIG. FIG. 26 is a flowchart showing a processing procedure of an operation for registering a patient's individual schedule. This operation is performed by the personal schedule registration means 141. In the present embodiment, the personal schedule is registered using a keyboard and a screen directly connected to the prescription operation management server 2. An operator such as a system administrator first logs in to the prescription operation management server 2 while viewing the screen using the keyboard. In this case, although not shown in FIG. 26, a user ID and a password are required for security. If both the user ID and the password do not match, the user cannot log in to the prescription operation management server 2. Information input from the keyboard is notified to the central processing unit 13 via the input unit 15. The screen information is displayed on the screen via the display unit 16.

  After logging in, the operator requests creation of the patient's personal schedule while operating the screen (S261b). The prescription operation management server 2 receives the information (S261a), and the personal schedule registration means 141 creates an input screen for the personal schedule and transmits it to the screen (S262a). The personal calendar input screen is displayed on the screen (S262b), and the operator displays “vacant”, “scheduled”, “going out”, “outpatient” as shown in FIG. The schedule is input and transmitted (S263b).

  The personal schedule registration means 141 that has received the input content stores the received schedule details for each day and time of the patient in the corresponding area of the corresponding patient's personal schedule DB 155 (S264a). Next, the personal schedule table registration unit 141 outputs a screen for selecting whether to end the input (S265a). A screen for selecting whether to end the input is displayed on the screen (S264b), and the contents selected by the operator are notified to the personal schedule registration means 141 (S265b, S266a). The personal schedule table registration unit 141 determines the selection contents (S267a), and when continuing without ending, the process returns to step S262a and repeats the above processing until the end is selected. When the end is selected, the personal schedule table registration unit 141 outputs a registration completion screen for notification of registration completion (S268a), and ends the process. A registration completion screen is displayed on the screen (S266b). A personal schedule is created by such a processing procedure.

  In this embodiment, the system administrator performs a registration operation using a keyboard and screen directly connected to the prescription operation management server 2, but an interface is created so that registration can be performed, for example, on the WEB screen, By publishing the URL, it is also possible for a patient to create his own schedule using a WEB browser via the Internet using a personal computer from home. Further, it is possible to add an interface so that the mobile phone 7 designates and inputs the URL. In the case of the mobile phone 7, the mobile phone 6 is connected to the communication network 4 from the mobile network 6 via the base station and then connected to the prescription operation management server 2.

[10. Drug inventory management]
Drug inventory management will be described below with reference to FIG. FIG. 27 is a flowchart showing a processing procedure of an operation for performing medicine inventory management. This operation is performed by the medicine stock management unit 142. First, the stock amount of the corresponding medicine is acquired from the medicine stock DB 156 and is set to A (S271). Next, the number of medicines left by all patients taking the medicine is determined as B (S272). In step S272, a process of selecting a patient taking the corresponding drug from all patients and further adding the number owned by the patient with reference to the dosing schedule history DB 154 for all selected patients. Although it is performed, it is omitted and described in one frame.

  Next, the past average number of outpatients outpatients per day is obtained and set as X (S273). Next, the total number of patients taking the drug in a day is determined and set as Y (S274). Further, on the condition that the corresponding product has stock for 30 days, (A + B) / (X + Y) is calculated, and it is determined whether or not the value is 30 or less (S275). If the value is 30 or less, the ordering process for the corresponding medicine is performed (S276). If it exceeds 30, the process proceeds to step S277 without doing anything.

  In step S277, it is determined whether or not all of the medicines have been processed. If all of the medicines have not been processed, the next medicine is designated (S278), and the process returns to step S271. The process is repeated until the process ends. If the processing has been completed for all drugs, the processing is terminated (yes route in S277). By operating as described above, it is possible to automatically order medicines. Although not described in the flowchart of FIG. 27, when the inventory becomes smaller than a predetermined threshold, it is possible to notify on the screen or mail the inventory manager. .

[11. Announcement and reservation]
The notification of the visit and the reservation operation at that time will be described with reference to FIG. FIG. 28 is a flowchart showing a processing procedure of an operation of making a visit notification and a visit reservation. This operation is an operation performed by the visit notification means 137. The difference from the operation of the visit notification means 137 shown in FIG. 17 is that in step S281, a function is added in which a candidate for a visitable date and time is obtained by checking the schedule of the hospital and the patient for the visitable date and time. is there. The patient's schedule shall be checked for free time using the patient's personal schedule. Although the schedule on the hospital side is not shown, it is assumed that the schedule of the doctor in charge is known.

  In addition, when notifying the patient of the visitable date and time, the URL indicating the date and time of the visitable date as shown in FIG. Notice. When the patient clicks and specifies the URL described in the visit notice email, a web browsing screen as shown in FIG. 30 is displayed, and the visitable date and time can be viewed on the web. Reservations can be made by selecting a date and time convenient for the patient and pressing the send button. It is possible.

[12. Display of medication history]
Next, an operation of displaying a patient's medication history will be described with reference to FIG. FIG. 31 is a flowchart showing a processing procedure of an operation for displaying a medication-specific medication status corresponding to a patient. This operation is an operation performed by the medicine taking history display unit 143. The medication history of the medication that the patient has taken for a patient is extracted by searching the medication schedule history DB 154 to create a list (S311). It is determined whether the survey has been completed for all drugs taken by the patient (S312). If not completed, the next drug is designated (S313), and the process returns to step S311 for all drugs taken by the patient. Repeat the above process.

Next, a list of all the taking statuses related to the patient's medicine as shown in FIG. 32 is displayed, and the process ends. This process is a process for one patient, but it is also possible to find attributes specific to a patient or a drug by creating a list of a plurality of patients' taking statuses.
The second embodiment of the present invention is configured and operates as described above.

  According to the present invention, it is possible to make a reservation for a visit by creating and managing a patient's personal schedule, and by providing the drug inventory management means 142, the consumption of the patient being taken is also taken into account. Inventory management and drug orders can be made at the appropriate time. Further, since the patient's medication history can be easily known as a list over the past, the doctor in charge can use the information to provide services such as finely detailed diagnosis to the patient. In addition, since it is possible to automatically manage the ordering of medicines, which has been done manually, it is possible to set at least the normal use state by setting so that there is no shortage of medicine or excessive stock of medicines. It becomes possible to prevent the occurrence of drug shortage and excess inventory.

  Next, a third embodiment will be described below. In the third embodiment, when receiving a medication information mail for guiding medication taking transmitted from the prescription management server 2, the received mobile phone 7 stores the content of the medication, and the medication date and time However, it is different in that it has a function of automatically notifying the prescription operation management server 2 of the medication result.

  FIG. 33 is a flowchart showing a processing procedure of an operation of the mobile phone 7 for taking notification of taking and forgetting to drink. This operation is performed by the dosing notification process 78 and the forget-to-drink notification process 79 in the mobile phone 7. In this embodiment, they are mixed in one flowchart, but separate operations can be performed. The prescription operation management server 2 creates a taking date mail and notifies the mobile phone 7 of it. Unlike the medication information email sent by the prescription operation management server 2 in the first embodiment at the date and time of taking, the medication date and time email in the third embodiment accepts a prescription and receives information about medication from the QR code. This is an email that, when extracted, sends the contents such as the date and time of taking it as it is.

  When the prescription operation management server 2 extracts information such as the medication date and time related to taking the medicine from the QR code, the medication date and time email is sent to the mobile phone 7 by email (S331a). The mobile phone 7 that has received the dosing date / time mail (S331b) displays the received message on the screen, and stores the information related to the date and time of taking in the storage unit 74 in the mobile phone 7 (S332b).

  It is determined whether or not it is time to take the medicine (S333b), and when it is time to take the medicine, the mobile phone 7 takes the medicine to the patient using means such as sound, vibration, lamp lighting, and message display. Prompt (S334b). Further, a screen for inputting the result of taking the medicine is displayed (S335b), and the patient inputs the result to transmit the result of taking to the prescription operation management server 2 (S336b). Is received (S332a). Next, it is determined whether or not the next dose is scheduled to be taken (S339b). If there is no next dose, the process is terminated. If there is (S336b no route), the process returns to step S333b as long as there is a dose. Repeat the operation.

  If it is not the time of taking, it is determined whether forgetting to drink has occurred (S337b). If it occurs, the patient is notified of forgetting to drink using at least one means such as sound, vibration, lamp lighting, and message display (S338b). If there is no forgetting to drink, the process proceeds to step S339b.

In the present embodiment, it becomes possible by registering a program in a language such as Java (registered trademark) or Brew (Binary Runtime Environment for Wireles) on the mobile phone 7 side and starting the program on the mobile phone 7. . Since the mobile phone 7 has individual identification information that uniquely identifies the mobile phone 7, the information can be used as authentication information to access the prescription operation management server 2.
The third embodiment of the present invention is configured and operates as described above.

  According to the present embodiment, since the prescription operation management server 2 may immediately send a mail related to taking, the prescription operation management server 2 may not have a function of sending an email at a specified time. If there are a large number of patients subscribed to this service, there is a possibility that the processing performed by the prescription management server 2 will be delayed. It makes it possible to handle patients.

  In addition, it is possible to manage the notification of forgetting to drink and the notification of the visit on the mobile phone 7 side. Furthermore, although not shown in the drawing, it communicates with the prescription management server 2 when necessary, and the patient can receive information provided by the hospital with medical data desired by the patient such as prescription information. Since the hospital side can also check the position information of the patient, it is possible to further add functions using these pieces of information.

  In the first and second embodiments, the dose information mail must arrive at the exact date of the dose in order to prompt the patient. Although it is possible that a mail server failure, a mobile network 6 failure, or a patient is out of service area, the medication information email may not arrive, but in this embodiment it is possible to notify in advance by email. As long as the mobile phone is turned on, the patient can be informed of the date and time of taking, so that the patient can be notified of the taking more stably, and a service that can be relieved by the patient can be provided.

  Although the mobile phone 7 is used in the third embodiment, it can also be performed by a PDA (Personal Digital Assistance).

It is a functional block diagram of a prescription operation management system concerning a 1st embodiment of the present invention. It is a figure which shows the operation | movement outline | summary of the prescription operation management system concerning the 1st Embodiment of this invention. It is a data structural example of patient information DB of FIG. It is a data structural example of the chemical | medical agent information DB of FIG. It is a data structural example of prescription information DB of FIG. It is a data structural example of the dosing schedule log | history DB of FIG. It is a flowchart which shows the process sequence which the information registration collection means of FIG. 1 performs. It is a flowchart which shows the process sequence which the QR code provision means of FIG. 1 performs. It is a flowchart which shows the process sequence which the QR code reading means of FIG. 1 performs. It is a flowchart which shows the process sequence which a taking mail delivery destination registration means of FIG. 1 performs. It is a flowchart which shows the process sequence which the dosing schedule log | history registration means of FIG. 1 performs. It is a flowchart which shows the process sequence which the taking mail preparation transmission means of FIG. 1 performs. It is a flowchart which shows the process sequence which performs registration which transmits the mail in the 1st Embodiment of this invention at the designated time. It is a data structural example of the designated time mail transmission registration table used in the registration which transmits the mail in the 1st Embodiment of this invention at the designated time. It is a flowchart which shows the process sequence which transmits the mail in the 1st Embodiment of this invention at the designated time. It is a flowchart which shows the process sequence which the mail monitoring reception analysis means of FIG. 1 performs. It is a flowchart which shows the process sequence which the hospital notification means of FIG. 1 performs. It is an example of the screen of the dosing information mail in the 1st Embodiment of this invention. It is an example of a screen of the notification email forgetting to drink in the first embodiment of the present invention. It is an example of a screen of a visit notice mail in a 1st embodiment of the present invention. It is an example of the screen of the dosing information mail in the 1st Embodiment of this invention. It is a screen example of a reply WEB in the first embodiment of the present invention. It is a functional block diagram of the prescription operation management system concerning the 2nd Embodiment of this invention. It is a data structural example of personal schedule table DB of FIG. It is a data structural example of the chemical | medical agent stock DB of FIG. It is a flowchart which shows the process sequence which the personal schedule registration means of FIG. 23 performs. It is a flowchart which shows the process sequence which the chemical | medical agent stock management means of FIG. 23 performs. It is a flowchart which shows the process sequence which the visit notification means of FIG. 23 performs. It is an example of a screen of a visit notice mail in a 2nd embodiment of the present invention. It is an example of the WEB browsing screen in the 2nd Embodiment of this invention. It is a flowchart which shows the process sequence of the medicine taking log | history display means in the 3rd Embodiment of this invention. It is a data structural example of the medicine taking log | history in the 3rd Embodiment of this invention. It is a flowchart which shows the process sequence of the notification of taking and the notification of forgetting to drink in the 3rd Embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Prescription operation management system 2 Prescription operation management server 3 Pharmacy terminal 4 Communication network 5 Fixed / portable terminal 6 Mobile network 7 Cellular phone 12, 32, 52, 72 Transmission / reception part 13,33,53,73 Central processing part 15,35 , 55, 75 Input unit 16, 36, 56, 76 Display unit 14, 74 Storage unit 131 Transmission / reception processing unit 132 Input / output processing unit 133 Information registration collection unit 134 QR code assignment unit 135 Dosing mail creation transmission unit 136 Mail monitoring reception analysis Means 137 Visit notice means 138 Dosing history registration means 139 Dosing mail distribution destination registration means 140 37 80 QR code reading means 141 Personal schedule table registration means 142 Drug inventory management means 143 Drug dosing history display means 151 Patient information (database) DB
152 Drug Information (Database) DB
153 Prescription information (database) DB
154 Scheduled dose history (database) DB
155 Personal calendar (database) DB
156 Drug Inventory (Database) DB
38, 81 Mail delivery registration means 57, 77 Mail receiving means 78 Dosing notification process 79 Forgetting to drink notification process

Claims (17)

A system in which a patient terminal used by a patient via a communication network and a prescription operation management server that manages taking medicine according to a prescription are connected,
The prescription operation management server includes an identification code creating means for creating an identification code including at least an identifier for identifying a prescription and an email address;
Creating an information mail related to the prescription, and for the e-mail address for which e-mail delivery registration has been performed, comprises a mail creation transmitting means for transmitting the created information mail at a registered date and time,
The patient terminal includes identification code reading means for reading the created identification code,
Mail distribution registration means for acquiring information recorded in the read identification code and performing distribution registration of the information mail on the prescription operation management server;
An email sending / receiving means for sending and receiving emails;
A prescription management system characterized by having   The mail delivery registration means is a means having a function of transmitting the contents of the obtained identification code by mail or notifying the prescription operation management server using a predetermined method. The prescription operation management system according to claim 1.   The identification code includes at least one information of a type of medicine to be prescribed, a method of taking the medicine, a number of days of taking medicine delivered by a corresponding prescription, and information on a next visit date. The prescription operation management system according to 1 or 2. Monitoring the reception of a reply email to the dose information email, if received, email monitoring reception analysis means for extracting the received date and time;
A dosing schedule history registration means for registering in the dosing schedule history database for storing the dosing schedule and history of the patient that the extracted date and time or reply email was not received;
The prescription operation management according to any one of claims 1 to 3, further comprising: a visit notification means for transmitting a visit notification email for notifying a next visit based on the medication history information of the patient. system.   5. The prescription administration management according to claim 4, wherein the reply mail is transmitted by selecting necessary information from a screen displayed by specifying and accessing a URL described in the dose information mail. system.   If the mail monitoring reception analysis means does not receive a reply mail within a predetermined time or receives a reply mail that has not been taken, the mail monitoring reception analysis means notifies the mail that a forgetfulness has occurred. The prescription operation management system according to claim 4 or 5, characterized in that The prescription operation management server provides an interface for canceling the delivery of the dose information mail on the WEB browsing screen,
7. The medication mail delivery destination registration unit cancels delivery of medication information mail when a medication information email cancellation interface on the WEB browsing screen is designated from the patient terminal. Prescription management system described in 1.   8. The prescription operation management system according to any one of claims 4 to 7, wherein the prescription operation management server includes a medicine taking history display unit that acquires a history of past medicine taking and creates a list thereof. .   The mail monitoring reception analyzing means extracts the date and time of taking from the received reply mail, calculates the next dose and date according to the extracted dose date and drug information, and notifies the patient by e-mail The prescription operation management system according to any one of claims 4 to 8. The prescription operation management server has a personal schedule with a column for registering information on whether a patient is present or whether or not to visit,
A personal schedule registration means for registering the patient's location or whether or not to visit the personal schedule;
The prescription operation management system according to any one of claims 4 to 9, wherein the visit notification means determines an optimal visit date for taking a medicine with reference to the personal schedule.   The prescription operation management system according to claim 10, wherein the prescription operation management server is configured to be able to refer to or refer to and modify the personal schedule from outside via a communication network.   The prescription operation management system according to claim 10, wherein the visit notification means makes a patient visit reservation based on the personal schedule. The visit notification means creates a list of dates and time zones that can be reserved for visits and sends them to the patient by e-mail, extracts the dates and time zones described in the reply e-mail from the patient,
The prescription operation management system according to claim 10, wherein the prescription operation management system is registered in a patient's personal schedule and a hospital schedule.   The prescription operation management server calculates a drug ordering process by calculating an average daily quantity of medicines required for a new prescription, a patient's medicine holding quantity, and a hospital or pharmacy medicine inventory quantity. The prescription operation management system according to any one of claims 4 to 13, further comprising medicine inventory management means for performing the following. A program for taking medicines that runs on a mobile phone,
When the dose information email is received, the information is accumulated, and dose notification processing for giving a warning at the scheduled dose date and time,
Forgetting to drink notification process that gives a warning about forgetting to drink when a predetermined time has elapsed from the scheduled dose
Notification program for operating a mobile phone on a mobile phone An identification code creating step for creating an identification code including at least an identifier for identifying a prescription and an email address;
An identification code reading step for reading the created identification code;
A mail delivery registration step of acquiring information recorded in the read identification code and performing mail delivery registration;
Creating an information mail related to the prescription, to the e-mail address for which the registration registration of the information mail has been performed, a mail creation sending step for sending the created information mail at a registered date and time;
The prescription operation management method characterized by including. A program that runs on a computer that manages a medication schedule described in a patient's prescription,
An identification code creating process for creating an identification code including at least an identifier for identifying a prescription and an email address;
An identification code reading process for reading the created identification code;
Mail distribution registration processing for acquiring information recorded in the read identification code and performing mail distribution registration;
Creating an information mail related to the prescription, mail creation transmission processing for transmitting the created information mail at the date and time of registration for the email address for which the delivery registration of the information mail has been performed;
Is a prescription operation management program characterized by operating a computer on a computer.

Images