Consultation management system, reminder method, hospital terminal, and program

Abstract

To provide a consultation management system, a reminding method, a hospital terminal, and a program that prompt reception of consultation by a patient for whom available medical offices are expanded.SOLUTION: In a consultation management system, a control device (11) causes a storage unit to store, in association with first data for identifying a patient, second data that indicates a consultation date corresponding to the patient, third data that indicates a period up to a next round of consultation determined by a doctor, fourth data that indicates whether the patient needs to be reminded to receive consultation, and fifth data that indicates a type of reminder. The control device (11) selects and executes either an electronic mail transmission process or a postal matter printing process on the basis of the fifth data, for prompting reception of consultation by a patient for whom the fourth data indicates that a reminder is needed, and a scheduled consultation date calculated from a period to the next consultation as indicated by the third data is approaching within a prescribed number of days. The reception of consultation by a patient for whom available medical offices are expanded is promoted by the configuration stated above.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a medical consultation management system, a reminding method, a hospital terminal, and a program. [Background technology]

[0002] When a patient visits a medical institution, there are cases where the disease is not cured in one visit and a second visit is required. If the patient does not have many subjective symptoms such as pain, they tend to forget to visit the hospital again. It is desirable to encourage such patients who tend to forget to visit the hospital in some way.

[0003] Japanese Patent Application Laid-Open Publication No. 2017-130227 (Patent Document 1) discloses a hospital visit notification method and a hospital visit notification program that enable patients to remember to visit the hospital and take their medicines in accordance with their doctor's instructions. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2017-130227 Summary of the Invention [Problem to be solved by the invention]

[0005] Japanese Patent Application Laid-Open Publication No. 2017-130227 (Patent Document 1) displays a hospital visit notification on a patient's mobile device when the next visit date is predetermined, indicating that the visit date is approaching. However, unless the patient is a large, very busy hospital or a dental clinic with long consultation hours, there is little need for a strict reservation system, and many hospitals do not adopt a reservation system. Therefore, at such clinics, if a follow-up visit is necessary, the doctor will often instruct the patient on a rough estimate of when the next visit should be, such as "two weeks later."

[0006] Japanese Patent Publication No. 2017-130227 (Patent Document 1) does not mention the case where the appointment date is not strictly determined, and in such cases it cannot be used, so there is room for improvement in the hospital visit notification program.

[0007] An object of the present invention is to provide a consultation management system, a reminding method, a hospital terminal, and a program that encourage patients to visit a wider range of target clinics. [Means for solving the problem]

[0008] The present disclosure relates to a consultation management system that encourages patients to visit a doctor. The consultation management system includes a storage unit and a control device that stores, in the storage unit, second data indicating a consultation date corresponding to the patient, and third data indicating either a period until the next consultation, a next scheduled consultation date, or an appointment date determined by a doctor, in association with first data that identifies the patient. The control device executes processing to send a reminder to encourage a patient to visit a doctor when the scheduled consultation date, calculated from the period until the next consultation indicated by the third data, is approaching within a first predetermined number of days.

[0009] Preferably, the control device further stores in the storage unit fourth data indicating whether a reminder to encourage the patient to visit a doctor and fifth data indicating the type of reminder. For a patient for whom the fourth data indicates that a reminder is necessary and whose scheduled visit date calculated from the period until the next visit indicated by the third data is approaching within a first predetermined number of days, the control device selects and executes an email sending process or a mail printing process to encourage the patient to visit a doctor based on the fifth data.

[0010] More preferably, after executing the process of sending an e-mail or printing mail to encourage a patient to visit a doctor, if the patient's updated appointment date is not stored in the memory unit within a certain period of time, the control device further executes the process of sending an e-mail or printing mail to encourage a patient to visit a doctor.

[0011] Preferably, the control device stores in the memory unit sixth data identifying the medicine prescribed by the doctor, seventh data indicating the amount of medicine prescribed by the doctor, and eighth data indicating the date on which the medicine was prescribed, and the control device calculates the reference date on which the remaining amount of medicine will be zero based on the sixth data, seventh data, and eighth data, and executes an email sending process or mail printing process to encourage patients who are approaching the reference date within a second predetermined number of days to visit the hospital.

[0012] Preferably, the doctor is an ophthalmologist, and the control device receives from the patient information on the date the eye drops were opened and the date on which the eye drops were used up, stores the information in a memory unit, and, upon request from the ophthalmologist, transmits information including the period of use and amount of the eye drops to a hospital terminal located in the ophthalmologist's clinic.

[0013] Preferably, the doctor is an ophthalmologist, and the control device receives information on the date the eye drops were opened and the date the eye drops were used up from the patient and stores the information in a memory unit, and if the patient does not inform the patient of the date the eye drops were used up even after a predetermined period of time has passed since the date of opening and the expiration date, the control device sends the patient an email informing them that the eye drops have expired.

[0014] Preferably, the control device stores the second data in the storage unit each time the patient visits the hospital, and in response to a request from the doctor, the control device displays information indicating the patient's continued outpatient visit rate from the second data stored in the storage unit on a hospital terminal used by the doctor.

[0015] Preferably, the control device sends additional information to the patient other than the reminder when executing the process for sending the reminder.

[0016] In another aspect, the present disclosure relates to a reminding method using a computer to encourage a patient to visit a doctor, the reminding method including the steps of: storing second data indicating a doctor's appointment date corresponding to the patient in a storage unit in association with first data identifying the patient; storing third data indicating a period until the next doctor's appointment, a next scheduled doctor's appointment date, or an appointment date in association with the first data in the storage unit; and sending a reminder to encourage the patient to visit a doctor when the scheduled doctor's appointment date, calculated from the period until the next doctor's appointment, the next scheduled doctor's appointment date, or the appointment date indicated by the third data, is approaching within a predetermined number of days.

[0017] Preferably, the step of storing the third data in the storage unit further stores fourth data indicating whether a reminder to encourage the patient to visit a doctor and fifth data indicating a type of reminder in the storage unit. The step of sending the reminder selects, based on the fifth data, an email sending process or a mail printing process to encourage a patient to visit a doctor when the fourth data indicates that a reminder is necessary and the patient's scheduled visit date calculated from the period until the next visit indicated by the third data is approaching within a predetermined number of days.

[0018] Yet another aspect of the present disclosure relates to a medical consultation management program for causing a computer to execute the above-described reminding method.

[0019] Yet another aspect of the present disclosure relates to a hospital terminal, which includes an input unit configured to input first data identifying a patient, second data indicating a consultation date corresponding to the patient and associated with the first data, third data indicating a period until the next consultation or a scheduled next consultation date determined by a doctor, and fourth data indicating whether a reminder to encourage the patient to consult a doctor is necessary, a transmitter that transmits the first to fourth data to a consultation management system, a request unit that requests the consultation management system to output information on a hospital visit continuation rate, and a receiver that receives the information.

[0020] Yet another aspect of the present disclosure relates to a hospital terminal. The hospital terminal includes an input unit configured to input first data identifying a patient, second data associated with the first data and indicating a consultation date corresponding to the patient, third data indicating a period until the next consultation or a scheduled next consultation date determined by a doctor, and fourth data indicating whether a reminder to encourage the patient to consult is necessary; a transmission unit configured to transmit the first to fourth data to a consultation management system; a request unit requesting the consultation management system to output medication information; and a medication information receiving unit. The input unit is further configured to input sixth data indicating a medication prescribed by a doctor selected from the medication information received by the receiving unit, seventh data indicating the amount of medication prescribed by the doctor, and eighth data indicating the date the medication was prescribed. The transmission unit is further configured to transmit the sixth to eighth data to the consultation management system. The request unit further requests the consultation management system to output patient information indicating the percentage of patients who visited the hospital within a second predetermined number of days until a reference date when the remaining amount of medication calculated based on the sixth, seventh, and eighth data will become zero. The receiver is further configured to receive patient information.

[0021] Yet another aspect of the present disclosure relates to a program for causing a computer operating as a hospital terminal to execute the following processes: a process of receiving, via an input unit, first data for identifying a patient, second data indicating a consultation date corresponding to the patient and associated with the first data, third data indicating a period until the next consultation or a scheduled next consultation date determined by a doctor, and fourth data indicating whether a reminder to encourage the patient to visit the hospital is necessary; a process of transmitting the first to fourth data to the consultation management system; a process of requesting the consultation management system to output information on the rate of continued visits; and a process of receiving information.

[0022] Yet another aspect of the present disclosure relates to a program for causing a computer operating as a hospital terminal to execute the following processes: receiving, via an input unit, first data identifying a patient, second data associated with the first data and indicating a consultation date corresponding to the patient, third data indicating a period until the next consultation or a scheduled next consultation date determined by a doctor, and fourth data indicating whether a reminder to encourage the patient to consult is necessary; transmitting the first to fourth data to the consultation management system; requesting the consultation management system to output drug information; receiving the drug information; further receiving, via the input unit, sixth data indicating a drug prescribed by the doctor selected from the received drug information, seventh data indicating the amount of the drug prescribed by the doctor, and eighth data indicating the date the drug was prescribed; further transmitting the sixth to eighth data to the consultation management system; further requesting the consultation management system to output patient information indicating the percentage of patients who visited the hospital within a second predetermined number of days until a reference date when the remaining amount of drug will become zero, calculated based on the sixth, seventh, and eighth data; and receiving the patient information. [Effects of the Invention]

[0023] According to the present invention, even if the appointment date is not strictly determined, a timely reminder to encourage the patient to visit the clinic is sent in a manner desired by the patient, so that an improvement in the rate of visits can be expected. [Brief explanation of the drawings]

