JP2009031889A - Medical service provision system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a medical service providing system capable of providing a patient with care related to patient care after a medical examination from the side of a medical institution.
When a medical record / prescription data of a patient examined by each doctor is transmitted from a personal computer 12a, 12b installed in each examination room in the hospital 1 to the in-hospital server 11 via the LAN 10, the in-hospital server 11 calculates a medication end date of the medicine prescribed to the patient based on the received medical record / prescription data, and generates an e-mail notifying the patient of the medication end date. Then, two days before the end date, the in-hospital server 11 transmits the generated e-mail from the base station 4 to the mobile phone 2 possessed by the patient via the router 13 and the Internet 5.
[Selection] Figure 1

Description

  The present invention relates to a medical service providing system that can provide a service related to patient care after a medical examination.

  Today, in medical institutions such as hospitals, consultation reservations, chart preparation, and checkout processing are systemized using information terminals such as computers connected to the network, which greatly increases patient waiting time before and after the doctor's examination. Has been shortened to. In recent years, the scale of the system described above is not limited to hospitals, but is connected to an information terminal installed in a pharmacy, and a system for medical institutions that improves the convenience of users for providing drugs based on prescriptions. Has been proposed.

  For example, in the medical reservation system disclosed in Patent Document 1, a patient can make a medical appointment from a homepage of a hospital established on the Internet from a mobile phone. If specified, when the doctor inputs information about the contents of the examination and information about the prescription (hereinafter referred to as prescription information) to the host computer of the hospital after the examination, Prescription information is transmitted to the terminal. As a result, patients can make appointments for examinations even outside the opening hours of the hospital, and the pharmacies can immediately dispense the medicines that were in the prescription, and they were instructed by the prescription without waiting for the patient. Medicine can be provided.

  Moreover, in the medical service providing system disclosed in Patent Document 2, it is possible to make a medical appointment by accessing a server in a hospital from a terminal installed at a patient's home, as in the medical appointment system described above. . Further, after the medical examination, when the doctor registers the prescription information in the server in the hospital, the prescription ID associated with the prescription information is written on an examination card (hereinafter referred to as an IC examination ticket) converted to an IC card, and is sent to the patient. Returned. When the patient submits the IC examination ticket to the pharmacy, the prescription information can be obtained from the hospital server based on the prescription ID written in the IC examination ticket from the terminal installed in the pharmacy. Dispensing medicine based on information. Furthermore, after the patient returns home, it is also possible to make inquiries from the terminal at home by accessing the pharmacy and the hospital server about the efficacy and usage of the prescribed medicine and the response method according to changes in symptoms.