[0024] [Figure 1] 1 is a diagram showing an examination management system according to the first embodiment and a terminal to which the examination management system sends and receives data. FIG. [Figure 2] FIG. 2 is a diagram showing the contents of data stored in a database of a medical management system. [Figure 3] 4 is a flowchart showing the processing carried out between the medical consultation management system, the hospital terminal, and the patient in the first embodiment. [Figure 4] 10 is a flowchart for explaining the patient information accumulation and reminder sending date calculation process executed by the medical examination management system in step S202. [Figure 5]10 is a flowchart for explaining a reminder sending process executed by the medical examination management system in step S203. [Figure 6] 10 is a flowchart illustrating a process of sending another reminder. [Figure 7] 10 is a flowchart showing the processing carried out between the medical consultation management system, the hospital terminal, and the patient in the second embodiment. [Figure 8] 10 is a flowchart showing details of the process in step S202A. [Figure 9] 10 is a flowchart illustrating the process of step S208A. [Figure 10] 11 is a flowchart for explaining an information providing service added in the third embodiment. [Figure 11] FIG. 1 is a diagram showing the contents of data in which a history of multiple visits to the hospital is registered and stored in a database. [Figure 12] 11 is a flowchart showing details of the process executed in step S222 of FIG. 10. [Figure 13] 13 is a flowchart for explaining an information providing service added in the fourth embodiment. [Figure 14] 14 is a flowchart illustrating details of the process executed in step S203B of FIG. 13. [Figure 15] 10A and 10B are diagrams for explaining two modes of delivering a message from an ophthalmologist to a patient. [Figure 16] 13 is a flowchart illustrating an information collection service according to a fifth embodiment. [Figure 17] 10 is a flowchart illustrating a service for conducting a questionnaire survey for all patients. [Figure 18] 13 is a flowchart for explaining a suggestion box service as another specific example of the fifth embodiment. [Figure 19] 13 is a flowchart for explaining a service in which the medical examination management system provides drug information to patients from a drug database in the sixth embodiment. [Figure 20] 13 is a flowchart for explaining a service in which the medical examination management system notifies a patient of the time to apply eye drops in the sixth embodiment. [Figure 21] 13 is a flowchart for explaining a service in which the medical examination management system reports the time of administration of eye drops to an ophthalmologist or a family member in the seventh embodiment. [Figure 22] 13 is a flowchart for explaining a service in which the medical consultation management system reports the average amount of eye drops used to an ophthalmologist in the seventh embodiment. [Figure 23] 13 is a flowchart for explaining a service in which the medical examination management system manages the expiration date of eye drops in the eighth embodiment. [Figure 24] 13 is a flowchart for explaining a service in which the medical examination management system notifies the patient of the remaining amount of eye drops based on an image in the ninth embodiment. [Figure 25] FIG. 22 is a diagram showing a configuration using a medical examination management system according to a tenth embodiment. [Figure 26] 10 is a flowchart illustrating a service in which the consultation management system collects information on portable examination devices and provides it to ophthalmologists. [Figure 27] FIG. 22 is a diagram showing a configuration using a medical examination management system according to an eleventh embodiment. [Figure 28] 10 is a flowchart for explaining services provided to hay fever patients by the medical consultation management system. DETAILED DESCRIPTION OF THE INVENTION

[0025] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. Although several embodiments will be described below, it is intended from the beginning of the application that the configurations described in each embodiment may be appropriately combined. Note that the same or corresponding parts in the drawings are designated by the same reference numerals, and their description will not be repeated.

[0026] [Embodiment 1] FIG. 1 is a diagram showing a medical examination management system according to the first embodiment and a terminal to which the medical examination management system sends and receives data.

[0027] The medical consultation management system 1 includes a control device 11, a database 13 which is a storage unit for storing data, and a printer 12. The control device 11 is configured to include a computer. The medical consultation management system 1 is connected via a computer network 2 such as the Internet to a hospital terminal 3 installed in an ophthalmology clinic, multiple patient terminals 4 owned by multiple patients, and a management terminal 5 of a service provider that manages the medical consultation management system. Note that the connection between the computer network 2 and each terminal is not limited to a wired connection, and may be wireless via a mobile phone line, wireless LAN, or the like. There may also be multiple hospital terminals 3, and the medical consultation management system 1 may be installed in common at multiple hospitals.

[0028] A personal computer, tablet computer, etc. can be used as the hospital terminal 3. The patient terminal 4 can be a personal computer, tablet computer, smartphone, mobile phone, etc. that can receive e-mail. Note that e-mail also includes messages exchanged via short message service (short mail) that can identify the recipient by phone number, and other message application software (message app).

[0029] The medical consultation management system 1 provides computer resources as a service to doctors or patients at hospitals via a computer network 2, thereby realizing so-called cloud computing.

[0030] The consultation management system 1 has a visit management function and a reminder function. The visit management function is a function that can easily keep track of a patient's appointment date, visit status, and dropout status for ophthalmologists and others. The reminder function is a function that sends reminders on behalf of clinics to encourage patients who need to be examined to do so. In this specification, "reminder" refers to a medium for notifying patients that their appointment date is approaching, including communication media such as email and application software (apps) that display notifications on devices with functions similar to email, as well as paper media such as postcards and envelopes. In addition, a "reminder" may be an automated voice message sent to patients via telephone.

[0031] FIG. 2 is a diagram showing the contents of data stored in the database of the medical consultation management system. Referring to FIG. 2, a patient ID (IDentification) is assigned to each patient, and for each patient ID, the name, date of consultation, period until next consultation or scheduled visit date, whether a reminder is required, type of reminder, reminder sending date, contact information, disease name, prescribed product, quantity, prescription date, etc. are registered in database 13. If postcard delivery is specified as the type of reminder, the address and postal code are also registered in database 13. If short message or phone call is specified as the type of reminder, the telephone number is also registered in database 13. If medication amount management is not performed, the disease name, prescribed product, quantity, and prescription date do not need to be recorded in database 13.

[0032] 1 and 2, the consultation management system 1 includes a database 13 that functions as a storage unit, and a control device 11. The control device 11 stores in the database 13, in association with first data (patient ID) that identifies the patient, second data indicating the consultation date corresponding to the patient, third data indicating the period until the next consultation determined by the doctor, fourth data indicating whether a reminder to encourage the patient to consult a doctor is necessary, and fifth data indicating the type of reminder. For patients for whom the fourth data indicates that a reminder is necessary and whose scheduled consultation date calculated from the period until the next consultation indicated by the third data is approaching within a first predetermined number of days (for example, seven days), the control device 11 selects and executes an email sending process or a mail printing process to encourage the patient to consult a doctor based on the fifth data.

[0033] The control device 11 executes a reminding method for a computer to prompt a patient to visit a doctor. As shown in the flowcharts of FIGS. 3, 4, and 5, this reminding method includes the steps of: storing second data indicating a patient's visit date in a storage unit in association with first data identifying the patient (S2001); storing third data indicating a period until the patient's next visit determined by a doctor, fourth data indicating whether a reminder to prompt the patient to visit a doctor is necessary, and fifth data indicating the type of reminder in association with the first data (S2002); and selecting, based on the fifth data, the sending of an email or the printing of mail to prompt a patient to visit a doctor (S203) for a patient for whom the fourth data indicates a need for a reminder and whose scheduled visit date, calculated from the period until the patient's next visit indicated by the third data, is approaching within a predetermined number of days. The visit management system 1 is manufactured by installing a visit management program for causing a computer to execute this reminding method in a computer included in the control device 11.

[0034] 3 is a flowchart showing the processing carried out between the consultation management system, the hospital terminal, and the patient in embodiment 1. In steps S101 and S301, the patient visits the hospital for the first time and an initial consultation reception process is executed. In the initial consultation reception process, the patient's name, address or email address, and consultation date are registered on the hospital terminal.

[0035] For example, when a desktop personal computer is used as the hospital terminal 3, the administrative staff member handling reception processes will look at the patient's medical questionnaire and perform registration. Also, when a tablet computer is used as the hospital terminal 3, the patient may temporarily use the hospital terminal 3 and register their own name, address, etc. Also, the administrative staff member handling reception processes and the patient may operate the hospital terminal 3 together.

[0036] Next, in step S102, a process is performed to input next visit information based on the results of the patient's examination by the ophthalmologist. The next visit information may be the appointment date if a reservation system is adopted, or may be the estimated time until the next visit (e.g., one week later) determined by the ophthalmologist if a reservation system is not adopted. The ophthalmologist or hospital administrative staff inputs the next visit information into the hospital terminal. If a next visit is scheduled, the ophthalmologist or administrative staff asks the patient what they would like and inputs whether they would like a reminder, which is a notification to encourage them to visit the hospital. If the patient requests a reminder, the ophthalmologist or administrative staff asks the patient what type of reminder they would like (e.g., email or postcard), and inputs this into the hospital terminal 3. Note that email may be in another format, such as short message service (SMS), as long as it delivers a notification to the patient's terminal. The ophthalmologist or administrative staff also inputs contact data (e.g., email address or address) corresponding to the type of reminder into the hospital terminal.

[0037] Furthermore, in steps S103 and S201, the data input to the hospital terminal 3 is transmitted to the consultation management system 1 via the computer network 2. Note that the transmission of data performed in step S103 may be performed for each item of data input in each of steps S101 and S201.

[0038] In step S201, when the reception of data (hereinafter referred to as patient information data) about the patient, such as the patient's name, date of visit, email address or address, whether a reminder is required, type of reminder, etc., is completed, the visit management system 1 records the patient information data in the database 13 in step S202 and calculates the date on which the reminder will be sent based on the recorded patient information data.

[0039] Next, the consultation management system 1 executes a reminder sending process in step S203. In step S302, the patient receives the reminder by email or in writing, such as a postcard. Note that email also includes messages exchanged via short message service (short mail) and other message application software (message app), which can identify the recipient by phone number.

[0040] The processing of steps S202 and S203 performed by the medical management system 1 will be explained in detail later using a flowchart.

[0041] Next, when the patient visits the hospital for the second or subsequent time in step S305, the hospital terminal 3 performs a return visit reception process in step S105. When the patient's name or ID is entered, in step S106, the hospital terminal 3 requests the visit management system 1 to send the remaining registered information of the patient.

[0042] When the consultation management system 1 receives the transmission request in step S205, it outputs the patient's registered information to the hospital terminal 3 in step S206. If there is a change in the registered data, the data is updated at this time. The consultation date may be updated to the latest consultation date, but since it is possible that calculations such as consultation rates will be performed, it is preferable to retain past consultation dates and add the latest consultation date.

[0043] Next, in step S108, the same process as in step S102 is performed, that is, the process of inputting the next visit information based on the results of the patient's examination by the ophthalmologist. At this time, too, it is preferable to display the patient information from the previous visit on the hospital terminal in advance so that only the parts that need to be updated need to be input.

[0044] Furthermore, in steps S109 and S207, the data input to the hospital terminal 3 is transmitted to the consultation management system 1 via the computer network 2. Note that data transmission may be performed in step S108 each time updated data for one item is input.

[0045] When reception of the patient information data is completed in step S207, the medical examination management system 1 records the patient information data in the database 13 in step S208, and updates the reminder sending date based on the recorded patient information data.

[0046] Next, in step S209, the medical examination management system 1 executes a reminder sending process similar to that in step S203. In step S306, the patient receives the reminder by email or in writing, such as on a postcard.

[0047] 4 is a flowchart for explaining the patient information accumulation and reminder sending date calculation process executed by the consultation management system in step S202. Referring to FIG. 4, in step S2001, the consultation management system 1 stores the patient ID and consultation date in the database 13. Subsequently, in step S2002, the consultation management system 1 stores the period until the next consultation in the database 13. Furthermore, in step S2003, the consultation management system 1 calculates the scheduled consultation date based on the consultation date and the period until the next consultation, and in step S2004 calculates the reminder sending date based on the scheduled consultation date and stores it in the database 13. Then, in step S2005, the process returns to the main routine.

[0048] For example, in Figure 2, for a patient with patient ID 0001, the consultation date is July 1, 2018, and the ophthalmologist has specified that the next consultation will be two weeks later. In this case, the consultation management system 1 sets the scheduled consultation date to July 15, 2018, 14 days after the consultation date. However, the scheduled consultation date is merely a guideline for the visit, and it is fine for the patient to visit the hospital on a day that is convenient for them within the few days before or after the scheduled consultation date. Once the scheduled consultation date is determined in step S2003, the consultation management system 1 sets the reminder sending date in step S2004, taking this scheduled consultation date into consideration.

[0049] Specifically, let's say the allowable range for appointments is ±D days from the scheduled appointment date. Then, for patients who will receive reminders by email, the reminder date is calculated as D days before the scheduled appointment date. For patients who will receive reminders in writing, such as by postcard, the reminder date is determined to be Z days earlier than the scheduled appointment date. For example, if D=2 and Z=1, for patient ID 0001, the reminder date will be set to July 13, 2018 if sent by email, and to July 12, 2018 if sent in writing.

[0050] Note that D, which indicates the acceptable range of consultation, may be changed by the ophthalmologist in terms of the type of disease or symptoms. Furthermore, the patient may specify in advance the day or time when they wish to receive a reminder, and this may be taken into consideration when determining the date for sending the reminder in step S2004. For example, if the patient transmits in advance the time when they wish to receive a reminder to the consultation management system 1 via a computer network, the consultation management system 1 will determine the date for sending the reminder taking this time into consideration. The time when they wish to request delivery may be specified by specifying, for example, a day of the week or a time of day. Conversely, they may specify days of the week when they wish to avoid delivery.

[0051] Furthermore, the reminder sending date may be determined by installing application software on the hospital terminal 3 side, performing the above calculation process, and transmitting the reminder sending date to the consultation management system 1.

[0052] 5 is a flowchart for explaining the reminder sending process executed by the medical consultation management system in step S203. The process of this flowchart is periodically called from the main routine and executed. The process of this flowchart may be set to be executed, for example, at 3:00 PM on weekdays, or may be set to be executed three times a week, for example, at noon on Mondays, Wednesdays, and Fridays. Referring to FIG. 5, in step S2011, the medical consultation management system 1 reads data starting with the patient ID from the database 13.

[0053] Next, in step S2012, the medical management system 1 determines whether the reminder sending date recorded corresponding to the read patient ID matches the current date. If the reminder sending date matches the current date (YES in S2012), the medical management system 1 determines in step S2013 whether the type of reminder specified by the corresponding ID is email or postcard.

[0054] If the type of reminder is email, in step S2014, the medical examination management system 1 sends an email to the registered email address. On the other hand, if the type of reminder is postcard, in step S2015, the medical examination management system 1 prints a postcard using the printer 12. The printed postcards are periodically collected by the administrator of the medical examination management system 1 and sent via a post office or the like. Instead of printing postcards, the name, address, and telephone number of the patient to whom the reminder should be sent may be sent to a shipping agent, and an order for the postcard to be sent may be placed. In this case, the patient information stored in the database 13 is sent from the control device 11 via the computer network 2 to an external provider or service operator, and the external provider or service operator prints the postcards.

[0055] In this embodiment, the types of reminders are exemplified as email and mail, but they are not limited to these and other options may be used. For example, a list of patients with phone numbers who will receive reminders may be sent to a hospital staff member, who may then contact the patients by phone, or the reminders may be sent to the patients by facsimile or other means. Furthermore, reminders may be sent to patients by automated voice over the telephone.

[0056] In step S2012, if today does not match the reminder sending date, and if reminder processing is performed in either step S2014 or S2015, in step S2016, the patient management system 1 determines whether checking of all patient IDs has been completed.

[0057] If checking of all patient IDs has not yet been completed (NO in S2016), in step S2017, the medical management system 1 reads the data of the next patient ID from the database 13. Then, it repeats the processing from step S2012 onwards. On the other hand, if checking of all patient IDs has been completed (YES in S2016), the medical management system 1 proceeds to step S2018 and returns the processing to the main routine.

[0058] The above-described process makes it possible to promptly remind patients even when a definite appointment date has not been determined in advance.

[0059] Even if such a reminder is sent, it is conceivable that some patients may forget to visit the hospital, and for such patients, another reminder may be sent.

[0060] FIG. 6 is a flowchart for explaining the process of sending another reminder. The process of this flowchart (referred to as step S203A) is executed after step S203 of FIGS. 3 and 5, in which a reminder is sent, is executed. First, in step S2021, the consultation management system 1 determines whether today is the check date after the reminder was sent. The check date should preferably be a date that falls outside the allowable consultation range. For example, it can be a date that is four days after the reminder was sent.

[0061] If today is not the check date after the reminder has been sent (NO in S2021), there is no need to send another reminder, so the process proceeds to step S2024. If today is the check date after the reminder has been sent (YES in S2021), in step S2022, the consultation management system 1 determines whether the latest consultation date has been updated.

[0062] If the latest consultation date has been updated (YES in S2022), it is assumed that the next consultation has taken place on the date on which the reminder was sent. Therefore, there is no need to send another reminder, and processing proceeds to step S2024. On the other hand, if the latest consultation date has not been updated (NO in S2022), there is a need to send another reminder. In this case, the consultation management system 1 sends another reminder in step S2023, and processing returns to the main routine in step S2024.

[0063] 6, the control device 11 executes a (first) process of sending an e-mail or a process of printing mail to prompt the patient to visit a doctor, and then executes a (second) process of sending an e-mail or a process of printing mail to prompt the patient to visit a doctor if the patient's updated visit date is not stored in the database 13 within a certain period of time. Note that the control device 11 may be configured to send a third or subsequent reminder if there is no response after sending the second or subsequent reminder.

[0064] In this way, by sending further reminders at the appropriate time, the patient attendance rate can be further improved.

[0065] [Embodiment 2] In the first embodiment, the date for sending the reminder was determined based on the date of the consultation and the period until the next consultation. In the second embodiment, the date for sending the reminder is also determined by taking into consideration the amount of eye drops prescribed. For example, since the amount of prescribed eye drops used varies from patient to patient, many patients visit the hospital when they run out of the medicine. This can lead to patients running out of eye drops and being unable to administer them. In the second embodiment, reminders are sent to prevent patients from running out of eye drops.

[0066] Fig. 7 is a flowchart showing the processing carried out between the medical consultation management system, the hospital terminal, and the patient in embodiment 2. In Fig. 7, the same processes as those in Fig. 3 described above are denoted by the same reference numerals, and description thereof will not be repeated.

[0067] Steps S101 and S301 are the same as those described in FIG. 3. In step S111, a process for inputting the prescribed product is performed after the ophthalmologist examines the patient. For example, in the case of an ophthalmologist, the product name and the number of prescribed eye drops are input. When the ophthalmologist specifies the type of medicine at this time, it is preferable that the consultation management system 1 outputs the product information to the hospital terminal 3, as shown in step S211. For example, the consultation management system 1 may output a product information list screen showing the corresponding type of product name and the indications for each product from a prepared medicine database to the hospital terminal 3, and the ophthalmologist may select the product to prescribe from the displayed products.

[0068] In the case of the second embodiment, the prescription product information is input in this way, and the disease name, prescription product, quantity, prescription date, etc. are recorded in the database as shown in Fig. 2. Then, for steps S102, S103, and S201, the same processing as that described in Fig. 3 is executed.