JP 2001-357307 A JP 2002-245162 A

  By the way, it is difficult for the conventional various systems described above to provide a sufficient service for care for a patient after examination. In other words, the system disclosed in Patent Document 1 improves the convenience of the patient, but does not provide any services to the patient during the period between the purchase of the prescribed drug and the next appointment appointment. There is nothing to do. Further, in the system disclosed in Patent Document 2, after a patient returns home, he / she can access a pharmacy or a hospital server from his home terminal to inquire about the efficacy / usage of the drug and the response method for symptom change. However, since the patient has to take action, for example, a patient who is not good at operating a personal computer may not use the above-described service. In addition, with the increasing number of elderly people living alone due to the progress of the nuclear family and aging, the need for a system that can actively provide services to patients from the healthcare provider side is increasing. is expected.

  Therefore, an object of the present invention is to provide a medical service providing system capable of providing a patient with care related to patient care after a medical examination from the medical institution side.

  In order to achieve the above object, the present invention provides a medical service providing system that provides a patient with a service related to care after medical examination, and is a calendar that always measures time and indicates the current date and time. Timing means for generating information, notification mail information storage means for storing character string information indicating the text of an e-mail notifying that the medication period has ended, and unique information assigned to each of the plurality of patients Patient information storage means for storing the patient identification information of the patient and at least the destination information indicating the email transmission destination of the patient corresponding to the patient identification information, the examination date for examining the patient, and the medicine prescribed on the examination date Prescription information storage means for storing prescription information including information on the name, dose, usage, quantity, etc. of the patient in association with the patient identification information given to the patient, and the notification mail information storage hand A prescription information unique to the patient stored in the prescription information storage means in the character string information stored in the prescription information storage means, and a notification mail generation means for generating a medication end notification mail; and the prescription information storage means Based on the stored prescription information, an end date calculating means for calculating an end date for taking the medicine prescribed for the patient specified by the patient identification information associated with the prescription information, and the timing means are generated Notification mail transmission determining means for determining whether or not to transmit the dose end notification mail generated by the notification mail generation means based on the calendar information to be performed and the dose period end date calculated by the end date calculation means And when the notification mail transmission determining means determines to transmit the dose end notification mail, the dose end notification mail is sent to the patient information storage means. Is characterized by comprising a mail transmission means for transmitting according to the transmission destination information stored patient.

  Here, the “dose” included in the prescription information is the amount of medicine to be taken at one time, and the “usage” is information indicating when the medicine is taken (for example, “before every meal”, “after every meal”, “ Once in the morning "," before going to bed ", etc.). The “amount” is information indicating how many tablets (or how many, how many days) the medicine is prescribed. Further, the prescription information unique to the patient, which is incorporated in the character string information stored in the notification mail storage means by the notification mail generation means, includes, for example, the date of examination, the name and quantity of the medicine prescribed for the patient, etc. is there. Further, the notification mail transmission determining means, for example, when the current date and time coincide with the date and time when the dosing period ends, or the current date and time is a predetermined time before the date and time when the dosing period ends. Or when a predetermined time has elapsed, it is determined to send a dosing end notification mail.

  According to the present invention, the end date and time of the medication period prescribed for each patient is calculated based on the examination date included in the prescription information of each patient and the dose, usage, and quantity of the medicine prescribed on the examination date. Based on the current date and the calculated end date of the taking period, an e-mail notifying the patient that the end of the taking period is approaching or has ended (dose period) (End mail) is sent. As a result, the patient who received the e-mail can know that the end of the medication period is approaching or has ended, and reserves the next examination based on the physical condition at that time. It can be an opportunity to determine whether or not. Therefore, a service related to patient care after a medical examination can be provided from a medical institution such as a hospital.

  In the medical service providing system described above, the present invention provides a mail receiving unit that receives an e-mail transmitted from the outside, and a patient that the mail receiving unit has transmitted the dosing end notification mail by the mail transmitting unit. A response mail determination means for determining whether or not a response mail for the dose end notification mail has been received; and when the mail reception means determines that the reply mail has not been received from the patient by the response mail determination means, Response non-reception notification means for performing notification to that effect is provided.

  Here, the timing at which the response mail determination means determines whether or not the response mail from the patient who has sent the dose end notification mail has been received is, for example, every time a predetermined time elapses or the above dose There are times when a predetermined time has elapsed since the end notification mail was transmitted.

  According to the present invention, in the above-described medical service providing system, when a reply mail is not sent from the patient who has transmitted the above-described dosing period completion notification mail, this is notified by the response non-reception notification means. . As a result, it is possible to quickly notify a person in charge at a medical institution such as a hospital that there is no response from the patient in response to the notification message of completion of medication sent to the patient. Measures such as checking the condition can be taken quickly.

  In addition, in any one of the medical service providing systems described above, the present invention provides a reservation information storage that stores reservation information including information related to the patient appointment date and time in association with the patient identification information given to the patient. Means, a reservation information confirming means for determining whether or not the reservation information of the patient to which the dose completion notification mail is transmitted by the mail transmitting means is stored in the reservation information storing means, and the reservation information confirming means In addition, when it is determined that the reservation information of the patient who has transmitted the dosing end notification mail is not stored in the reservation information storage unit, the reservation information storage unit includes a reservation non-registration notification unit that notifies that fact. .

  Here, as the timing at which the reservation information confirmation unit confirms the reservation information of the patient who has sent the dosing end notification email, for example, when the current date and time coincide with the date and time when the dosing period ends, or the current date and time When a predetermined time elapses or a predetermined time elapses before the date and time when the dosing period ends, and further, when a predetermined time elapses after the above-mentioned dosing end notification email is transmitted, There is a case where the response non-reception notifying means performs notification, a time when a predetermined time has elapsed since the response non-reception notifying means performs notification, and the like.

  According to the present invention, after sending a dose end notification mail to a patient, for example, when no reply mail is sent from the patient, the next examination information of the patient is stored in the reservation information storage means. In other words, it is confirmed whether or not the patient has made a next medical appointment, and if the next medical appointment has not been made, this is notified by the reservation non-registration notification means. Therefore, for example, it is possible to promptly notify a person in charge at a medical institution such as a hospital that the patient has not made an appointment for the next examination despite the fact that the patient has been notified of the end of the dose. The person in charge can quickly take measures such as checking the condition of the patient.

  Furthermore, the present invention provides a notification mail information storage unit that stores character string information indicating a text of an e-mail prompting a patient to take a medicine in any of the medical service providing systems described above, and the notification mail information storage unit Incorporating prescription information unique to the patient stored in the prescription information storage means into the character string information stored in the notification information generating means for generating a dosing time notification mail, and the timing means are generated. Based on the calendar information and the prescription information, it has notification mail transmission determining means for determining whether or not to send the dosing time notification mail generated by the notification mail generating means, the mail generating means When the notification mail transmission determining means determines to transmit the dose time notification mail, the notification time notification mail is sent to the patient information storage means. It is characterized by transmitting according to the transmission destination information stored patient.

  Here, the prescription information unique to the patient incorporated in the character string information stored in the notification mail storage means by the notification mail generation means includes, for example, the name and dose of the medicine prescribed for the patient. In addition, the notification mail transmission determining means transmits the dosing time notification mail when, for example, the current time reaches a predetermined dosing time or before a predetermined time. To decide.

  According to the present invention, when it is time to take a medicine prescribed for each patient, or when the time is approaching, an e-mail (dosing time notification mail) prompting to take the medicine is transmitted to each patient. The As a result, the patient who has received the e-mail can know that it is time to take the medicine or that it has approached, so the possibility that the patient forgets to take the medicine can be reduced, Services related to patient care after the examination can be actively provided to the patient from the medical institution side.

  ADVANTAGE OF THE INVENTION According to this invention, the service regarding the care of the patient after a medical examination can be provided with respect to a patient from the medical institution side.

  Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating an overall configuration of a medical service providing system according to the present embodiment. A hospital 1 as a medical institution in which the medical service providing system according to the present embodiment is installed, and the medical service providing system described above. A mobile phone 2 and a pharmacy 3 of a patient who receives services from are shown. The cellular phone 2 possessed by the patient communicates with the base station 4 wirelessly and can communicate with other telephones via a telephone line (not shown) and communicate with other information terminals via the Internet 5. Data communication is possible. The pharmacy 3 is provided with a personal computer (hereinafter referred to as a personal computer) 30 that receives services from the medical service providing system according to the present embodiment, and is connected to the Internet via a router 31 that is also installed in the pharmacy 3. Data communication with other information terminals connected to 5 is possible.

  A LAN (Local Area Network) 10 is constructed in the hospital 1, and the LAN 10 is connected with an in-hospital server 11, personal computers 12 a and 12 b assigned to each doctor working in the hospital 1, and a router 13. ing. The in-hospital server 11 is installed in a department that performs medical office work, for example, and communicates various information with the personal computer 30 installed in the mobile phone 2 and the pharmacy 3 via the router 13 and the Internet 5. Further, as will be described in detail later, the in-hospital server 11 has built various databases (hereinafter, “database” is referred to as DB), and data input from a keyboard (described later) provided in the in-hospital server 11; And the data in each DB are updated by the data transmitted via the LAN 10 from the personal computers 12a and 12b installed in the examination room where each doctor examines in the hospital 1. Further, the in-hospital server 11 provides various services to the patient and the pharmacy 3, and based on the data stored in each DB, the mobile phone 2 and the pharmacy 3 in the above-described mobile phone 2 via the router 13 and the Internet 5 are used. Information is provided to the personal computer 30.

  Each of the personal computers 12a and 12b is installed in a doctor's office where a doctor consults, and all of them have hardware such as a CPU, a RAM, a hard disk drive, a keyboard, a mouse, and a monitor, which are included in a normal personal computer. In addition, a communication board (hereinafter referred to as a LAN card) that enables data communication via a LAN is provided, and various data are exchanged with the hospital server 11 via the LAN 10.

  In order to enable the in-hospital server 11 and the personal computers 12a and 12b to communicate with other devices via the Internet 5, the router 13 is a network address translator (NAT) or a network address port translator (NAPT), for example. A global IP address assigned to the hospital 1 from an unshown provider and a private IP address assigned to various information terminals such as personal computers 12a and 12b connected to the LAN 10 by a network administrator of the LAN 10, for example. It has a function to convert.

  The personal computer 30 installed in the pharmacy 3 includes a LAN card in addition to hardware such as a CPU, a RAM, a hard disk drive, a keyboard, a mouse, and a monitor. The LAN card is connected to the router 31, and the router 31 transmits and receives data to and from the hospital server 11 via the Internet 5.

  Next, the configuration of the hospital server 11 will be described with reference to the block diagram shown in FIG. In FIG. 2, the CPU 110 executes the program stored in the ROM 111 to control various devices including the ROM 111 via the bus B and realize the function of the medical service providing system in the present embodiment. The work RAM 112 temporarily stores data generated in the process in which the CPU 110 executes the above-described program. A real-time clock (hereinafter referred to as RTC) 113 constantly measures time, and outputs calendar information representing the current year, month, day, day of the week, hour, minute, and second to the CPU 110 in response to a request from the CPU 110. To do. Therefore, the RTC 113 corresponds to a time measuring means. The keyboard 114 includes a plurality of keys corresponding to letters, numbers, and symbols, and outputs information input by operating the keys by the office staff in the hospital 1 to the CPU 110. The display 115 is a control screen for controlling the medical service providing system according to the present embodiment, an input screen for inputting data of various DBs described later, and information notified to the above-mentioned office staff (described later). For example, a user interface screen is displayed. The LAN card 116 is connected to the LAN 10, and exchanges various data with the personal computers 12 a and 12 b installed in the hospital 1 and the mobile phone 2 and the personal computer 30 under the control of the CPU 110.

  The database storage device 117 and the mail information storage device 118 are auxiliary storage devices such as hard disk drives, for example. The database storage device 117 stores data constituting various DBs such as a patient DB, a reservation DB, a medical record / prescription DB, and a medicine DB. I remember it. The mail information storage device 118 is provided with a mail transmission schedule storage area, a mail text storage area, and a mail data storage area. The mail transmission schedule storage area stores mail transmission schedule information (details will be described later) for managing the transmission schedule of electronic mail to be transmitted to the mobile phone 2. In the mail text storage area, character string information (hereinafter referred to as mail text information) that forms the format of an email to be transmitted to the mobile phone 2 possessed by the patient is stored. Further, in the mail data storage area, an email transmitted to each patient generated based on the above-described email format and an email received from each patient are stored.

  Next, the contents of the patient DB, reservation DB, medical record / prescription DB, and drug DB stored in the database storage device 117 will be described with reference to FIGS. FIG. 3 shows the contents of data stored in the patient DB. For example, a patient ID (patient identification information) consisting of letters, numbers, and symbols uniquely given to each patient at the time of the first visit, The patient's name, a unique number assigned to the patient's examination ticket (hereinafter referred to as the examination ticket No.), and the e-mail address (destination information) specified by the patient are stored in association with each other. ing. The data related to these patients is registered in the patient DB from the keyboard 114 of the in-hospital server 11 based on an questionnaire filled in by the patient at the first visit. The patient DB 110 corresponds to patient information storage means. FIG. 4 shows the contents of the data stored in the reservation DB. The above-mentioned patient ID and reservation number given when the patient makes a reservation for a medical examination. The appointment date, appointment time zone, medical department for which examination is desired, and the name of the doctor in charge are stored in association with each other. These data are registered in the reservation DB from the keyboard 114 of the in-hospital server 11 when the patient makes a medical appointment. This reservation DB corresponds to reservation information storage means.

  FIG. 5 shows the contents of the data stored in the medical record / prescription DB, and the medical record / prescription DB stores the medical examination contents of the patient in charge for each doctor. Specifically, as shown in FIG. 5, for the data indicating the name of the doctor and the medical department to which the doctor belongs, the patient ID of the patient who was examined, the date of the patient's examination, and the contents of the inquiry in the examination performed on each examination date Further, the medicine ID and quantity indicating the kind of medicine prescribed by the doctor at the time of each examination are stored in association with each other. Here, the medicine ID is identification information (described later) uniquely assigned to each medicine that can be prescribed in the hospital 1. Moreover, the amount of the above-mentioned medicine is represented by the number of days of the dosing period (that is, the taking period). In FIG. 5, up to three types of drugs can be registered in the prescription DB, but the number of types of drugs that can be registered may be more than this. This chart / prescription DB corresponds to prescription information storage means.

  FIG. 6 shows the contents of the data stored in the drug DB. The drug ID, which is unique identification information given to each drug that can be prescribed in the hospital 1, the name of the drug, and the drug (That is, information indicating when to take the medicine, for example, “after each meal”, “before each meal”, “when waking up”, “before going to bed”, etc.) (Notification time designation information), a dose of medicine (amount of medicine taken at a time), and information indicating precautions during taking (for example, sleepiness after taking) are stored in association with each other.

  Next, the contents of the mail transmission schedule information and the mail text information stored in the mail transmission schedule storage area and the mail text storage area of the mail information storage device 118 will be described with reference to FIGS. FIG. 7 shows the contents of the email transmission schedule information. The patient ID, the medication end date when the medication period prescribed for each patient is completed, and the medication time created based on the email text information described later are shown. An e-mail for notifying the patient (dose time notification e-mail) file name (indicated as “ma1”, “mb1”, etc. in FIG. 7) and an e-mail for notifying the patient that the dosing period is about to end Information indicating whether the email (hereinafter referred to as a dose termination notification email) was sent, the email address to which these emails were sent, and whether a reply email was received for the dose termination notification email (FIG. 7) Are described as “reply mail” in association with each other. Here, the information indicating whether or not a reply mail is received is represented by “0” or “1”. If “0”, no reply mail is received, and if “1”, the reply mail is received. Is received. Moreover, the transmission time of the above-mentioned dosing time notification mail is predetermined at three times of 7:00, 12:00, and 19:00, and each transmission is performed according to the notification time designation information of the medicine prescribed to the patient. The CPU 110 generates a dosing time notification mail corresponding to the time. In FIG. 7, a portion that is blank for each transmission time of 7:00, 12:00, and 19:00 indicates that there is no taking time notification mail transmitted at that time. .

  8A and 8B are explanatory diagrams for explaining an example of the contents of the mail text information stored in the mail information storage area. FIG. 8A is a dose end notification mail, and FIG. 8B is a dose time notification. Shows the contents of the email text information. These texts are stored as text data in the mail information storage device 118, and in the text of each mail, information specific to the patient who sends each mail is located at the position of the variable name between “&”. A mail addressed to each patient is generated by replacement / insertion by the CPU 110. That is, in the dosing end notification mail shown in FIG. 8A, the variable name “& Name &”, “& Date &”, “& mdep &”, “& term &” is included in the text of the mail, and the dose for the patient with the CPU 110 is included. When creating the end notification mail, the name of the patient who sends the mail is read from the patient DB and replaced / substituted at the position of the variable name “& Name &”. In addition, in the positions of the variable names “& Date &”, “& mdep &”, and “& term &”, the patient's examination date, the medical department that received the examination, and the amount of the prescribed medicine, respectively, are sent to the chart / prescription DB. Is read and replaced / assigned.

  In addition, in the dosing time notification mail shown in FIG. 8B, in addition to the variable names “& Name &”, “& Date &”, “& mdep &”, which are the same as the dosing end notice mail, “& media1 &”, “& media2 &”, “& media3 &” ”Is included. At the position of this variable name, the CPU 110 reads out the name of the medicine from the medicine DB based on the medicine ID prescribed to the patient who sends the mail stored in the medical chart / prescription DB, and replaces / substitutes it. Is done. The mail information storage device 118 that stores the text of the dose end notification mail and the dose time notification mail corresponds to the notification mail storage means and the notification mail storage means.

  Next, with reference to FIG. 9 to FIG. 14, the operation in the present embodiment having the above-described configuration will be described. FIG. 9 is a chart / prescription data registration executed when the hospital server 11 registers the chart / prescription data transmitted from the personal computer 12a or 12b via the LAN 10 in the chart / prescription DB shown in FIG. It is a flowchart which shows the flow of a process.

  When the chart / prescription data registration process is executed, the CPU 110 of the hospital server 11 first determines whether or not the chart / prescription data is received from the personal computer 12a or 12b via the LAN 10 by the LAN card 116 (step S1). ). Here, the medical chart / prescription data includes the name of the doctor, the medical department to which the doctor belongs, the patient ID of the patient being examined, the date of the examination, the contents of the interview and findings in the examination, the drug ID corresponding to the prescribed drug, and the prescription It consists of data showing the amount of medicine. If no medical record / prescription data is received from the personal computer 12a or 12b, the determination result in step S1 is NO, and the CPU 110 repeatedly performs the process in step S1, and hereinafter, the medical record / prescription data reception standby state. It becomes.

  On the other hand, when the medical record / prescription data is received from the personal computer 12a or 12b, the determination result in step S1 is YES, and the CPU 110 temporarily stores the received medical record / prescription data in the work RAM 112 (step S2), and the database storage device. The medical record / prescription DB in 117 (see FIG. 5) is registered (step S3). That is, the CPU 110 searches the medical record / prescription DB based on the doctor's name and the data indicating the medical department to which the doctor belongs among the medical record / prescription data stored in the work RAM 112, and the data (patients) examined by the corresponding doctor ( Patient-related data stored in the work RAM 112 is added to and registered in the patient ID, examination date, contents of inquiry and findings, drug ID, and the amount thereof. Next, the CPU 110 determines whether or not a medicine ID is included in the medical record / prescription data stored in the work RAM 112 (step S4). If no medicine is prescribed for the patient in this examination, the determination result in step S4 is NO, and the CPU 110 returns to the process in step S1 and enters a medical record / prescription data reception standby state.

  On the other hand, if the medical record / prescription data stored in the work RAM 112 includes a medicine ID, the determination result in step S4 is YES, and the CPU 110 displays the prescription end date of the prescribed medicine. Calculate (step S5). That is, the CPU 110 calculates the dose end date by adding the amount (number of days) of the prescribed medicine to the examination date stored in the work RAM 112, and temporarily stores the result in the work RAM 112. Next, the CPU 110 generates a medication end notification email for notifying the medication end date calculated in step S5 (step S6). That is, the CPU 110 first reads the text data of the dosing end notification mail shown in FIG. 8A from the mail text storage area of the mail information storage device 118. Next, the patient ID is read out from the medical chart / prescription data stored in the work RAM 112, and the name of the patient corresponding to the patient ID is read out from the patient DB (see FIG. 3) stored in the database storage device 117. . Then, the character string “& Name &” in the text of the above-mentioned medication end notification mail is replaced with a character string representing the patient's name read from the patient DB. In addition, the CPU 110 includes the character strings “& Date &”, “& mdep &”, and “& term &” in the text of the above-mentioned medication end notification email in the medical chart / prescription data stored in the work RAM 112, respectively. Replace it with a character string that represents the examination date, medical department, and quantity.

  Then, the CPU 110 associates the medication end notification email generated in step S6 with the patient ID stored in the work RAM 112 and stores it in the email data storage area of the email information storage device 118 (step S7). Next, the CPU 110 reads the mail address corresponding to the patient ID from the patient DB based on the patient ID stored in the work RAM 112, and adds it to the mail transmission schedule information together with the patient ID and the dose end date calculated in step S5. ,Remember. At this time, the value of “reply mail” for the patient ID is stored as “0” (step S8). And CPU110 produces | generates the dosing time alerting | reporting mail transmitted to the patient corresponding to patient ID memorize | stored in work RAM112 (step S9). The procedure for generating the dosing time notification mail will be described in detail later. When the process of step S9 is completed, the CPU 110 clears the medical chart / prescription data stored in the work RAM 112 in the process of step S2, returns to the process of step S1, and enters a medical record / prescription data reception standby state.

  As described above, when the CPU 110 receives the medical record / prescription data from the personal computer 12a or 12b, the CPU 110 calculates the medication end date by the process of step S5 based on the received medical record / prescription data, and then finishes the administration by the process of step S6. Generate an email to notify the patient of the day. Therefore, CPU110 which performs the process of step S5 and S6 is equivalent to an end date calculation means and a notification mail production | generation means.

  Next, with reference to FIG. 10, the process for generating the dosing time notification mail in step S9 of FIG. 9 will be described in detail. First, the CPU 110 reads the text data of the dosing time notification mail shown in FIG. 8B from the mail text storage area of the mail information storage device 118 (step S10). Then, the CPU 110 reads the patient ID from the medical record / prescription data stored in the work RAM 112, and obtains a character string representing the patient's name corresponding to the patient ID from the patient DB stored in the database storage device 117. read out. Then, the character string “& Name &” in the text of the dosing time notification mail read in step S10 is replaced with a character string representing the patient's name read from the patient DB (step S11). Next, the CPU 110 reads the examination date and the medical department included in the medical chart / prescription data stored in the work RAM 112, and “& Date &” and “& mdep &” in the text of the dosing time notification mail read in step S10. Are replaced with each other and stored in the work RAM 112 (step S12).

  Next, the CPU 110 reads out all medicine IDs from the medical record / prescription data stored in the work RAM 112, and names of medicines corresponding to the respective medicine IDs from the medicine DB (see FIG. 6) and notification time designation information. Is read (step S13). Then, the CPU 110 determines whether or not a medicine ID to which a medication time notice mail should be transmitted is included in the medicine ID stored in the work RAM 112 based on the read notice time designation information. (Step S14). In the case where a medicine ID to which a medication time notification mail is to be transmitted at 7:00 am is included (that is, there is a medicine in which the item of 7:00 in the notification time designation information shown in FIG. 6 is “1”), The determination result in step S14 is YES, and the CPU 110 reads the name of the medicine ID from the medicine DB, and the character string “& medi1 &” to “& medi3 &” in the text of the dosing time notification mail that has been processed in step S12. (Step S15). Here, if there is only one medicine ID for which a medication time notification mail should be sent at 7:00 am, the character string “& media1 &” is replaced with the name corresponding to the medicine ID, and “& medi2 &” and “& media3 &” Delete the string. If there are two, the character strings “& media1 &” and “& media2 &” are replaced with names corresponding to the drug IDs, and the character string “& media3 &” is deleted.

  Next, CPU 110 assigns a unique file name to the text data of the dosing time notification mail generated in step S15 and stores it in the mail data storage area of mail information storage device 118 (step S16). Then, the CPU 110 registers the file name assigned in step S16 in the mail transmission schedule information stored in the mail transmission schedule storage area of the mail information storage device 118 (step S17). Here, the file name is associated with the patient ID registered in the mail transmission schedule information in step S8 of FIG. 9, and the taking time notification mail of the text data is transmitted at 7:00 am. It is registered in the mail transmission schedule information so that it can be identified. That is, to explain along the contents of the mail transmission schedule information shown in FIG. 7, the file name given in step S15 is the “7:00” column of the item “transmission time” in the row of the corresponding patient ID. Will be registered.

  Next, CPU 110 includes, based on the notification time designation information read out in step S13, whether or not a medicine ID to which a medication time notification mail is to be transmitted is included among the medicine IDs stored in work RAM 112. Is determined (step S18). Here, in step S14 described above, the medicine ID stored in the work RAM 112 did not include the medicine ID for which the medication time notification mail should be transmitted at 7:00 am (that is, the notification time designation information shown in FIG. 6). If there is no medicine for which the 7:00 item is “1”), the determination result in step S14 is NO, and the process proceeds to step S18 without performing the processes in steps S15 to S17.

  In step S18, there is a medicine whose medicine ID to which a medication time notice mail should be transmitted at 12:00 pm (that is, there is a medicine in which the item of 12:00 of the notice time designation information shown in FIG. 6 is “1”). ), The determination result in step S18 is YES, and the CPU 110 determines the type of drug ID to which a medication time notification mail is to be transmitted at 12:00 pm and the type of drug ID to which a medication time notification email is to be transmitted at 7:00 am. Comparison is made and it is determined whether or not all match (step S19). If they all match, the file name given to the taking time notification mail generated in step S15 is registered in the “12:00” field of the item “transmission time” in the mail transmission schedule information shown in FIG. S20). That is, in this case, the same file name is registered in the “7:00” and “12:00” fields of the item “transmission time”.

  On the other hand, if the type of drug ID to which the medication time notification mail is to be transmitted at 12:00 pm does not match the type of drug ID to which the medication time notification email is to be transmitted at 7:00 am, the determination result in step S19 is The CPU 110 reads NO from the medicine DB the name of the medicine ID to which the medication time notification mail should be transmitted at 12:00 pm, and, similar to the processing in step S15, of the text of the medication time notification mail that has undergone the processing in step S12 , “& Media1 &” to “& media3 &” are replaced (step S21). Then, CPU 110 assigns a unique file name to the text data of the dosing time notification mail generated in step S21 and stores it in the mail data storage area of mail information storage device 118 (step S22). Next, the CPU 110 registers the file name assigned in step S22 in the mail transmission schedule information stored in the mail transmission schedule storage area of the mail information storage device 118 (step S23). That is, to explain along the contents of the mail transmission schedule information shown in FIG. 7, the file name given in step S22 is the “12:00” field of the item “transmission time” in the row of the corresponding patient ID. Will be registered.

  Next, CPU 110 includes, based on the notification time designation information read out in step S13, whether or not a medicine ID to which a medication time notification mail is to be transmitted is included among the medicine IDs stored in work RAM 112 at 7:00 pm. Is determined (step S24). Here, in step S18 described above, the medicine ID stored in the work RAM 112 did not include the medicine ID to which the medication time notification mail should be transmitted at 12:00 pm (that is, the notification time designation information shown in FIG. 6). If there is no medicine whose 12:00 item is “1”), the determination result in step S18 is NO, and the process proceeds to step S24 without performing the processes in steps S19 to S23. Further, when the process of step S20 described above is completed, the CPU 110 directly proceeds to the process of step S24.

  In step S24, the medicine ID for which the medication time notification mail is to be transmitted at 7:00 pm is not included (that is, all items at 19:00 in the notification time designation information shown in FIG. 6 are “0”). The determination result in step S24 is NO, and the CPU 110 ends the taking time notification mail generation process shown in FIG. 10, and clears various data temporarily stored in the work RAM 112 in the process of performing the processes shown in FIGS. After that, the process returns to step S1 in the chart / prescription data registration process shown in FIG. In contrast, a medicine ID for which a medication time notification mail should be transmitted at 7:00 pm is included (that is, a medicine whose item of 19:00 in the notification time designation information shown in FIG. 6 is “1”). If YES, the determination result in step S24 is YES, and the CPU 110 determines the type of drug ID to which the medication time notification mail is to be transmitted at 7:00 pm and the type of drug ID to which the medication time notification email is to be transmitted at 7:00 am. Are compared to determine whether or not they all match (step S25). If they all match, the file name given to the taking time notification mail generated in step S15 is registered in the “19:00” field of the item “transmission time” in the mail transmission schedule information shown in FIG. (Step S26). That is, in this case, the same file name is registered in the “7:00” and “19:00” fields of the item “transmission time”. Then, when the process of step S26 is completed, the CPU 110 ends the taking time notification mail generation process shown in FIG. 10, and clears various data temporarily stored in the work RAM 112 in the process of performing the processes shown in FIGS. Thereafter, the process returns to step S1 in the medical record / prescription data registration process shown in FIG.

  Further, if the type of the medicine ID to which the medication time notification mail is to be transmitted at 7:00 pm does not match the type of the medicine ID to which the medication time notification email is to be transmitted at 7:00 am, the determination result in step S25 is NO, CPU110 compares the kind of medicine ID which should send a taking time information mail at 7:00 pm, and the kind of medicine ID which should send a medicine time information mail at 12:00 pm, and judges whether all are in agreement ( Step S27). If all of them match, the file name given to the taking time notification mail generated in step S21 is registered in the “19:00” field of the item “transmission time” in the mail transmission schedule information shown in FIG. (Step S28). That is, in this case, the same file name is registered in the “12:00” field and the “19:00” field of the item “transmission time”. When the processing of step S28 is completed, the CPU 110 clears various data temporarily stored in the work RAM 112 in the course of performing the processing shown in FIGS. 9 and 10, and then in the medical record / prescription data registration processing shown in FIG. The process returns to step S1.

  On the other hand, if the type of medication ID to which the medication time notification email is to be transmitted at 7 pm does not match the type of medication ID to which the medication time notification email is to be transmitted at 12:00 pm, the determination result in step S27 is NO, The CPU 110 reads from the medicine DB the name of the medicine ID to which the medication time notification mail is to be transmitted at 7:00 pm, and, in the same manner as the process of step S15, among the texts of the medication time notification mail that has undergone the process of step S12, “& media1 &” ˜ The character string “& medi3 &” is replaced with the name of the medicine read from the medicine DB (step S29). Then, CPU 110 assigns a unique file name to the text data of the dosing time notification mail generated in step S29 and stores it in the mail data storage area of mail information storage device 118 (step S30). Next, the CPU 110 registers the file name assigned in step S30 in the mail transmission schedule information stored in the mail transmission schedule storage area of the mail information storage device 118 (step S31). That is, to explain along the contents of the mail transmission schedule information shown in FIG. 7, the file name given in step S30 is the “19:00” field of the item “transmission time” in the row of the corresponding patient ID. Will be registered. When the processing of step S31 is completed, the CPU 110 clears various data temporarily stored in the work RAM 112 in the process of performing the processing shown in FIGS. 9 and 10, and then in the medical record / prescription data registration processing shown in FIG. The process returns to step S1.

  As described above, in the medical service providing system according to the present embodiment, the name of the medicine prescribed for each patient is inserted into the text information of the dosing time notification mail shown in FIG. 8B and transmitted to each patient. A dosing time notification email is generated. In addition, the name of the medicine corresponding to the transmission time of the dosing time notification mail and the dosing time is inserted in the text of the dosing time notification mail. Therefore, CPU110 which performs the dosing time notification mail generation process (that is, the dosing time notification mail generation process shown in FIG. 10) in step S9 in FIG. 9 corresponds to a notification mail generation unit.

  Next, with reference to the flowchart shown in FIG. 11, the flow of the dose end notification mail transmission process for transmitting the dose end notification email generated in step S6 of FIG. 9 will be described. The dosing end notification mail transmission process shown in FIG. 11 is a process executed once a day from the end time of the office work in the hospital 1 shown in FIG. 1 to the start time of the next day's office work. In the present embodiment, it is assumed that the dosing end notification mail transmission process shown in FIG. 11 is executed at midnight when the date is changed.

  When the CPU 110 starts the dosing end notification mail transmission process shown in FIG. 11, first, current calendar information is acquired from the RTC 113 shown in FIG. 2 (step S40). Next, in the patient ID registered in the mail transmission schedule information shown in FIG. 7, the CPU 110 has a blank “dose end notification mail transmission date” column (that is, a dose end notification mail has not been transmitted yet). Information indicating the dose end date corresponding to the patient ID is read (step S41), and it is determined whether or not the read dose end date is two days before the current date (step S42). For example, in the case of the mail transmission schedule information shown in FIG. 7, the dose end date of the patient ID “n9xy4gqw” is read. If the read end date is two days before the current date, the determination result in step S42 is YES, and the CPU 110 reads the mail address of the patient ID from the mail transmission schedule information (step S43). ). Next, the CPU 110 reads the text data of the medication end notification mail corresponding to the patient ID generated by the process of step S6 of FIG. 9 from the mail data storage area of the mail information storage device 118 (step S44).

  Then, the CPU 110 sends the text e-mail read out in step S44 (that is, the dosing end notice mail) from the LAN card 116 to the mail address read in step S43, with the subject as “dosing end notice mail”. Transmission is performed via the LAN 10, the router 13, and the Internet 5 (step S45). As described above, in step S42, when it is determined that the patient's dose end date is two days before the current date, a dose end notification mail is transmitted to the patient by the process of step S45. Therefore, the CPU 110 that performs the process of step S42 corresponds to a notification mail transmission determination unit, and the CPU 110 that performs the process of step S45 corresponds to a mail transmission unit.

  Next, when the CPU 110 transmits the medication end notification email by the process of step S45, the date of transmission of the medication end notification email is displayed in the “sent end notification email transmission date” column of the email transmission schedule information shown in FIG. Then, registration is performed in association with the patient ID of the destination patient (step S46). And it is judged whether processing of Step S42 was performed about all patient ID which has not transmitted a dose end notice mail among patient ID registered into mail transmission schedule information (Step S47). When the process of step S42 has not been performed for all of the patients who have not sent the dose end notification mail, the determination result of step S47 is NO, the process proceeds to step S41, and the CPU 110 notifies the dose end notification. The dose end date associated with the next patient ID that has not transmitted mail (for example, in the case of the mail transmission schedule information shown in FIG. 7, patient ID “3drpm6iw”) is read, and the processing from step S42 is performed. And if the process of step S42 is performed about all the patients who have not transmitted the dose completion notification mail, the judgment result of step S47 will be YES and the dose end notification mail transmission process shown in FIG. 11 will be complete | finished.

  Next, with reference to the flowchart shown in FIG. 12, the flow of the dosing time notification mail transmission process for transmitting the dosing time notification mail generated in step S9 of FIG. 9 will be described. In FIG. 12, the CPU 110 acquires current calendar information from the RTC 113 (step S50). Then, the CPU 110 determines whether the current time is 7 am, 12 pm, or 7 pm (steps S51 to S53). If the current time is neither 7:00 am, 12:00 pm, or 7:00 pm, the determination results in steps S51 to S53 are all NO, and the CPU 110 proceeds to the process in step S50. The current calendar information is acquired again from the RTC 113. On the other hand, if the current time is 7:00 am, the determination result in step S51 is YES, and the CPU 110 transmits the “transmission” associated with each patient ID in the mail transmission schedule information shown in FIG. When the file name is registered in the “7:00” column of the item “time”, the text data of the file name is read from the mail data storage area of the mail information storage device 118. Then, the read text data is transmitted to the mail address of the patient ID corresponding to the text data (step S54).

  If the current time is 12:00 pm, the determination result in step S52 is YES, and the CPU 110 refers to the “transmission time” associated with each patient ID in the mail transmission schedule information shown in FIG. When the file name is registered in the “12:00” column of the item, the text data of the file name is read from the mail data storage area of the mail information storage device 118. Then, the read text data is transmitted to the mail address of the patient ID corresponding to the text data (step S55). Further, if the current time is 7 pm, the determination result in step S53 is YES, and the CPU 110 refers to “transmission time” associated with each patient ID in the mail transmission schedule information shown in FIG. When the file name is registered in the “19:00” column of the item, the text data of the file name is read from the mail data storage area of the mail information storage device 118. Then, the read text data is transmitted to the mail address of the patient ID corresponding to the text data (step S56). Then, after completing any of the processes of steps S54 to S56, the CPU 110 proceeds to the process of step S50, acquires the current calendar information from the RTC 113 again, and thereafter executes the processes of steps S51 to S56. .

  As described above, in the medical service providing system according to the present embodiment, when the current time is 7 am, 12 pm, or 7 pm by the processing of steps S51 to S53, the time is changed according to the time. Then, any one of steps S54 to S56 is executed. As a result, the dosing time notification mail corresponding to the current time is read out of the dosing time notification emails generated in accordance with each time described above by the dosing time notification email generation process shown in FIG. Sent to the patient's email address corresponding to the time notification email. Therefore, the CPU 110 that executes the processes of steps S51 to S53 corresponds to notification mail transmission determining means, and the CPU 110 that executes the processes of steps S54 to S56 corresponds to mail transmitting means.

  Next, referring to the flowchart shown in FIG. 13, in response to the medication end notification mail sent to each patient by the medication end notification email transmission process shown in FIG. A flow of a reply mail check process for checking whether or not a mail has been sent will be described. In addition, the medical service provision system in this embodiment shall perform the reply mail check process shown in FIG. 13 with a predetermined period.

  In FIG. 13, the CPU 110 first receives an e-mail sent to the hospital 1 from a mail server of a provider (not shown) connected to the Internet 5 via the router 13 and the LAN 10 by the LAN card 116. The data is stored in the mail data storage area of the mail information storage device 118 (step S60). Then, CPU 110 determines whether or not the character string “dosing end notification mail” is included in the subject among the received mails stored in the mail data storage area of mail information storage device 118 (step S61). That is, in the medical service providing system according to the present embodiment, among the received e-mails, an e-mail whose subject includes the character string “dose end notification mail” is treated as a reply mail to the dose end notification mail. Yes.

  In general, when a reply operation is performed on an email received while the mobile phone 2 is displaying the email, the subject of the email being displayed is included in the subject of the reply email. Therefore, since the subject of the medication end notification email transmitted to each patient by the process of step S45 in FIG. 11 is “medication termination notification email”, the medication termination notification email shown in FIG. 8A is received. When the patient performs a reply operation to the mail while displaying the dose end notification mail received by the mobile phone 2 in accordance with the text of the mail, the subject line of the reply mail includes the character string “dose end notification mail” It will be. As a result, in the medical service providing system according to the present embodiment, when the character string “dose end notification mail” is included in the subject of the received e-mail, it is treated as a reply mail to the sent dose end notification mail. .

  Then, in the received e-mail, when there is no person whose subject includes the character string of “dose end notification mail”, the determination result in step S61 is NO, and the reply mail check process shown in FIG. 13 is performed. finish. On the other hand, if there is an e-mail that includes the character string “dosing end notice mail” in the subject, the determination result in step S61 is YES, and the CPU 110 is the sender of the e-mail. It is determined whether or not the mail address is registered in the mail transmission schedule information shown in FIG. 7 (step S62). If the e-mail address representing the sender of the e-mail is not registered in the e-mail transmission schedule information, the determination result in step S62 is NO, and the reply e-mail check process shown in FIG. 13 is terminated. . On the other hand, if the mail address representing the sender of the electronic mail is registered in the mail transmission schedule information, the determination result in step S62 is YES, and the CPU 110 displays the mail transmission schedule information shown in FIG. In FIG. 13, after updating the value (initial value is “0”) of the “reply mail” field of the patient ID corresponding to the mail address to “1” (step S63), the reply mail check process shown in FIG. To do.

  Next, referring to the flowchart shown in FIG. 14, the clerk in charge of the hospital 1 according to the presence / absence of a reply mail from the patient in response to the dose end notification mail transmitted by the dose end notification mail transmission process shown in FIG. 11. The flow of alarm processing for calling attention to will be described. The medical service providing system according to the present embodiment executes this alarm processing once a day when the start time of office work in the hospital 1 is reached.

  First, after obtaining the current calendar information from the RTC 113 (step S70), the CPU 110 selects the patient ID registered at the top of the patient IDs registered in the mail transmission schedule information shown in FIG. The dose end date is read (step S71), and the read dose end date is compared with the current calendar information to determine whether the dates match, that is, whether the read dose end date has been reached (step S71). Step S72). If the read end date coincides with the date indicated by the current calendar information, the determination result in step S72 is YES, and the CPU 110 sets the value in the “reply mail” column corresponding to the patient ID to “1”. It is determined whether or not a reply mail is received from the patient (step S73). Thereby, CPU110 which performs the process of step S73 is equivalent to a reply mail determination means.

  In step S73, if the value in the “reply mail” field corresponding to the patient ID is “0” (that is, no reply mail is received), the determination result in step S73 is NO, and the CPU 110 The patient's name corresponding to the ID is read from the patient DB, and a message is displayed on the display 115 indicating that the patient ID, the patient's name, and the medication end notification email have been sent but no reply email has been sent ( Step S74). Thereby, CPU110 which performs the process of step S74 respond | corresponds to a reply non-reception notification means. Next, the CPU 110 accesses the reservation DB and determines whether or not a diagnosis reservation for the patient ID is registered (step S75). Thereby, CPU110 which performs the process of step S75 is equivalent to a reservation information confirmation means.

  When the appointment reservation for the patient ID is registered in the reservation DB, the determination result in step S75 is YES, and the CPU 110 displays the patient ID, the patient's name, and the dose end displayed on the display 115 in step S74. In addition to the message that the notification mail is transmitted but the reply mail is not sent, a message that the examination reservation is made is displayed (step S76). On the other hand, when the appointment reservation for the patient ID is not registered in the appointment DB, the determination result in step S75 is NO, and the CPU 110 displays the patient ID, the patient's name, the patient ID displayed on the display 115 in step S74. Further, in addition to the message indicating that the medication end notification mail has been transmitted but the reply mail has not been sent, a message indicating that the examination reservation has not been made is displayed (step S77). Therefore, CPU110 which performs the process of step S77 is equivalent to a reservation non-registration notification means.

  When the process of step S76 or S77 described above is completed, CPU 110 determines whether or not the determinations of steps S72 and S73 have been made for all of the patient IDs registered in the mail transmission schedule information shown in FIG. Step S78). If the determinations in steps S72 and S73 have not been made for all patient IDs, the determination result in step S78 is NO, and the CPU 110 returns to the process in step S71 and is registered in the mail transmission schedule information shown in FIG. The next dose end date of the next patient ID is read out, and the processing from step S72 is performed. And if the process of step S72, S73 is performed about all patient IDs, the judgment result in step S78 will be YES, and CPU110 will complete | finish the alarm process shown in FIG.

  In the process of step S72 described above, if the dose end date read from the mail transmission schedule information does not match the date indicated by the current calendar information, the determination result of step S72 is NO, and the CPU 110 Then, the process proceeds to step S78, and it is determined whether or not the processes in steps S72 and S73 have been performed for all patient IDs. In step S73, if a reply mail is received from the patient corresponding to the patient ID, the determination result in step S73 is YES, and the data related to the patient ID is obtained from the mail transmission schedule information shown in FIG. Delete (step S79). When the process of step S79 is completed, the CPU 110 proceeds to the process of step S78 and determines whether or not the processes of steps S72 and S73 have been performed for all patient IDs.

  According to the medical service providing system described above, when a patient's medical record / prescription data is transmitted from the personal computers 12a and 12b installed in each examination room in the hospital 1 to the in-hospital server 11 via the LAN 10, the in-hospital server 11 executes the medical chart / prescription data registration process shown in FIG. 9, and registers the received medical chart / prescription data in the medical chart / prescription DB stored in the database information storage device 117 of the hospital server 11 ( Step S3). Further, at this time, the CPU 110 calculates the medication end date of the medicine prescribed to the patient based on the received medical record / prescription data (step S5), and notifies the patient that the medication end date is approaching. Is generated (step S6). This dosing end notice mail is stored in the mail data storage area of the mail information storage device 118 (step S7), and when it is midnight, the CPU 110 performs the dosing end notice mail transmission process shown in FIG. Among the patients, a dose completion notification mail of a patient who is two days before the dose end date (step S42, YES) is read from the mail information storage device 118 (step S44) and transmitted to the patient (step S45). ).

  As a result, the patient who has received the above-mentioned medication end notification email by the mobile phone 2 can know that the end of the medication period is approaching, and the next examination will be performed according to the physical condition at that time. Can be used as an opportunity to determine whether or not to make a reservation. Therefore, the medical service providing system according to the present embodiment can provide services related to care after diagnosis to the patient.

  Further, the CPU 110 of the in-hospital server 11 executes the reply mail check process shown in FIG. 13 for each predetermined period, and determines whether or not a reply mail for the dosing end notice mail transmitted to each patient has been received. To check. And when it becomes the start time of the office work of the hospital, the CPU 110 executes the alarm process shown in FIG. 14, and when the reply mail from the patient who sent the dosing end notice mail is not received (step S73, NO), A message indicating that the patient's ID, name, and reply mail have not been received is displayed on display 115 (step S74). As a result, the person in charge at the hospital 1 can quickly detect that there is no response to the medication end notification email sent to the patient, and promptly take measures such as confirming the condition of the patient. Can do.

  In the alarm processing shown in FIG. 14, the CPU 110 determines whether or not the patient reservation information is registered in the reservation DB stored in the database information storage device 117 (step S75). If the information is not registered, a notification to that effect is given (step S77). As a result, if no reply email has been sent from the patient and the patient has not made an appointment for the next medical examination, the person in charge of the hospital 1 can be informed of this quickly. A person can quickly take measures such as checking the condition of the patient.

  Furthermore, CPU110 produces | generates the dosing time alerting | reporting mail which encourages each patient to take the medicine prescribed | regulated by performing the medical chart / prescription data registration process shown in FIG. 9 (step S9). The content of the medication time notification email generated at this time is roughly the name of the medicine to be taken according to the time (7:00, 12:00, 19:00) of taking the medicine prescribed for each patient. Is described (FIG. 10, steps S14 to S31). Then, CPU 110 repeatedly executes the dosing time notification mail transmission process shown in FIG. 12, and when any time of 7:00, 12:00, or 19:00 is reached (any of steps S51 to S53 is YES). ), A dosing time notification mail corresponding to each time is transmitted to the mobile phone 2 of each patient (steps S54 to S56). As a result, the patient who has received the taking time notification e-mail can know that the time for taking the medicine has come or has approached, so the possibility that the patient will forget to take the medicine may be reduced. it can.

  In the medical service providing system described above, in the alarm process shown in FIG. 14, the processes of (1) step S72, (2) steps S73, S74, S79, and (3) steps S75 to S77 were performed. However, any one of the processes (1) to (3) may be omitted. Further, step S9 in FIG. 9 (that is, the taking time notification mail generation process in FIG. 10) may be omitted.