[0069] In step S201, when the consultation management system 1 receives patient information data from the hospital terminal 3, in the second embodiment, in step S202A, the patient information data is recorded in the database 13, and the reminder sending date (1) and the reminder sending date (2) are calculated based on the recorded patient information data. Here, the reminder sending date (1) is a date calculated from the period until the next consultation instructed by the ophthalmologist, similar to the reminder sending date in the first embodiment. On the other hand, the reminder sending date (2) is a date added in the second embodiment that is determined based on the date on which a re-prescription of the drug corresponding to the prescribed amount is required.

[0070] Figure 8 is a flowchart showing the details of the processing of step S202A. In the first half of Figure 8, the reminder sending date (1) calculation processing S2030 is performed in a manner similar to that of step S202 shown in Figure 4. Specifically, in step S2031, the consultation management system 1 stores the patient ID and consultation date in the database 13. Subsequently, in step S2032, the consultation management system 1 stores the period until the next consultation in the database 13. Furthermore, in step S2033, the consultation management system 1 calculates the scheduled consultation date (1) based on the consultation date and the period until the next consultation, and in step S2034 calculates the reminder sending date (1) based on the scheduled consultation date (1) and stores it in the database 13.

[0071] The method for calculating the reminder sending date (1) is the same as the method for calculating the reminder sending date described in the first embodiment, and therefore description thereof will not be repeated here.

[0072] In the second embodiment, a reminder sending date (2) calculation process S2040 is further executed. For example, if the prescribed product is eye drops, the reminder sending date (2) is the date on which a reminder is sent to notify the patient that the amount of eye drops has fallen below a specified amount. More specifically, in step S2041, the medical management system 1 stores the name of the prescribed product, its prescribed amount, whether the product is for one eye or both eyes, and the number of times the product is to be used in the eye drops, in the database 13. The prescribed amount may be the number of bottles of eye drops prescribed and the amount filled. From this information stored in the database 13, the amount of eye drops per day and the number of days for which the prescription is given can be determined. Next, in step S2042, the medical management system 1 calculates the scheduled medical appointment date (2). For example, if the prescribed amount of eye drops is three bottles, each of which is a 10-day supply, the scheduled medical appointment date (2) is set to 30 days after the current medical appointment date (10 days x 3). However, the scheduled consultation date (2) is merely a guideline for the visit date, and there is no problem as long as the patient visits on a day that is convenient for them before the remaining amount of eye drops runs out. Once the scheduled consultation date is determined in step S2042, the consultation management system 1 sets the reminder sending date (2) to a few days before the scheduled consultation date (2) in step S2043 and stores this in the database 13. Then, in step S2050, the process returns to the main routine.

[0073] 7, when the process of step S202A is completed, a reminder sending process is executed in step S203. In this process, the process of FIG. 5 described in the first embodiment is executed for each of reminder sending date (1) and reminder sending date (2). Description of the process of FIG. 5 will not be repeated here.

[0074] When the consultation management system 1 executes the reminder sending process, in step S302A, the patient receives reminder email (1) or reminder email (2) on the patient terminal 4. Reminder email (1) is an email sent on reminder sending date (1) and notifies the patient of the date of the consultation when the ophthalmologist will conduct the examination. Reminder email (2) is an email sent on reminder sending date (2) and notifies the patient of the date of the consultation when the ophthalmologist will issue a prescription for medication. Note that instead of email, reminders may be sent by postcard.

[0075] Upon receiving the reminder, the patient visits the clinic in step S305, and the re-examination process is executed starting from the re-examination reception process in step S105, as in embodiment 1. Steps S105, S106, S107, S108, S109, S205, S206, and S207 are the same as those described in Fig. 3. Furthermore, the processes in steps S112 and S212 are the same as those in steps S111 and S211, respectively, and therefore will not be described again.

[0076] When reception of the patient information data is completed in step S207, the consultation management system 1 records the patient information data in the database 13 in step S208A, and updates the reminder sending date based on the recorded patient information data. It should be noted that the need for updating the reminder sending date (2) at this time differs depending on whether or not a new medication was prescribed at the time of consultation.

[0077] Figure 9 is a flowchart for explaining the processing of step S208A. In Figure 9, the first calculation process of reminder sending date (1) S2030 is the same as the process explained in Figure 8. Next, in step S2060, the consultation management system 1 determines whether or not a medication has been prescribed for this consultation. The consultation management system 1 determines whether or not a medication has been prescribed based on whether or not the current consultation date recorded in the database 13 is the same as the medication prescription date.

[0078] If a medication has been prescribed (YES in S2060), in step S2040, the consultation management system 1 executes the process of updating the reminder sending date (2). Specifically, based on the new prescription information, the processes of steps S2041 to S2043 described in FIG. 8 are executed again. Note that if the patient has not used up all of the eye drops on hand, the newly prescribed amount may be added to the remaining amount of eye drops to calculate the reminder sending date (2).

[0079] On the other hand, if no medication was prescribed on this visit date (YES in S2060), the visit management system 1 does not update the reminder sending date (2) in step S2061. In this case, the reminder sending date (2) set up until now is maintained.

[0080] When the processing in step S2040 or step S2061 is completed, the processing returns to the main routine in step S2062.

[0081] In the second embodiment, as shown in FIG. 2, the control device 11 stores in the database 13 sixth data (prescription product) identifying the medicine prescribed by the doctor, seventh data (quantity) indicating the amount of the medicine prescribed by the doctor, and eighth data (prescription date) indicating the date the medicine was prescribed. The seventh data may be information on both the amount of medicinal solution filled in the eye drop bottle and the number of bottles of eye drops prescribed, or it may refer to only the number of bottles of eye drops prescribed if the amount filled in the eye drop bottle is obvious from the sixth data. As shown in FIGS. 7 and 8, since the amount of eye drop per dose is usually about 30 to 50 μL, the control device 11 calculates the reference date when the remaining amount of medicine will be zero based on the sixth, seventh, and eighth data, and executes an email sending process or a mail printing process to encourage patients who are within a second predetermined number of days (e.g., seven days) of the calculated reference date to visit a doctor. If multiple types of eye drops are prescribed, the eye drop that reaches zero first may be used as the reminder reference. Alternatively, the remaining amounts of multiple types of eye drops may be managed individually, and the reference date for each new eye drop may be reset each time a new eye drop is prescribed.

[0082] The hospital terminal 3 also includes an input unit 3a, a transmission unit 3b, a request unit 3c, and a receiving unit 3d. The input unit 3a is configured to input first to eighth data. The first data is data for identifying a patient. The second data is associated with the first data and indicates a consultation date corresponding to the patient. The third data indicates a period until the next consultation or a scheduled next consultation date determined by the doctor. The fourth data indicates whether a reminder to encourage the patient to consult a doctor is necessary. The transmission unit 3b is configured to transmit the first to fourth data to the consultation management system 1. The request unit 3c is configured to request the consultation management system 1 to output drug information. The receiving unit 3d is configured to receive the drug information from the consultation management system 1. The sixth data indicates a drug prescribed by a doctor that is selected from the drug information received by the receiving unit 3d or directly entered into the hospital terminal 3. The seventh data indicates the amount of drug prescribed by the doctor. The eighth data indicates the date on which the drug was prescribed. The transmission unit 3b is configured to further transmit the sixth to eighth data to the consultation management system 1. The request unit 3c further requests the consultation management system 1 to output patient information indicating the percentage of patients who visited the consultation management system 1 within a second predetermined number of days until the reference date when the remaining amount of medicine calculated based on the sixth data, the seventh data, and the eighth data becomes zero. The receiving unit 3d is configured to further receive this patient information.

[0083] Furthermore, the hospital terminal 3 can also input data 9 to identify the number of times the medicine prescribed by the doctor is administered (instilled) per day (this could be indirect information, such as instilling the medicine before going to bed), and data 10 to identify whether the medicine prescribed by the doctor is instilled in one eye or both eyes (this could be indirect information, such as instilling the medicine in the right eye).By combining these data with the sixth to eighth data, the reference date on which the remaining amount of medicine prescribed by the doctor will be zero can be calculated more accurately.

[0084] As explained above, in the second embodiment, in addition to the reminder of the next visit date as in the first embodiment, it is possible to send a timely reminder to recommend a visit before the prescribed medication runs out. This reduces the occurrence of situations such as running out of medication when administering eye drops, and is expected to improve the effectiveness of treatment.

[0085] [Embodiment 3] In the third embodiment, information useful for management is provided to ophthalmologists and the like in combination with sending reminders as in the first or second embodiment.

[0086] FIG. 10 is a flowchart for explaining the information provision service added in the third embodiment. As shown in steps S321 to S325, each time patients A and B visit the hospital repeatedly, patient information is input from the hospital terminal 3 in step S121. The patient information includes name, address, disease name, date of visit, etc. Each time, patient information data is sent to the visit management system 1, and in step S221 the visit management system 1 accumulates the patient information in the database 13. Then, in step S222, the visit management system 1 performs data analysis processing. In the data analysis processing, the visit management system 1 calculates the visit continuation rate, reminder response rate, and number of patients based on the accumulated patient information.

[0087] Here, the outpatient continuation rate is calculated for a certain period using the Kaplan-Meier (KM) method, which is commonly used in survival analysis, etc. The outpatient continuation rate can be output from several perspectives, such as for the entire hospital, calculated by disease, or by address based on postal code data.

[0088] The reminder response rate is calculated by dividing the number of patients who visited the clinic by the number of reminders sent, and is an indicator of how many patients who received a reminder actually visited the clinic.The reminder response rate can also be analyzed by reminder medium (email, SMS, postcard, etc.) and by patient who visited the clinic.

[0089] In step S122, when a request to view the analysis data is sent from the hospital terminal 3 to the consultation management system 1, the consultation management system 1 sends to the hospital terminal 3 screen information including the requested analysis items.

[0090] 11 is a diagram showing the contents of data in which a history of multiple visits to the hospital is registered and held in a database. FIG. 12 is a flowchart showing the details of the process executed in step S222 of FIG.

[0091] 12, in step S2071, the consultation management system 1 determines whether or not there is a request to view the analysis data from the hospital terminal 3. If there is no request to view, the process exits from this flowchart in step S2076. On the other hand, if there is a request to view (YES in S2071), the consultation management system 1 inquires about the analysis period in step S2072. The analysis period may be specified, for example, as the most recent year, or the start and end dates of the period may be specified. Upon receiving the specification of the analysis period from the hospital terminal 3, the consultation management system 1 extracts data to be analyzed from the patient information data stored in the database 13, as shown in FIG. 11, in step S2073.

[0092] Then, in step S2074, the consultation management system 1 analyzes the data and calculates the outpatient continuation rate, reminder response rate, outpatient rate by disease, outpatient rate by address, number of patients, etc. Once the various data have been calculated, the consultation management system 1 sends the display data to the hospital terminal 3 in step S2075, and exits the processing of this flowchart in step S2076.

[0093] In the third embodiment, the control device 11 accumulates the second data in the database 13 every time a patient visits the hospital. Then, in response to a request from a doctor, the control device 11 displays information indicating the patient's continuation rate of hospital visits from the second data accumulated in the database 13 on the hospital terminal 3 used by the doctor.

[0094] The hospital terminal 3 includes an input unit 3a, a transmission unit 3b, a request unit 3c, and a receiving unit 3d. The input unit 3a is configured to input first to fourth data. The first data is data for identifying a patient. The second data is associated with the first data and indicates the date of an appointment corresponding to the patient. The third data indicates the period until the next appointment or the scheduled date of the next appointment determined by the doctor. The fourth data indicates whether a reminder is necessary to encourage the patient to visit the hospital. The transmission unit 3b is configured to transmit the first to fourth data to the appointment management system. The request unit 3c requests the appointment management system 1 to output information on the appointment continuation rate. The receiving unit 3d is configured to receive the information on the appointment continuation rate from the appointment management system 1.

[0095] When calculating the outpatient continuation rate, diseases that can be cured in one session are excluded. In this case, the outpatient continuation rate is calculated as the ratio of patients who discontinued their outpatient visits midway to those who did not discontinue during the analysis period. The reminder response rate is calculated as the ratio of patients who recorded their visit date within a few days before or after the scheduled visit date among patients who received a reminder during the analysis period.

[0096] In addition, by looking at the outpatient rates by disease, it is possible to grasp, for example, annual trends in illnesses. By looking at the outpatient rates by address, it is possible to consider areas where advertising billboards should be erected, for example. Furthermore, by looking at the number of patients, it is possible to plan the amount of medical equipment to be introduced.

[0097] As described above, various analytical data can be displayed on the hospital terminal 3, so the consultation management system of the third embodiment is also effective as a management analysis tool for ophthalmology clinics.

[0098] [Embodiment 4] In the fourth embodiment, the medical consultation management system 1 provides information from the hospital to the patient in combination with sending a reminder as in the first or second embodiment.

[0099] For example, the information provided to patients can include the URL (Uniform Resource Locator) of the hospital's website. Patients can find various information by visiting the hospital's website. In addition, if a hospital does not have a website, the hospital may directly include any information it wishes to communicate to patients in a reminder email or postcard.

[0100] For example, some eye clinics have designated days for surgery and do not accept general consultations on those days, but there are also cases where no surgery is scheduled. In such cases, patients may be informed that general consultations are available. Conversely, patients may be informed of days when the outpatient clinic is temporarily closed due to surgery, conferences, etc.

[0101] Fig. 13 is a flowchart for explaining an information provision service added in the fourth embodiment. In steps S101B and S301, a patient visits a hospital for the first time and an initial consultation reception process is executed. In the initial consultation reception process, the patient's name, address or email address, and consultation date are registered at the hospital terminal. In the process of step S101B, in addition to the process of step S101 described in Fig. 3, whether or not information provision from the hospital is required is also registered according to the patient's wishes.

[0102] Next, in step S102, the next consultation information is input based on the results of the patient's examination by the ophthalmologist. The next consultation information includes the appointment date or estimated time until the next consultation, whether or not a reminder is required to prompt the patient to come to the consultation, and the desired type of reminder.

[0103] Furthermore, in steps S103 and S201, the data input to the hospital terminal 3 is sent to the medical examination management system 1 via the computer network 2.

[0104] When reception of the patient information data is completed in step S201, the medical examination management system 1 records the patient information data in the database 13 in step S202, and calculates the reminder sending date based on the recorded patient information data.

[0105] Next, the medical examination management system 1 executes a reminder sending process in step S203B. The process in step S203B is basically the same as the process in step S203 in Fig. 3, but also includes a process of including the information to be provided in the reminder.

[0106] If the information to be provided is the URL of the hospital's homepage, the consultation management system 1 includes the URL of the hospital's homepage in the email or prints it on a postcard in step S203B.

[0107] Furthermore, if the information to be provided is a message from the hospital, in step S126 the ophthalmologist or the like designates or inputs the information from the hospital terminal 3 and registers it in the consultation management system 1. In this case, the consultation management system 1 includes the registered information in an e-mail or prints it on a postcard in step S203B.

[0108] In step S302, the patient receives the reminder by email or in writing, such as a postcard. By looking at the email or postcard, the patient can be informed of any messages from the hospital.

[0109] Fig. 14 is a flowchart for explaining the details of the processing executed in step S203B in Fig. 13. In the flowchart in Fig. 14, processing in steps S2081 to S2083 is added to the processing in step S203 explained in Fig. 5. Therefore, only the added parts will be explained here.

[0110] In Fig. 14, if today is the reminder sending date in step S2012, the process proceeds to step S2081. In step S2081, it is determined whether or not information provision for the corresponding ID is required. This determination is made based on the information provision requirement entered in step S101B of Fig. 13.

[0111] If information provision is required (YES in S2081), the medical examination management system 1 will send a reminder plus the information to be provided. On the other hand, if information provision is not required (NO in S2081), the medical examination management system 1 will send only a reminder. Once the reminder content is determined in step S2082 or S2083, the process proceeds to step S2013, and the same process as in Figure 5 is executed thereafter.

[0112] Note that information may be provided at times other than when a reminder is sent. FIG. 15 is a diagram illustrating two modes of delivering a message from an ophthalmologist to a patient. The first mode is delivery in the form of including information in the reminder described above. In the first mode, as shown in steps S127, S227, S327, and S328, when a consultation reminder is sent, the message from the ophthalmologist is reflected on the reminder medium and sent to the patient. The second mode is delivery to all patients, etc., at any time, and is delivered separately from the reminder. In the second mode, as shown in steps S129, S229, and S329, a message from the ophthalmologist is sent to the patient by email. For example, notifications such as temporary closure dates, scheduled consultation dates during the New Year holidays, and consultation instructions for initial treatment before the onset of hay fever season may be delivered in the second mode.

[0113] As described above, in the fourth embodiment, the control device 11 sends additional information other than the reminder to the patient when executing the process for sending the reminder. That is, since the information that the patient wants to know can be added to the reminder, it can be used for communication, etc., improving convenience. In addition, it is also possible to send information to all patients at once using a medical consultation management system configured to send reminders.

[0114] [Embodiment 5] In embodiment 4, an example of delivering information from a hospital to a patient was described, but in embodiment 5, an example of delivering information to a patient and collecting information from the patient and displaying it on a hospital terminal will be described.

[0115] 16 is a flowchart for explaining the information collection service of the fifth embodiment. In steps S101C and S301, a patient visits the hospital for the first time and an initial consultation reception process is executed. In the initial consultation reception process, the patient's name, address or email address, and consultation date are registered at the hospital terminal 3. In the process of step S101C, in addition to the process of step S101 described in FIG. 3, whether or not a questionnaire should be sent from the hospital is also registered according to the patient's wishes.

[0116] Next, in step S102, the next consultation information is input based on the results of the patient's examination by the ophthalmologist. The next consultation information includes the appointment date or estimated time until the next consultation, whether or not a reminder is required to prompt the patient to come to the consultation, and the desired type of reminder.

[0117] Furthermore, in steps S103 and S201, the data input to the hospital terminal 3 is sent to the medical consultation management system 1 via the computer network 2.

[0118] When reception of the patient information data is completed in step S201, the medical examination management system 1 records the patient information data in the database 13 in step S202, and calculates the reminder sending date based on the recorded patient information data.

[0119] Next, the medical examination management system 1 executes a reminder sending process in step S203C. The process in step S203C is basically the same as the process in step S203 in Fig. 3, but also includes a process of including the provided questionnaire information in the reminder.

[0120] If the reminder medium is email, the medical examination management system 1 includes, for example, a URL of a homepage where the questionnaire can be displayed and the answers can be entered in the email in step S203C.

[0121] If the reminder medium is a postcard, the consultation management system 1 prints, for example, a questionnaire and a response field on the postcard in step S203C. In this case, the postcard may be printed with a URL for a website where responses can be entered using a QR code (registered trademark) or the like. In this case, the patient enters their response by accessing the response entry website from a smartphone or the like. In addition, printing may be performed on a return postcard in step S203C so that the responses can be collected by return postcard.

[0122] In step S302, the patient receives a reminder by email or in writing, such as a postcard. The patient can be informed of the questionnaire by looking at the email or postcard. In step S331, the patient answers the questionnaire.