It is explanatory drawing for demonstrating the whole structure of the medical service provision system in embodiment of this invention. It is a block diagram which shows the structure of the hospital server which makes a part of the medical service provision system. It is explanatory drawing for demonstrating the content of the data memorize | stored in the patient database stored in the database information storage apparatus with which the same hospital server is equipped. It is explanatory drawing for demonstrating the content of the data memorize | stored in the reservation database stored in the database information storage apparatus with which the same hospital server is provided. It is explanatory drawing for demonstrating the content of the data memorize | stored in the medical chart / prescription database stored in the database information storage apparatus with which the hospital server is equipped. It is explanatory drawing for demonstrating the content of the data memorize | stored in the chemical | medical agent database stored in the database information storage device with which the same hospital server is equipped. It is explanatory drawing for demonstrating the content of the mail transmission schedule information stored in the mail information storage device with which the hospital server is provided. It is explanatory drawing for demonstrating the content of the mail text information stored in the mail information storage device with which the hospital server is provided. It is a flowchart which shows the flow of the medical chart / prescription data registration process which CPU of the hospital server performs. It is a flowchart which shows the flow of the dosing time alerting | reporting mail generation process which CPU of the same hospital server performs. It is a flowchart which shows the flow of the dose completion notification mail transmission process which CPU of the hospital server performs. It is a flowchart which shows the flow of the dosing time alerting | reporting mail transmission process which CPU of the hospital server performs. It is a flowchart which shows the flow of the reply mail check process which CPU of the same hospital server performs. It is a flowchart which shows the flow of the alarm process which CPU of the same hospital server performs.