[0123] In step S231, the consultation management system 1 accumulates, analyzes, and tallys the response information. Then, in step S131, when an ophthalmologist or the like requests response information to the questionnaire from the hospital terminal 3, the consultation management system 1 sends a screen showing the tallying results of the responses to the hospital terminal 3, and in step S132 a screen showing the tallying results is displayed on the hospital terminal 3. In this way, the consultation management system 1 can be used to conduct a questionnaire about the questions that the ophthalmologist or the like wants to ask of patients to whom reminders are to be sent, and the survey results can be used to help with hospital management.

[0124] The questionnaire does not have to be limited to patients to whom reminders are sent, but may be sent to all patients or selected patients at the same time at a different time.

[0125] FIG. 17 is a flowchart for explaining a service that conducts a survey targeting all patients. In FIG. 17, in step S141, an ophthalmologist or staff member inputs survey questions from the hospital terminal 3. The survey questions may also be input from the management terminal 5. In step S241, these questions are reflected in the homepage data stored in the database 13 of the consultation management system 1. The consultation management system 1 then sends an email to patients who have registered email addresses. At this time, for the convenience of data collection, patients who should be reminded by sending a postcard may be excluded. The consultation management system 1 sends the email by including a link to the homepage where the survey is conducted.

[0126] When the patient receives the e-mail in step S341, the patient accesses the questionnaire-dedicated website of each ophthalmology department from the URL stated in the e-mail in step S342, answers the questions in the questionnaire, and submits the results.

[0127] In step S242, the consultation management system 1 accumulates the answers to the questionnaire in the database 13 and tallys up the answer data. Then, the ophthalmologist or the like can view the accumulated answers from the hospital terminal 3 in step S142.

[0128] The above explains about questionnaires, but the answers to questionnaires are limited to questions that the hospital has in mind. However, it is possible that there may be areas for improvement in areas that the hospital has not anticipated. In order to collect information on such areas for improvement, it may be possible to implement a suggestion box service within the consultation management system, where patients can freely enter any concerns they may have.

[0129] Fig. 18 is a flowchart for explaining a suggestion box service as another specific example of embodiment 5. In Fig. 18, in step S146, it is possible to select whether the suggestion box service is applied to a patient at the time of their first visit or at a follow-up visit.

[0130] In step S246, for patients for whom the suggestion box service is set to be applied, the consultation management system 1 includes a link to a website that provides the suggestion box service in the email that serves as the reminder medium, or prints a QR code (registered trademark) that indicates the URL of the website on a postcard that serves as the reminder medium. Alternatively, the consultation management system 1 may send a link to the suggestion box at any time to all email members whose email addresses are registered.

[0131] When the patient receives the email or postcard in step S346, the patient accesses the suggestion box site for each ophthalmology clinic using the link in the email or the QR code (registered trademark) on the postcard in step S347 and responds with requests and the like.

[0132] In step S247, the consultation management system 1 stores the answer contents in the database 13. Then, the ophthalmologist or the like can view the answers stored in step S147 from the hospital terminal 3 and collect the patient's opinions and requests.

[0133] Patients rarely have an opportunity to voice their opinions about hospitals, and if they are dissatisfied, they may switch to another hospital. If a survey or suggestion box service can reveal patients' opinions, such as "the parking lot is small" or "the air conditioning in the waiting room is noisy," it will be possible to make further improvements to the hospital and help increase the rate of patients visiting the hospital.

[0134] [Embodiment 6] In the sixth embodiment, it will be explained that the medical examination management system 1 provides information required by patients.

[0135] Fig. 19 is a flowchart for explaining a service in which the medical examination management system provides drug information to patients from a drug database in embodiment 6. Referring to Fig. 19, in step S351, the patient (or ophthalmology staff) photographs an eye drop container with a camera, and in step S352, the drug name label is automatically recognized. For example, if application software with a dedicated character recognition function is installed on the patient's smartphone, photography and automatic recognition can be easily performed.

[0136] Subsequently, in step S353, the patient (or the ophthalmology staff) transmits the medication name and patient ID obtained by the recognition result to the medical examination management system 1.

[0137] In response to this, in step S251, the medical management system 1 performs a process of registering the drug information in association with the patient ID in the database 13. Furthermore, in step S252, the medical management system 1 picks up data indicating the link destination of the "medicine guide" for the registered drug, and in step S253, sends an email to the patient.

[0138] In step S354, the patient receives the e-mail at the patient terminal 4. By clicking on the link included in the e-mail, the patient can view the bookmark for the eye drops and other medications prescribed to them.

[0139] It is difficult for patients to keep such medication guides even if they are provided in paper form, so this service is convenient for patients who have forgotten the names of diseases for which the medications prescribed to them are indicated and how to use them.

[0140] Fig. 20 is a flowchart for explaining a service in which the medical examination management system notifies a patient of the time to instill eye drops in accordance with the sixth embodiment. Referring to Fig. 20, in step S361, the patient (or an ophthalmology staff member) photographs an eye drop container with a camera, and in step S362, the medication name label is automatically recognized. For example, if application software with a dedicated character recognition function is installed on a smartphone, photographing and automatic recognition can be easily performed.

[0141] Subsequently, in step S363, the patient (or the ophthalmology staff) transmits the medication name and patient ID obtained by the recognition result to the medical examination management system 1.

[0142] In response to this, the medical consultation management system 1 performs a process of registering the medication information in the database 13 in association with the patient ID in step S261. Furthermore, the medical consultation management system 1 retrieves data indicating a link to a website where the "eye drop timing setting" for the registered medication can be performed in step S262, and sends an email to the patient in step S263. This website has a pre-prepared screen where the patient can specify the preferred time for each method of eye drop administration. Note that email also includes messages exchanged via short message service (short mail) and other message application software (message app) that can identify the recipient by phone number.

[0143] In step S364, the patient receives the email on the patient terminal 4. By clicking on the link included in the email, the patient can arrive at an input screen that corresponds to the eye drops, etc., prescribed to them. In step S365, the patient sets the administration times for the registered medication on the linked screen in accordance with the administration instructions. For example, if the administration instructions are three times a day, the patient can specify three times a day when they have their smartphone, mobile phone, etc. at hand and can easily see when the reminder emails will arrive.

[0144] When the patient sets the instillation time on the linked screen, information on the instillation time is sent to the medical management system 1, which then records the instillation time in the database 13 in step S264. When the set instillation time arrives, the medical management system 1 sends the patient an email in step S265 indicating that it is the scheduled time to instill the eye.

[0145] The patient receives the e-mail in step S366, and upon learning that the e-mail contains information informing the patient that it is time to administer eye drops, administers the drops in step S367.

[0146] In the sixth embodiment, when the control device 11 executes the process for sending a reminder, it also sends additional information to the patient other than the reminder, i.e., information informing the patient of the time to administer eye drops. By incorporating such a service informing the patient of the time to administer eye drops into the medical examination management system 1, forgetting to administer eye drops can be prevented, which helps to improve the effectiveness of treatment.

[0147] [Embodiment 7] In the seventh embodiment, the status of the patient's eye drops administration is notified to an ophthalmologist or the like.

[0148] 21 is a flowchart for explaining a service in which the medical examination management system reports the time of application of eye drops to an ophthalmologist or a family member in embodiment 7. A homepage displaying an input button for reporting the application of eye drops is prepared in advance and registered in the medical examination management system 1, and the URL is communicated to the patient.

[0149] In step S371, the patient clicks a button on the linked screen when administering eye drops. In step S372, the patient terminal 4 transmits the administration time, medication name, and patient ID to the medical consultation management system 1. In response, in step S271, the patient ID and administration time are stored in the database 13. While the patient reported the administration of eye drops by clicking a button on the linked screen, the administration of eye drops can also be detected and reported using a device for the eye drop container equipped with a detection sensor. Examples of such sensors include a sensor that detects the tilt or pressure of the eye drop container. The medical consultation management system 1 then sends an email informing the patient of the administration of eye drops to the email addresses of family members, etc., as needed. Receiving such an email allows family members to confirm whether the patient's eye drops are administered at the correct time and frequency. This is particularly useful when the patient is elderly and requires close supervision. Furthermore, if the patient lives far from their family, such emails can also be useful for confirming the patient's safety. The eye drop notification email may be a message exchanged via a short message service (short mail) or other message application software (message app) that can identify the recipient by a phone number.

[0150] On the other hand, when an ophthalmologist or the like requests the display of the eye drop implementation status from the hospital terminal 3 in step S171 during an examination, the consultation management system 1 reads out from the database 13 the time data indicating the eye drop implementation status of the patient ID requested from the hospital terminal 3.

[0151] Then, in step S274, the medical consultation management system 1 creates display data and sends it to the hospital terminal 3, whereupon an ophthalmologist or the like can view the data from the hospital terminal 3 in step S172. The ophthalmologist can provide guidance to the patient on eye drops if the patient has applied them at the wrong frequency or at the wrong time. Note that when the display data created in step S274 is sent to the patient terminal 4, the patient can also view the data from the patient terminal 4 in step S373. This allows the patient to check the status of their own eye drops administration.

[0152] 22 is a flowchart illustrating a service in which the medical consultation management system reports the average amount of eye drops used to an ophthalmologist in the seventh embodiment. Referring to FIG. 22, in step S381, the patient (or ophthalmology staff) photographs the eye drop container with a camera, and in step S382, the medication name label is automatically recognized. For example, if application software with a dedicated character recognition function is installed on a smartphone, photographing and automatic recognition can be easily performed.

[0153] Subsequently, in step S383, the patient (or the ophthalmology staff) transmits the medication name and patient ID obtained by the recognition result to the medical examination management system 1.

[0154] In response to this, the medical consultation management system 1 performs a process of registering the medication information in the database 13 in association with the patient ID in step S281. Furthermore, the medical consultation management system 1 retrieves data indicating a link to a website where the "opening date setting" of the registered medication can be performed in step S282, and sends an email to the patient in step S283. This website has a pre-prepared screen where the opening date and end date of use of the eye drops can be entered for each patient ID. Note that email also includes messages exchanged via short message service (short mail) and other message application software (message app) where the recipient can be identified by a phone number.

[0155] In step S384, the patient receives the email on the patient terminal 4. By clicking on the link included in the email, the patient can reach a screen where the patient can input the date on which the prescribed eye drops were opened. In step S385, the patient inputs the date on which the eye drops were opened on the linked screen, thereby transmitting information indicating the opening date to the medical examination management system 1.

[0156] When the patient sets the opening date on the linked screen, information on the opening date is sent to the consultation management system 1, and the consultation management system 1 records the opening date in the database 13 in step S284.

[0157] Furthermore, when the patient has used up the eye drops, the patient inputs the date on which the eye drops will end on the linked screen in step S386, thereby transmitting information indicating the date on which the eye drops will end to the medical examination management system 1.

[0158] When the patient sets the end date of use on the linked screen, information on the end date of use is sent to the medical management system 1, and the medical management system 1 records the end date of use in the database 13 in step S285.

[0159] In step S181, when an ophthalmologist or the like requests display of the average medication usage amount from the hospital terminal 3 during an examination, the medical consultation management system 1 calculates the average usage amount from the date of opening and the date of completion of use of the eye drops corresponding to the patient ID requested from the hospital terminal 3. Then, in step S287, the medical consultation management system 1 creates data to display the average usage amount. The average usage amount may be displayed as, for example, "0.5 mL used per day, one bottle used in two weeks."

[0160] Then, the consultation management system 1 creates display data in step S287 and transmits it to the hospital terminal 3, whereupon the ophthalmologist or the like can view the data from the hospital terminal 3 in step S182.

[0161] In the seventh embodiment, the control device 11 receives information on the date on which the eye drops were opened and the date on which the eye drops were used up from the patient and stores the information in the database 13, and transmits information including the period of use and amount of the eye drops to the hospital terminal 3 located in the ophthalmologist's clinic in response to a request from the ophthalmologist.

[0162] Therefore, an ophthalmologist who views this information can use it to instruct patients on eye drops or to determine the amount of medication to prescribe.

[0163] [Embodiment 8] In the eighth embodiment, an example will be described in which the medical examination management system 1 is used to provide patients with information useful for managing eye drops.

[0164] For example, information on the opening date and expiration date of eye drops may be used to help manage the expiration date of eye drops. Eye drops often have an expiration date printed on the container when unopened, but once opened, the expiration date is often approximately one month from the start of use, regardless of the expiration date printed on the container. However, this fact is not widely known among patients. Therefore, if the expiration date is not entered even after a long time has passed since opening, the medical consultation management system 1 may notify the patient that the expiration date has passed.

[0165] Fig. 23 is a flowchart for explaining a service in which the medical examination management system manages the expiration date of eye drops in Embodiment 8. The processes of S381 to S385 and S281 to S285 in the flowchart of Fig. 23 are common to those in Fig. 22, and therefore description thereof will not be repeated.

[0166] In step S288, the medical consultation management system 1 periodically checks the database 13 to see if there are any eye drops whose expiration date has passed since the date of opening before receiving the end-of-use date. If the expiration date has passed, in step S289, an email is sent to the patient recommending that the patient discard the expired eye drops. The patient receives the email in step S387 and is informed that the expiration date of the eye drops they are currently using has passed.

[0167] As described above, in the eighth embodiment, the control device 11 receives information on the date on which the eye drops were opened and the date on which the eye drops were used up from the patient and stores the information in the database 13. If the patient does not inform the patient of the date on which the eye drops were used up even after a predetermined period of time has passed since the date on which the eye drops were opened and the expiration date has passed, the control device 11 sends the patient an email informing them that the eye drops have expired. Therefore, the patient can avoid using expired eye drops.

[0168] [Embodiment 9] FIG. 24 is a flowchart illustrating a service in which the medical consultation management system notifies a patient of the remaining amount of eye drops based on an image in the ninth embodiment. Referring to FIG. 24, in step S391, the patient (or ophthalmology staff) photographs an eye drop container with a camera, and in step S392, the medication name label is automatically recognized. For example, if application software with a dedicated character recognition function is installed on a smartphone, photography and automatic recognition can be easily performed. Note that the automatic recognition may be performed by recognizing not only characters but also a barcode or QR code (registered trademark) printed on the medication name label.

[0169] Subsequently, in step S393, the patient (or the ophthalmology staff) transmits the medication name and patient ID obtained by the recognition result to the medical examination management system 1.

[0170] In response to this, the medical consultation management system 1 performs a process of registering the medication information in association with the patient ID in the database 13 in step S291. Furthermore, the medical consultation management system 1 picks up data indicating a link to a homepage where the registered medication can be "determined remaining amount" and sends an email to the patient in step S293. This homepage has a pre-prepared screen that informs the patient of the remaining amount when the patient sends an image of the eye drop container they are currently using.

[0171] In step S394, the patient receives the email on the patient terminal 4. By clicking on the link included in the email, the patient can reach a screen for inputting image data of the eye drops prescribed to them. In step S395, the patient inputs a photograph of the eye drop container from the linked screen.

[0172] When the patient sends an image from the linked screen, the image data is sent to the medical management system 1, which receives the image data in step S294. In step S295, the medical management system 1 compares an image of the container before opening, in which a specified amount of eye drops is sealed, with the current image of the container to determine the percentage of liquid volume estimated from the current image, and in step S296 sends remaining volume information to the patient by email. The patient can know the percentage of remaining volume by looking at the email received in step S396.

[0173] The remaining amount information sent from the medical consultation management system 1 to the patient can be modified in various ways. For example, the remaining amount (mL) can be calculated from the container shape and liquid level, and the remaining amount information can be provided as the number of days' worth of medicine this corresponds to, based on a standard amount of use. Since eye drop containers do not have markings or the like, and the amount used varies from patient to patient, it is difficult for patients to grasp the remaining amount. According to the ninth embodiment, it is possible to know approximately how many days' worth of medicine remains in the eye drops, thereby preventing the medicine from running out before the patient's appointment arrives.

[0174] [Embodiment 10] Fig. 25 is a diagram showing a configuration using a consultation management system according to embodiment 10. The configuration shown in Fig. 25 differs from the configuration shown in Fig. 1 in that a patient terminal 4 is connected to a portable testing device 21. The other configuration is the same as that shown in Fig. 1, and therefore description thereof will not be repeated. For example, if the patient terminal 4 is a smartphone, a personal computer, or the like, wireless communication such as Wifi (registered trademark), Bluetooth (registered trademark), or NFC (Near Field Communication) may be used between the portable testing device 21 and the patient terminal 4.

[0175] In the tenth embodiment, an example will be described in which a patient reports biological information measured at home by a portable testing device 21 to an ophthalmologist using the consultation management system 1. The biological information may be, for example, blood pressure, pulse rate, body temperature, etc., but in the case of ophthalmology in particular, examples of biological information include intraocular pressure measured by an intraocular pressure measuring device and fundus photographs taken by a fundus photographing device.

[0176] Glaucoma eye drops are prescribed with the aim of lowering intraocular pressure, but intraocular pressure fluctuates throughout the day. Furthermore, the period and degree of intraocular pressure fluctuations vary from person to person. Therefore, the optimal time to administer eye drops varies from patient to patient. If detailed data on intraocular pressure fluctuations measured at home could be provided to an ophthalmologist, the ophthalmologist could provide guidance on the best time to administer eye drops.

[0177] FIG. 26 is a flowchart illustrating a service in which the medical consultation management system collects information about portable testing devices and provides it to ophthalmologists. Referring to FIG. 26, in step S601, a patient measures their intraocular pressure and takes fundus photographs using the portable testing device 21. The patient measures their intraocular pressure at regular intervals throughout the day, and the measurement data is stored in the portable testing device 21 along with the measurement time. In step S602, the patient transmits time-series intraocular pressure data to a patient terminal 4, such as a smartphone, via wireless communication such as Wifi (registered trademark), Bluetooth (registered trademark), or NFC (Near Field Communication). In step S603, the patient inputs into the smartphone the time when eye drops were administered while the intraocular pressure data to be transmitted was being measured, and in step S604, the patient transmits the data to the medical consultation management system 1 along with the intraocular pressure data.

[0178] In step S501, the consultation management system 1 stores and graphs the intraocular pressure data received from the patient terminal 4. In step S401, the patient-specific self-intraocular pressure measurement data graphed by the consultation management system 1 can be viewed by an ophthalmologist via the hospital terminal 3. In step S402, the ophthalmologist inputs instructions for the patient into the hospital terminal 3. For example, the ophthalmologist transmits advice to the consultation management system 1 about the time to administer eye drops to coincide with the time when intraocular pressure peaks.

[0179] The consultation management system 1 stores the patient advice received from the hospital terminal 3 in step S502 in the database 13, and also transmits the patient advice by email to the patient terminal 4. In step S605, the patient receives the ophthalmologist's instructions at the patient terminal 4. The patient can change the time of eye drops administration based on the ophthalmologist's instructions.