Explanation of symbols

1 Hospital 2 Mobile phone 3 Pharmacy 4 Base station 5 Internet 10 LAN
11 Hospital servers 12a and 12b Personal computer 13 Router 110 Display 111 ROM
112 Work RAM
113 Real Time Clock 114 Keyboard 115 Display 116 LAN Card 117 Database Information Storage Device 118 Mail Information Storage Device

Claims (4)

A medical service providing system that provides services related to care after examination to a patient,
A timekeeping means that constantly measures time and generates calendar information representing the current date and time;
A notification mail storage means for storing character string information indicating the text of an e-mail notifying that the medication period has ended;
Patient information storage means for storing unique patient identification information assigned to each of the plurality of patients, and at least transmission destination information indicating an email transmission destination of the patient corresponding to the patient identification information;
Prescription information storage for storing prescription information including information on the date of examination for the patient and the name, dose, usage, and quantity of the medicine prescribed on the examination date in association with the patient identification information given to the patient Means,
A notification mail generating means for generating a dose completion notification mail by incorporating prescription information unique to the patient stored in the prescription information storage means into the character string information stored in the notification mail storage means;
An end date calculating means for calculating a medication period end date of the medicine prescribed to the patient specified by the patient identification information associated with the prescription information based on the prescription information stored in the prescription information storage means; ,
Based on the calendar information generated by the time measuring means and the dose period end date calculated by the end date calculating means, it is determined whether or not to send the dose end notification mail generated by the notification mail generation means. Notification email transmission decision means,
When the notification mail transmission determining unit determines to transmit the dosing end notification mail, the mail sending unit transmits the dosing end notification mail according to the transmission destination information of the patient stored in the patient information storage unit. A medical service providing system comprising: A mail receiving means for receiving e-mails sent from outside;
A reply mail judging means for judging whether or not the mail receiving means has received a reply mail to the medication end notification mail from the patient who has sent the medication end notice mail by the mail sending means;
The response mail determining means comprises: a response non-reception notifying means for notifying that when the mail receiving means determines that the reply mail has not been received from the patient. The medical service provision system described. Reservation information storage means for storing reservation information including information related to the appointment date and time of the patient in association with the patient identification information given to the patient;
Reservation information confirmation means for determining whether or not the reservation information of the patient to whom the dose completion notification mail has been transmitted by the mail transmission means is stored in the reservation information storage means;
A reservation non-registration notification means for notifying the reservation information confirmation means that the reservation information of the patient who has sent the dosing end notification email is not stored in the reservation information storage means; The medical service providing system according to claim 1, wherein: Notification mail storage means for storing character string information indicating the text of an e-mail prompting the patient to take medicine;
Incorporating prescription information unique to the patient stored in the prescription information storage means into the character string information stored in the notification mail storage means, notification mail generation means for generating a dosing time notification mail;
Notification mail transmission determining means for determining whether or not to transmit the dosing time notification mail generated by the notification mail generation means based on the calendar information generated by the time counting means and the prescription information. ,
The mail generation means
When the notification mail transmission determining means determines to transmit the dosing time notification mail, the dosing time notification mail is transmitted according to the transmission destination information of the patient stored in the patient information storage means. The medical service providing system according to any one of claims 1 to 3.

Images