[0180] Next, after changing the time of instillation, the patient measures his / her intraocular pressure with the portable testing device 21 in step S601A. In step S602A, time-series intraocular pressure data is sent via Wifi (registered trademark) to the patient terminal 4, such as a smartphone. In step S603A, the patient inputs into the smartphone the time when the eye drops were instilled while the intraocular pressure data to be sent was being measured (after the change based on the ophthalmologist's instructions), and in step S604A, sends this together with the intraocular pressure data to the consultation management system 1.

[0181] In step S501A, the consultation management system 1 stores and graphs the intraocular pressure data received from the patient terminal 4. In step S403, the patient-specific self-intraocular pressure measurement data graphed by the consultation management system 1 can be viewed by the ophthalmologist via the hospital terminal 3. In this way, the ophthalmologist can confirm the effect of changing the eye drop administration time on fluctuations in intraocular pressure.

[0182] As described above, the consultation management system of the tenth embodiment can notify the patient of the optimal timing for administering glaucoma eye drops, taking into account daily fluctuations in intraocular pressure under the supervision of an ophthalmologist, and the ophthalmologist can also know the effect of changing the administration time.

[0183] [Embodiment 11] In the eleventh embodiment, a case will be described in which the medical examination management system 1 provides various information to patients with hay fever.

[0184] Fig. 27 is a diagram showing a configuration using a medical consultation management system according to embodiment 11. The configuration shown in Fig. 25 differs from the configuration shown in Fig. 1 in that, in addition to the configuration shown in Fig. 1, the patient terminal 4 is configured to be able to acquire the position of the patient terminal 4 using a GPS 31 including multiple GPS (Global Positioning System) satellites, and the medical consultation management system 1 is configured to be able to acquire information such as weather, wind direction, and temperature from a weather information provider 32 such as the Japan Meteorological Agency. The other configurations are the same as those in Fig. 1, so description thereof will not be repeated. For example, when the patient terminal 4 is a smartphone, it is often configured to be able to acquire position information from a GPS.

[0185] In the eleventh embodiment, when a patient with hay fever inputs the degree of itching caused by hay fever into the patient terminal 4, the patient terminal 4 simultaneously acquires location information using the GPS 31. The medical examination management system 1 acquires meteorological conditions such as the weather, wind direction, and temperature at that time and location from the weather information provider 32 and records them in the database 13.

[0186] By storing such information, for example, if similar weather conditions are predicted for the following year, the patient can be notified of the risk of developing hay fever in advance.

[0187] FIG. 28 is a flowchart illustrating the services provided by the medical management system to patients with hay fever. Referring to FIG. 28, in step S611, the patient inputs the degree of itching they feel due to hay fever into the patient terminal 4. For example, when the patient feels a strong itch, the patient operates their smartphone to input that the itch is strong. Then, in step S612, the time and location information are automatically acquired by the smartphone, and in step S613, information such as "March 10th, 2:00 PM, itchy +++" and the location information are sent from the smartphone to the medical management system 1. Note that the location information is not limited to the patient's actual location, and the patient may manually input the location information themselves.

[0188] In step S511, the medical management system 1 acquires weather data (wind direction, wind speed, temperature, etc.) for the location included in the information transmitted from the patient terminal 4. Then, in step S512, the medical management system 1 stores in the database 13 a set of (1) itching level, (2) location data, and (3) weather data transmitted from the patient.

[0189] Next, in step S513, the medical management system 1 analyzes the conditions under which the patient feels strong itching. For example, the medical management system 1 identifies the combination of temperature, location, wind direction, etc. on the day the patient felt strong itching, based on the accumulated data.

[0190] Based on the analysis results, in step S514, the medical examination management system 1 sends "hay fever risk information" customized for each patient by email to the patient terminal 4. When the hay fever risk information is received by email in step S614, the patient can take measures against hay fever, such as wearing a mask when going out, changing the place where they go out, or refraining from going out.

[0191] Although the above embodiment has been described using a specific example in which the system is introduced into an ophthalmology clinic, it may also be introduced into other clinics. In that case, eye drops may be read as oral medication, etc.

[0192] The embodiments disclosed herein should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims, not by the description of the above embodiments, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0193] 1 consultation management system, 2 computer network, 3 hospital terminal, 3a input section, 3b transmission section, 3c request section, 3d reception section, 4 patient terminal, 11 control device, 12 printer, 13 database, 21 portable testing equipment, 32 weather information provider.

Claims

1. A consultation management system that encourages patients to visit a doctor, A memory unit; a control device that stores in the storage unit, in association with first data that identifies the patient, second data that indicates a consultation date corresponding to the patient, and third data that indicates either a period until the next consultation, a scheduled next consultation date, or an appointment date determined by an ophthalmologist; the control device executes a process for sending a reminder to encourage a patient to visit the hospital when a scheduled visit date calculated from the period until the next visit indicated by the third data is approaching within a first predetermined number of days; The control device receives from the patient information on the date the eye drops were opened and the date on which the eye drops were used up, stores the information in the memory unit, and, upon request from the ophthalmologist, transmits information including the period of use and amount of the eye drops to a hospital terminal located in the ophthalmology clinic.

2. The control device further stores fourth data indicating whether a reminder to prompt the patient to see a doctor and fifth data indicating a type of the reminder in the storage unit; 2. The consultation management system of claim 1, wherein the control device selects and executes an email sending process or a mail printing process to encourage a patient to visit the hospital based on the fifth data for a patient for whom the fourth data indicates that a reminder is necessary and whose scheduled appointment date calculated from the period until the next appointment indicated by the third data is approaching within a first predetermined number of days.

3. 3. The medical consultation management system of claim 2, wherein the control device further executes an email sending process or mail printing process to encourage a medical consultation if the patient's updated medical consultation date is not stored in the memory unit within a certain period after executing an email sending process or mail printing process to encourage a medical consultation.

4. the control device stores in the storage unit sixth data specifying the medicine prescribed by the ophthalmologist, seventh data indicating the amount of the medicine prescribed by the ophthalmologist, and eighth data indicating the date on which the medicine was prescribed; The control device calculates a reference date when the remaining amount of medication will be zero based on the sixth data, the seventh data, and the eighth data, and executes an email sending process or a mail printing process to encourage patients who are within a second predetermined number of days of the reference date to visit the hospital.

5. A medical consultation management system as described in any one of claims 1 to 4, wherein if the patient has not notified the patient of the date the eye drops were used up even after a predetermined period of time has passed since the date of opening and the expiration date has passed, the control device sends an email to the patient informing them that the expiration date of the eye drops has passed.

6. The medical consultation management system according to claim 1 , wherein the control device sends additional information other than the reminder to the patient when executing the process for sending the reminder.

7. A reminder method for encouraging a patient to visit a doctor using a computer, comprising: storing second data indicating a consultation date corresponding to the patient in a storage unit in association with first data identifying the patient; storing third data in the storage unit in association with the first data, the third data indicating either a period until the next visit, a scheduled date for the next visit, or an appointment date determined by the ophthalmologist; a step of sending a reminder to encourage a patient to visit the hospital when a scheduled visit date calculated from the period until the next visit indicated by the third data, the next scheduled visit date, or the appointment date is approaching within a predetermined number of days; The reminding method includes a step of receiving from the patient information on the date on which the eye drops were opened and information on the date on which the eye drops were used up, storing the information in the memory unit, and transmitting information including the period of use and amount of the eye drops to a hospital terminal located in an ophthalmology clinic in response to a request from the ophthalmologist.

8. The reminding method described in Claim 7, further comprising a step of sending an email to the patient informing them that the expiration date of the eye drops has passed, if the patient has not notified them of the date they used up the eye drops even after a predetermined period of time has passed since the date of opening the eye drops.

9. The step of storing the third data in the storage unit further includes storing fourth data indicating whether or not a reminder to prompt the patient to visit a doctor and fifth data indicating a type of reminder in the storage unit; 8. The reminder method according to claim 7, wherein the step of sending the reminder selects, based on the fifth data, sending an email or printing mail to encourage a patient to visit the hospital when the fourth data indicates that a reminder is necessary and when the scheduled visit date calculated from the period until the next visit indicated by the third data is approaching within a predetermined number of days.

10. A medical examination management program for causing a computer to execute the reminding method according to any one of claims 7 to 9.

11. an input unit configured to input first data identifying a patient, second data associated with the first data and indicating a consultation date corresponding to the patient, third data indicating a period until the next consultation or a scheduled next consultation date determined by a doctor, and fourth data indicating whether a reminder to encourage the patient to consult a doctor is necessary; a transmitting unit configured to transmit the first to fourth data to a medical management system; a request unit that requests the medical examination management system to output drug information; A receiving unit for the drug information, the input unit is configured to further input sixth data indicating a drug prescribed by a doctor selected from the drug information received by the receiving unit, seventh data indicating an amount of the drug prescribed by the doctor, and eighth data indicating a date on which the drug was prescribed; The transmission unit is configured to further transmit the sixth to eighth data to the medical examination management system; The request unit further requests the medical examination management system to output patient information indicating the percentage of patients who visited the medical examination management system within a second predetermined number of days until a reference date when the remaining amount of medicine calculated based on the sixth data, the seventh data, and the eighth data becomes zero; The hospital terminal, wherein the receiving unit is configured to further receive the patient information.

12. a process of receiving, via an input unit, first data identifying a patient, second data associated with the first data and indicating a consultation date corresponding to the patient, third data indicating a period until the next consultation or a scheduled next consultation date determined by a doctor, and fourth data indicating whether a reminder to encourage the patient to consult a doctor is necessary; A process of transmitting the first to fourth data to a medical management system; A process of requesting the medical examination management system to output drug information; receiving the drug information; a process of further receiving, via the input unit, sixth data indicating a drug prescribed by a doctor selected from the received drug information, seventh data indicating the amount of the drug prescribed by the doctor, and eighth data indicating the date on which the drug was prescribed; A process of further transmitting the sixth to eighth data to the medical examination management system; a process of further requesting the medical examination management system to output patient information indicating the percentage of patients who visited the hospital within a second predetermined number of days until a reference date when the remaining amount of medicine calculated based on the sixth data, the seventh data, and the eighth data becomes zero; and a program for causing a computer operating as a hospital terminal to execute the process of receiving the patient information.

Images