JP6561526B2 - Program, information processing apparatus and information processing method - Google Patents

Description

  The present invention relates to a program, an information processing apparatus, and an information processing method.

2. Description of the Related Art Conventionally, there is known a medication information management system in which a patient himself obtains medication information and can confirm whether or not the patient has taken the medication at a date and time determined by a doctor.
(For example, refer to Patent Documents 1 and 2).

Japanese Patent Laid-Open No. 10-201827 Japanese Unexamined Patent Publication No. 2009-100855

  However, there is a problem that the effect of the prescribed medicine cannot be grasped by the conventional technique.

  In one aspect, an object is to provide a program or the like that can grasp the effect of a drug prescribed to a patient.

The computer accepts the setting of the timing for confirming the effect accompanying the medication of the medicine prescribed to the patient, and at the timing, transmits a message for inquiring about the effect of the medicine to the patient's terminal, from the patient's terminal. When a response indicating that there is no effect associated with taking a drug is received, when information regarding a medical appointment is output to the patient's terminal and a response indicating that there is no effect associated with taking the drug is received from the patient's terminal Then, it is determined whether or not there is a medical appointment, and if it is determined that there is a medical appointment, a process for canceling the medical appointment is executed.

  It becomes possible to grasp the effect of the medicine prescribed to the patient.

It is a block diagram showing the outline of an information processing system. It is a block diagram which shows the hardware group of a doctor computer. It is explanatory drawing which shows the record layout of patient DB. It is explanatory drawing which shows the record layout of medical chart DB. It is a block diagram which shows the hardware group of a portable terminal. It is a block diagram which shows the hardware group of a server computer. It is explanatory drawing which shows the record layout of patient DB of a server computer. It is explanatory drawing which shows the record layout of medical chart DB of a server computer. It is explanatory drawing which shows the record layout of the medication DB which a server computer has. It is explanatory drawing which shows the input image of medication completion information. It is explanatory drawing which shows the display image in which the message was displayed on the display part of the portable terminal. It is explanatory drawing which shows the display image of the information regarding a medical examination reservation displayed on the display part of a portable terminal. It is a flowchart which shows the registration procedure of a timing value. It is a flowchart which shows the output processing procedure of the information regarding a medical examination reservation. It is a flowchart which shows the output processing procedure of the information regarding a medical examination reservation. 6 is a block diagram illustrating an overview of an information processing system according to Embodiment 2. FIG. FIG. 10 is a block diagram illustrating a hardware group of a server computer in a second embodiment. It is explanatory drawing which shows the record layout of beacon DB. It is a flowchart which shows the procedure of an installation process. It is a flowchart which shows the procedure of an installation process. It is a flowchart which shows the procedure of an installation process. It is a flowchart which shows the procedure of an installation process. FIG. 10 is a block diagram illustrating a hardware group of a doctor computer according to a fourth embodiment. FIG. 10 is a block diagram illustrating a hardware group of a server computer according to a fourth embodiment. It is explanatory drawing which shows the record layout of reservation DB of a doctor computer. It is explanatory drawing which shows the record layout of reservation DB of a server computer. It is explanatory drawing which shows the image of the reservation reception screen displayed on the display part of a portable terminal. It is a flowchart which shows the procedure of a reservation process. It is a flowchart which shows the procedure of a reservation process. It is a flowchart which shows the procedure of a reservation process. It is a flowchart which shows the procedure of a reservation process. It is explanatory drawing which shows the record layout of reservation DB. It is explanatory drawing which shows the record layout of reservation DB. It is a flowchart which shows the procedure of a deletion process. It is a flowchart which shows the procedure of a deletion process. It is a flowchart which shows the procedure of a deletion process. It is a flowchart which shows the procedure of a deletion process. It is a functional block diagram which shows operation | movement of the server computer and doctor computer of the form mentioned above. FIG. 20 is a block diagram illustrating a hardware group of a server computer according to an eighth embodiment.

Embodiment 1
Hereinafter, embodiments will be described with reference to the drawings. FIG. 1 is a block diagram showing an outline of an information processing system. The information processing system includes a first computer 1, an information processing device 2, a second computer 3, and the like. The first computer 1, the information processing apparatus 2, and the second computer 3 are connected to each other via a communication network N such as the Internet, a public telephone network, and a LAN (Local Area Network). The second computer 3 is, for example, a server computer, a personal computer, a PDA (Personal Digital Assistant), a smartphone, or the like provided in a medical facility such as a hospital or a pharmacy. Hereinafter, the second computer 3 is referred to as a doctor computer 3.

  The first computer 1 is a server computer or a personal computer that transmits and receives information to and from the above-described doctor computer 3. Hereinafter, the first computer 1 is referred to as a server computer 1. In the present embodiment, the first computer 1 and the second computer 3 are separated, but may be integrated into any one of them. The information processing apparatus 2 is a personal computer, a mobile phone, a PDA, a smartphone, a camera, a game machine, or the like. Below, the information processing apparatus 2 is demonstrated as what is the portable terminal 2. FIG. When prescribing the medicine to the patient, the doctor inputs information (hereinafter, sometimes referred to as a timing value) for timing for confirming the effect of taking the medicine to the doctor computer 3.

  The doctor computer 3 outputs a timing value input from a doctor who is a user to the server computer 1. The server computer 1 acquires the timing value output from the doctor computer 3. Further, the server computer 1 refers to the patient's medication status by means of a medical chart DB, which will be described later, and uses the timing value acquired from the doctor computer 3 to transmit a message for inquiring the effect of the medication to the patient's portable terminal 2. The portable terminal 2 displays a message asking whether or not the medication has been effective, such as “Did the fever fall?”. Here, when the server computer 1 receives an answer indicating that there is no effect, specifically, that the heat does not decrease due to the medication, the server computer 1 outputs information related to the examination appointment to the portable terminal 2. Details will be described below.

  FIG. 2 is a block diagram showing a hardware group of the doctor computer 3. The doctor computer 3 includes a CPU (Central Processing Unit) 31 as a control unit, a RAM (Random Access Memory) 32, an input unit 33, a display unit 34, a storage unit 35, a communication unit 36, and the like. The CPU 31 is connected to each part of the hardware via the bus 37. The CPU 31 controls each part of the hardware according to the control program 35P stored in the storage unit 35. The RAM 32 is, for example, SRAM (Static RAM), DRAM (Dynamic RAM), flash memory, or the like. The RAM 32 also functions as a storage unit, and temporarily stores various data generated when the CPU 31 executes various programs.

  The input unit 33 is an input device such as a mouse or a keyboard, a mouse or a touch panel, and outputs received operation information to the CPU 31. The display unit 34 is a liquid crystal display, an organic EL (electroluminescence) display, or the like, and displays various information according to instructions from the CPU 31. The communication unit 36 is a communication module, and transmits / receives information to / from the server computer 1 or the portable terminal 2 via the communication network N such as the Internet.

  The storage unit 35 is a hard disk or a large-capacity memory, and includes a control program 35P, a patient database (hereinafter referred to as DB) 351, a medical chart DB 352, and the like. In addition, although embodiment gave patient DB351 etc. in the example which memorize | stored in the memory | storage part 35, it does not restrict to this. In addition to being stored in the RAM 32, it may be stored in another DB server (not shown).

  FIG. 3 is an explanatory diagram showing a record layout of the patient DB 351. The patient DB 351 includes a patient ID field, a patient name field, a patient terminal ID field, and the like. In the patient ID field, unique identification information (hereinafter referred to as a patient ID) for specifying a patient who has visited for medical examination is stored. The patient name corresponding to the patient ID is stored in the patient name field. In the patient terminal ID field, unique identification information (hereinafter referred to as “patient terminal ID”) for specifying the portable terminal 2 of the patient is stored in association with the patient ID. The patient terminal ID is, for example, an e-mail address, an IP (Internet Protocol) address, or a MAC (Media Access Control) address.

  FIG. 4 is an explanatory diagram showing a record layout of the medical record DB 352. The medical record DB 352 includes a patient ID field, an examination date field, a disease name field, a prescription drug field, a prescription field, a timing field, a message field, a reply field, and the like. In the examination date field, the date and time when the patient was examined is stored in association with the patient ID. In order to simplify the description, only the year, month, and day are shown, but hours, minutes, and seconds may be stored. In the disease name field, a disease name is stored in association with the patient ID. In the prescription drug field, a drug prescribed to the patient is stored in association with the patient ID.

  In the prescription field, a period for prescribing the medicine is stored. In the example of FIG. 4 where the patient ID is 98374, the drug “XXX” is prescribed for 3 days. In the embodiment, for ease of explanation, only the number of days is stored as a prescription, but the present invention is not limited to this. In addition to the number of days, more specific prescription contents such as the prescription time, the number of times, the number of tablets, etc. after each meal and before meals may be stored. The doctor inputs a disease name, prescription drugs, prescription contents, and the like from the input unit 33 of the doctor computer 3. The CPU 31 stores the input data in the medical record DB 352.

  The timing field stores the timing at which the notification message is transmitted to the patient in association with the patient ID. When a plurality of medicines are prescribed, a plurality of timings may be stored in association with the patient ID and the medicine. In the example of the patient ID of 98374 in FIG. 4, 4 is stored in the timing field, and this number indicates the number of times of medication. Specifically, a message is transmitted when a patient with patient ID 98374 has taken this medicine four times. In the message field, a message is stored in association with the patient ID. The message has a content indicating whether or not the medication has been effective, and a text sentence such as “Did the fever fall?” Is stored. The doctor inputs a timing value and a message for transmitting a message to the patient from the input unit 33 of the doctor computer 3. The CPU 31 stores the input timing and message in the medical record DB 352.

  In the embodiment, the number of times of medication is given as the timing, but it is not limited to this. The period from the examination such as 3 days or 24 hours later may be the timing for notifying the patient of the message, or the organization from the first medication may be the timing for notifying the patient of the message. The reply field stores the reply contents for the message in association with the patient ID. In the example of FIG. 4, “NO” indicating that there is no effect of medication at a certain timing is stored. If there is a medicinal effect, “YES” information is stored. In the embodiment, the reply contents are indicated by “YES” or “NO” for easy explanation, but the present invention is not limited to this. You may make it memorize text sentences, such as "I am not in good health" and "It has improved very much."

  FIG. 5 is a block diagram showing a hardware group of the mobile terminal 2. The portable terminal 2 includes a CPU 21 as a control unit, an input unit 23, a display unit 24, a storage unit 25, a communication unit 26, a GPS (Global Positioning System) module 28, a short-range communication module 29, and the like. The CPU 21 is connected to each part of the hardware via the bus 27. CPU21 controls each part of hardware according to control program 25P memorized by storage part 25. The storage unit 25 is, for example, an SRAM, DRAM, flash memory, hard disk, or the like. The storage unit 25 temporarily stores various data generated when the CPU 21 executes various programs.

  The input unit 23 is an input device such as a mouse, a keyboard, or a touch panel, and outputs received operation information to the CPU 21. The display unit 24 is a liquid crystal display, an organic EL (electroluminescence) display, or the like, and displays various information according to instructions from the CPU 21. The communication unit 26 is a communication module, and transmits / receives information to / from the server computer 1 or the doctor computer 3 via a communication network N such as the Internet.

  The GPS module 28 acquires position information including latitude and longitude from the satellite. The short-range communication module 29 is, for example, a module that performs communication based on the Bluetooth (registered trademark) standard or an infrared communication module.

  FIG. 6 is a block diagram showing a hardware group of the server computer 1. The server computer 1 includes a CPU 11 as a control unit, a RAM 12, an input unit 13, a display unit 14, a storage unit 15, a clock unit 18, a communication unit 16, and the like. The CPU 11 is connected to each part of the hardware via the bus 17. The CPU 11 controls each part of the hardware according to the control program 15P stored in the storage unit 15. The RAM 12 is, for example, SRAM, DRAM, flash memory or the like. The RAM 12 also functions as a storage unit, and temporarily stores various data generated when the CPU 11 executes various programs.

  The input unit 13 is an input device such as a mouse or a keyboard, a mouse or a touch panel, and outputs received operation information to the CPU 11. The display unit 14 is a liquid crystal display, an organic EL (electroluminescence) display, or the like, and displays various information according to instructions from the CPU 11. The communication unit 16 is a communication module, and transmits / receives information to / from the doctor computer 3 and the portable terminal 2 via the communication network N such as the Internet. The clock unit 18 outputs date and time information to the CPU 11.

  The storage unit 15 is a hard disk or a large-capacity memory, and includes a control program 15P, a patient DB 151, a medical record DB 152, a medication DB 153, and the like. In the embodiment, the example in which the patient DB 151 and the like are stored in the storage unit 15 is described, but the present invention is not limited to this. In addition to being stored in the RAM 12, it may be stored in another DB server (not shown).

  FIG. 7 is an explanatory diagram showing a record layout of the patient DB 151 of the server computer 1. The patient DB 151 stores the patient ID, patient name, patient terminal ID, and the like transmitted from the doctor computer 3 of each hospital in a form associated with the hospital. In the example of FIG. 7, patient IDs of hospital A, hospital B, and hospital C are stored. Since the contents of each record are as in the patient DB 351 included in the doctor computer 3 described above, detailed description is omitted. When the contents of the patient DB 351 are updated, the CPU 31 of the doctor computer 3 transmits the updated contents and identification information for identifying the hospital (hereinafter referred to as a hospital ID) to the server computer 1. The CPU 11 of the server computer 1 updates the stored content of the patient DB 151 based on the updated content and the hospital ID transmitted from the doctor computer 3. Conversely, when the patient DB 151 of the server computer 1 is updated, the patient DB 351 of the doctor computer 3 is updated based on the updated content. As a result, the patient DB corresponding to the hospital X of the patient DB 151 of the server computer 1 has the same contents as the patient DB 351 of the doctor computer 3 existing in the hospital X. In this embodiment, the doctor DB 3 is also provided in the doctor computer 3 in case of a network failure or the like, but it can also be realized by providing only the server computer 1.

  FIG. 8 is an explanatory diagram showing a record layout of the medical record DB 152 of the server computer 1. The medical record DB 152 stores the patient ID, the date of examination, the timing, the message, the presence / absence of a reply, etc. transmitted from the doctor computer 3 of each hospital. In the example of FIG. 8, patient IDs of hospital A, hospital B, and hospital C are stored. Since the contents of each record are the same as the medical record DB 352 included in the doctor computer 3 described above, detailed description is omitted. When the contents of the medical chart DB 352 are updated, the CPU 31 of the doctor computer 3 transmits the updated contents and the hospital ID to the server computer 1. The CPU 11 of the server computer 1 updates the stored content of the medical record DB 152 based on the transmitted update content and hospital ID. Conversely, when the medical record DB 152 of the server computer 1 is updated, the medical record DB 352 of the doctor computer 3 is updated based on the updated contents. As a result, the medical record DB corresponding to the hospital X in the medical record DB 152 of the server computer 1 has the same contents as the medical record DB 352 of the doctor computer 3 existing in the hospital X. Note that this can also be realized by providing the medical record DB only to the server computer 1.

  FIG. 9 is an explanatory diagram showing a record layout of the medication DB 153 that the server computer 1 has. The medication DB 153 includes a patient ID field, a medication date / time field, a total medication frequency field, and the like. The medication date and time field stores the date and time when the patient took the prescribed medicine. When the CPU 11 acquires completion information indicating that the medication has been completed, the CPU 11 stores the date and time when the completion information was acquired in the medication date and time field of the medication DB 153 in association with the patient ID. The total number of times of taking the medicine prescribed in association with the patient ID is stored in the total number of times taken field. The CPU 11 increments the total number of times every time the patient ID and the completion information are acquired.

  FIG. 10 is an explanatory view showing an input image of medication completion information. The CPU 21 of the mobile terminal 2 activates the application stored in the storage unit 25. The CPU 21 reads prescription information received from the server computer 1 or the doctor computer 3 in advance, specifically, prescription drugs and prescription period from the storage unit 25 (not shown), and displays the read information on the display unit 24. In the example of FIG. 10, patient ID, prescription drug, and prescription period are displayed. The CPU 21 also displays information for confirming the current date and time and completion information of the medication on the display unit 24. In the example of FIG. 10, a text sentence for confirming taking such as “Did you take it after dinner?” Is displayed along with the current date and time. The CPU 21 displays a YES button 241 and a NO button 242 on the display unit 24.

  The CPU 21 receives input from the YES button 241 or the NO button 242 through the input unit 23. When the CPU 21 receives an input from the YES button 241, it transmits the patient ID and completion information to the server computer 1. Note that date / time information may also be transmitted. The CPU 11 of the server computer 1 receives the patient ID and completion information. The CPU 11 stores the patient ID, completion information, and current date and time in the medication DB 153. When the input of the NO button 242 is accepted, the same processing is performed after a predetermined period (30 minutes) has elapsed, and information for inputting completion information is displayed on the display unit 24. In addition, although embodiment demonstrates and mentions the form which makes a patient input completion information, it does not restrict to this. In addition, a sensor that detects that the medicine has been taken into the body may be used. In this case, when it is detected that the medicine has melted and the sensor has been taken into the body, the patient ID and completion information are transmitted to the server computer 1.

  When the CPU 11 receives the patient ID and the completion information, the CPU 11 determines whether or not the total number of times of medication has reached the timing value stored in the timing field of the medical chart DB 152. When the CPU 11 determines that the medicine has been reached, the CPU 11 reads a message inquiring about the effect of the medicine from the message field of the medical record DB 152. The CPU 11 refers to the patient terminal ID stored in the patient DB 151 and transmits the read message to the mobile terminal 2.

  FIG. 11 is an explanatory diagram illustrating a display image in which a message is displayed on the display unit 24 of the mobile terminal 2. The CPU 21 displays the received message, the YES button 241 and the NO button 242 on the display unit 24. In the example of FIG. 11, the message “Did the heat fall?” Is displayed as a message. The patient selects either the YES button 241 or the NO button 242 from the input unit 23. The CPU 21 receives input from the YES button 241 or the NO button 242 through the input unit 23. When the CPU 21 accepts the input of the NO button 242, the CPU 21 transmits response information (hereinafter referred to as “ineffective information”) and a patient ID to the effect that there is no effect associated with taking the medicine to the server computer 1. On the other hand, when the input of the YES button 241 is accepted, reply information indicating that there is an effect (hereinafter referred to as effect information) and the patient ID are transmitted to the server computer 1.

  The CPU 11 of the server computer 1 receives ineffective information or effect information. When the CPU 11 receives the ineffective information, the CPU 11 stores NO information in the reply field of the medical record DB 152 in association with the patient ID. When the effect information is received, YES information is stored in the reply field of the medical record DB 152 in association with the patient ID. In the present embodiment, for ease of explanation, an example of receiving YES or NO information is given, but the present invention is not limited to this. You may make it make a patient input a text. In this case, the CPU 11 of the server computer 1 performs a morphological analysis on the transmitted text, and determines whether the input text indicates no effect or an effect. May be. CPU11 reads the information regarding a medical examination reservation from the memory | storage part 15, when ineffective information is received. The CPU 11 refers to the patient terminal ID corresponding to the patient ID and transmits information related to the examination reservation to the mobile terminal 2.

  FIG. 12 is an explanatory diagram showing a display image of information related to a medical appointment displayed on the display unit 24 of the mobile terminal 2. CPU21 displays the information regarding a medical examination reservation on the display part 24, when the information regarding a medical examination reservation is received. In the example of FIG. 12, guidance such as “Please make a medical appointment” is displayed. It is also possible to display a hyperlink for jumping to a consultation appointment Web page. In addition, an SNS (Social Networking Site) may be accessed by clicking a hyperlink. In this case, the patient and the doctor may have a conversation through SNS.

  FIG. 13 is a flowchart showing a timing value registration procedure. The CPU 31 of the doctor computer 3 displays a screen (not shown) on the display unit 34 and receives the patient ID, disease name, prescription drug, prescription, timing value, and message via the input unit 33 (step S131). The CPU 31 stores the received patient ID, examination date, disease name, prescription drug, prescription, timing value, and message in the medical record DB 352 (step S132). CPU31 transmits patient ID, a medical examination date, a disease name, a prescription medicine, prescription, a timing value, and a message to the server computer 1 via the communication part 36 with hospital ID (step S133).

  The CPU 11 of the server computer 1 receives the patient ID, examination date, disease name, prescription drug, prescription, timing value, message, and hospital ID via the communication unit 16 (step S134). The CPU 11 stores the patient ID, examination date, disease name, prescription drug, prescription, timing value, and message in the medical record DB 152 in association with the hospital ID (step S135).

  14 and 15 are flowcharts showing an output processing procedure of information related to a medical appointment. The CPU 21 of the mobile terminal 2 receives input of medication completion information from the input unit 23 (step S141). CPU21 transmits completion information and patient ID to the server computer 1 via the communication part 26 (step S142). The CPU 11 of the server computer 1 receives the patient ID and the completion information via the communication unit 16 (step S143). The CPU 11 records the medication date and time in the medication DB 153, and calculates and stores the total number of times from the past number of medications (step S144).

  The CPU 11 of the server computer 1 reads the timing value from the medical record DB 152 with reference to the patient ID (step S145). The CPU 11 determines whether or not the total number of times has reached the read timing value (step S146). If the CPU 11 determines that the total number of times has not reached the timing value (NO in step S146), the process returns to step S143. When the CPU 11 determines that the total number of times has reached the timing (YES in step S146), the CPU 11 proceeds to step S147.

  When determining that the total number of times has reached the timing, the CPU 11 refers to the patient ID and reads a message from the medical record DB 152 (step S147). CPU11 reads patient terminal ID from patient DB151 (step S148). CPU11 transmits a message to the portable terminal 2 by using patient terminal ID as a destination (step S149). The CPU 21 of the portable terminal 2 receives the message from the server computer 1 and displays the message, the YES button 241 and the NO button 232 on the display unit 24 (step S151).

  The CPU 21 of the mobile terminal 2 receives an input from the YES button 241 or the NO button 242 via the input unit 23. Next, it is determined whether or not the accepted input is an input of the NO button 242 (step S152). If the CPU 21 determines that the input of the YES button 241 has been received (NO in step S152), the process proceeds to step S153. The CPU 21 transmits effect information indicating that there is an effect to the server computer 1 (step S153). The CPU 11 receives effect information (step S154).

  CPU11 memorize | stores YES which shows effect information in the reply field of medical chart DB152 (step S155), and complete | finishes a process after that. CPU21 makes a process transfer to step S156, when ineffective information is received (it is YES at step S152). The CPU 21 transmits ineffective information to the server computer 1 (step S156). The CPU 11 receives ineffective information (step S157). CPU11 reads the information regarding a medical examination reservation (step S158). CPU11 outputs the information regarding a medical examination reservation to the portable terminal 2 (step S159).

  The CPU 21 of the mobile terminal 2 receives information related to the examination reservation from the server computer 1 (step S1510). CPU21 displays the information regarding a medical examination reservation on the display part 24 (step S1511). The CPU 11 of the server computer 1 stores NO as ineffective information in the reply field of the medical record DB 152 in association with the patient ID (step S1512). Thereby, it is possible to promptly examine a patient who has no prescription effect. In addition, by making it possible to set an appropriate timing such as the number of times based on the experience of the doctor, it becomes possible to grasp the patient's situation more accurately.

Embodiment 2
The second embodiment relates to a mode for distributing an application for inputting ineffective information. FIG. 16 is a block diagram showing an outline of the information processing system according to the second embodiment. In addition to the first embodiment, a beacon 4 is provided. The beacon 4 is a communication module based on the Bluetooth standard, for example, and transmits and receives information to and from the short-range communication module 29 of the mobile terminal 2. In the embodiment, an example using Bluetooth is shown, but the present invention is not limited to this. In addition, information may be transmitted and received using RFID (Radio Frequency Identification).

  The beacon 4 is installed, for example, at an entrance of a hospital equipped with a doctor computer 3 or an accounting window. The server computer 1 acquires the notification timing from the doctor computer 3, stores the timing value in association with the patient ID in the medical record DB 152, and then outputs an application installation command via the communication network N. The application is for inputting effect information or ineffective information. When the patient approaches the entrance of the hospital or approaches the accounting window, the application is installed in the mobile terminal 2. Moreover, CPU21 of the portable terminal 2 uninstalls the installed application, when the input of effect information is received.

  FIG. 17 is a block diagram illustrating a hardware group of the server computer 1 according to the second embodiment. The storage unit 15 is further provided with a beacon DB 154. FIG. 18 is an explanatory diagram showing a record layout of the beacon DB 154. The beacon DB 154 includes a hospital name field and a beacon ID field. In association with the hospital name, identification information (hereinafter referred to as a beacon ID) for specifying the beacon 4 installed in the hospital is stored.

  19 and 20 are flowcharts showing the procedure of the installation process. The doctor inputs a timing value and a message from the input unit 33 of the doctor computer 3 in association with the patient ID. The CPU 31 stores the input patient ID, timing value, message, and the like in the medical record DB 352. The CPU 31 transmits the patient ID, timing value, message, and the like to the server computer 1. The CPU 11 of the server computer 1 receives the patient ID, timing value, and message (step S191).

  The CPU 11 stores the received patient ID, timing value, and message in the medical record DB 152 in association with the hospital name (step S192). The CPU 21 of the portable terminal 2 receives the beacon ID transmitted by the beacon 4 via the short-range communication module 29. The CPU 21 transmits the received beacon ID and patient terminal ID to the server computer 1 via the communication unit 26. The beacon 4 may acquire the patient terminal ID of the mobile terminal 2 and transmit the beacon ID and the patient terminal ID to the server computer 1. The server computer 1 acquires a beacon ID and a patient terminal ID (step S193).

  CPU11 refers to beacon DB154 and reads the hospital name corresponding to beacon ID (step S194). CPU11 reads patient ID corresponding to patient terminal ID with reference to patient DB151 corresponding to the read hospital name. CPU11 reads the medical examination date and time corresponding to a hospital name and patient ID from medical chart DB152 (step S195). The CPU 11 determines whether or not a difference obtained by subtracting the examination date from the current time output from the clock unit 18 is within a predetermined time (for example, within 2 hours) (step S196).

  If the CPU 11 determines that it is not within the predetermined time (NO in step S196), the process ends. If the CPU 11 determines that the time is within the predetermined time (YES in step S196), the process proceeds to step S197. The CPU 11 outputs an application installation command (step S197). The CPU 21 of the portable terminal 2 receives an application installation command (step S198). The CPU 21 determines whether or not permission information indicating permission of application installation has been received via the input unit 23 (step S199).

  CPU21 of the portable terminal 2 waits until permission information is received, when permission information is not received from a patient via the display part 24 (it is NO at step S199). If the CPU 21 determines that the permission information has been received (YES in step S199), the process proceeds to step S201. The CPU 21 transmits permission information to the server computer 1 (step S201). CPU11 reads an application from the memory | storage part 15, when permission information is received from the portable terminal 2 (step S202). The CPU 11 distributes the read application to the mobile terminal 2 (step S203).

  The CPU 21 of the mobile terminal 2 receives the distributed application (step S204). CPU21 installs an application in the memory | storage part 25 (step S205). The CPU 21 determines whether effect information has been transmitted via the input unit 23 (step S206). Specifically, the CPU 21 determines whether or not the YES button 241 is clicked on the screen displayed on the display unit 24.

  If the CPU 21 of the portable terminal 2 determines that the effect information has been transmitted (YES in step S206), the application stored in the storage unit 25 is uninstalled. (Step S207). If the CPU 21 determines that the effect information has not been transmitted (NO in step S206), it skips the process of step S207 and ends the series of processes. In the embodiment, an example in which the beacon 4 is used has been described, but the GPS module 28 may be used. In this case, the position information acquired by the GPS 28 module is transmitted to the server computer 1. The server computer 1 reads the hospital name corresponding to the position information. Thereby, since an application is installed, a user's convenience can be improved. In addition, when an answer indicating that there is an effect is obtained, it becomes possible to easily delete an application that is no longer needed.

  The second embodiment is as described above, and the other parts are the same as those of the first embodiment. Therefore, the corresponding parts are denoted by the same reference numerals, and detailed description thereof is omitted.

Embodiment 3
The third embodiment relates to a form in which an application installation instruction is output by the doctor computer 3. 21 and 22 are flowcharts showing the procedure of the installation process. The doctor inputs a timing value and a message in association with the patient ID from the input unit 33. The CPU 31 receives the input patient ID, timing value, message, and the like (step S211). The CPU 31 stores the received patient ID, timing value, message, and the like in the medical record DB 352 (step S212).

  The CPU 21 of the portable terminal 2 receives the beacon ID transmitted by the beacon 4 via the short-range communication module 29. The CPU 21 transmits the received beacon ID and patient terminal ID to the doctor computer 3 via the communication unit 26. The beacon 4 may acquire the patient terminal ID of the portable terminal 2 and transmit the beacon ID and the patient terminal ID to the doctor computer 3. The CPU 31 of the doctor computer 3 acquires a beacon ID and a patient terminal ID (step S213).

  The CPU 31 of the doctor computer 3 refers to the patient DB 351 and reads the patient ID corresponding to the patient terminal ID. CPU31 reads the medical examination date and time corresponding to patient ID from medical chart DB352 (step S214). The CPU 31 determines whether or not a difference obtained by subtracting the examination date and time from the current time output from the clock unit (not shown) is within a predetermined time (for example, within 2 hours) (step S215).

  If the CPU 31 determines that it is not within the predetermined time (NO in step S215), it ends the process. When CPU 31 determines that the time is within the predetermined time (YES in step S215), the process proceeds to step S216. The CPU 31 refers to the patient terminal ID and outputs an application installation command to the portable terminal 2 (step S216). The CPU 21 of the portable terminal 2 receives an application installation command (step S217). The CPU 21 determines whether or not permission information indicating permission of application installation has been received via the input unit 23 (step S218).

  If the CPU 21 of the portable terminal 2 has not received the permission information (NO in step S218), the CPU 21 waits until the permission information is received. If the CPU 21 determines that the permission information has been received (YES in step S218), the process proceeds to step S219. CPU21 transmits permission information to computer 3 for doctors (Step S219). CPU31 reads an application from the memory | storage part 35, when permission information is received (step S221). The CPU 31 distributes the read application to the mobile terminal 2 (step S222).

  The CPU 21 receives the distributed application (step S223). CPU21 installs an application in the memory | storage part 25 (step S224). The CPU 21 determines whether or not effect information has been transmitted via the input unit 23 (step S225). Specifically, the CPU 21 determines whether or not the YES button 241 has been clicked.

  When determining that the effect information has been transmitted (YES in step S225), the CPU 21 uninstalls the application stored in the storage unit 25 (step S226). If the CPU 21 determines that the effect information has not been transmitted (NO in step S225), it skips the process in step S226 and ends the series of processes. Thereby, since an application is installed, a user's convenience can be improved. In addition, when an answer indicating that there is an effect is obtained, it becomes possible to easily delete an application that is no longer needed.

  The third embodiment is as described above, and the others are the same as in the first and second embodiments. Therefore, the corresponding parts are denoted by the same reference numerals, and detailed description thereof is omitted.

Embodiment 4
Embodiment 4 relates to a form for making a medical appointment. FIG. 23 is a block diagram illustrating a hardware group of the doctor computer 3 according to the fourth embodiment, and FIG. 24 is a block diagram illustrating a hardware group of the server computer 1 according to the fourth embodiment. A reservation DB 355 is provided in the storage unit 35 of the doctor computer 3. A reservation DB 155 is also provided in the storage unit 15 of the server computer 1.

  FIG. 25 is an explanatory diagram showing a record layout of the reservation DB 355 of the doctor computer 3. The reservation DB 355 includes a patient ID field and a reservation date / time field. The next patient reservation date and time is stored in association with the patient ID. The CPU 31 receives the patient ID and the reservation date / time from the input unit 33 and stores them in the reservation DB 355.

  FIG. 26 is an explanatory diagram showing a record layout of the reservation DB 155 of the server computer 1. For each hospital (hospital A, hospital B, hospital C...), A reservation date and time is stored in association with the patient ID. When the content of the reservation DB 355 is updated, the CPU 31 of the doctor computer 3 transmits the hospital ID and the updated content (patient ID and reservation date / time) to the server computer 1. The CPU 11 receives the hospital ID and the updated content. The CPU 11 stores the received hospital ID and update contents in the reservation DB 155. Similarly, when the reservation DB 155 is updated, the CPU 11 transmits the updated content (patient ID and reservation date / time) to the doctor computer 3 corresponding to the hospital ID.

  FIG. 27 is an explanatory diagram showing an image of a reservation acceptance screen displayed on the display unit 24 of the mobile terminal 2. When the hyperlink to the medical appointment page shown in FIG. 12 is clicked, the CPU 11 of the server computer 1 refers to the appointment DB 155 and reads the appointment date and time (hereinafter referred to as the previous appointment date and time) corresponding to the patient ID. The CPU 11 reads the reservation acceptance screen from the storage unit 15. The CPU 11 generates a reservation reception screen to which the patient ID and the read reservation date / time are added, and transmits the reservation reception screen to the mobile terminal 2.

  As shown in FIG. 27, the patient ID and the previous reservation date and time (January 10, 2015 in the example of FIG. 27) are added to the template of the reservation reception screen. The user inputs the date before the previous reservation date / time through the input unit 23 as the next reservation date / time (hereinafter, the next reservation date / time). The user clicks the send button 243 through the input unit 23. The CPU 21 transmits the input next desired reservation date and time to the server computer 1 with the click of the transmission button 243 as a trigger.

  The CPU 11 of the server computer 1 determines whether or not the next reservation date is before the previous reservation date. If the CPU 11 determines that it is before the previous reservation date and time, the CPU 11 stores the next reservation date and time in the reservation DB 155 in association with the patient ID. Further, the CPU 11 deletes the previous reservation date / time from the reservation DB 155. The update contents of the reservation DB 155 are reflected in the reservation DB 355 of the doctor computer 3 as described above.

  28 and 29 are flowcharts showing the procedure of the reservation process. The CPU 11 of the server computer 1 outputs information related to the examination reservation to the display unit 24 of the portable terminal 2 by the process described in the first embodiment (step S281). The CPU 21 of the portable terminal 2 receives the information related to the medical appointment and displays the information related to the medical appointment shown in FIG. The patient clicks a hyperlink through the input unit 23 when making a medical appointment. The CPU 21 transmits the patient ID and the examination reservation request to the server computer 1 with the click of the hyperlink as a trigger (step S282).

  The CPU 11 of the server computer 1 receives the patient ID and the examination reservation request (step S283). The CPU 11 reads out the reservation acceptance screen template from the storage unit 15 (step S284). The CPU 11 refers to the reservation DB 155 and determines whether or not there is a previous reservation date and time corresponding to the patient ID (step S285). If the CPU 11 determines that the previous reservation date / time does not exist in the reservation DB 155 (NO in step S285), the process proceeds to step S286. CPU11 produces | generates the reservation reception screen which added patient ID and time limit information to the reservation reception screen template (step S286). The deadline information is information indicating a deadline until the appointment date, and is a text sentence such as “Please set up an appointment date within one week”. The time limit information can be changed as appropriate from the input unit 13.

  The CPU 11 of the server computer 1 transmits the generated reservation acceptance screen to the mobile terminal 2 (step S287). The CPU 21 of the portable terminal 2 receives the reservation acceptance screen and displays it on the display unit 24 (step S288). The CPU 21 receives the next reservation date and time via the input unit 23 (step S289). The CPU 21 determines whether or not the transmission button 243 has been clicked (step S291). If the CPU 21 determines that the send button 243 has not been clicked (NO in step S291), the CPU 21 waits until the send button 243 is clicked.

  If the CPU 21 of the portable terminal 2 determines that the transmission button 243 on the reservation acceptance screen has been clicked (YES in step S291), it transmits the accepted next reservation date and time to the server computer 1 (step S292). The CPU 11 of the server computer 1 receives the next reservation date and time. The CPU 11 refers to the received next reservation date and time and the current date and time to determine whether or not the next reservation date and time is within the time limit (within one week) added in step S286 (step S293). If the CPU 11 determines that it is not within the time limit (NO in step S293), the process returns to step S286. In this case, a text sentence such as “Please make a reservation within the deadline” may be displayed.

  When the CPU 11 of the server computer 1 determines that the next reservation date and time is within the time limit (YES in step S293), the process proceeds to step S294. The CPU 11 stores the next reservation date and time in the reservation DB 155 in association with the patient ID (step S294). The CPU 11 transmits a reservation confirmation screen to the mobile terminal 2 (step S295). The CPU 21 of the portable terminal 2 displays a reservation confirmation screen on the display unit 24 (step S296). Note that the process of step S293 may be executed on the mobile terminal 2 side.

  If the CPU 11 determines that there is a previous reservation date corresponding to the patient ID (YES in step S285), the process proceeds to step S297. The CPU 11 reads the previous reservation date / time from the reservation DB 155 (step S297). CPU11 produces | generates the reservation screen which added patient ID and the last reservation date to the reservation reception screen template (step S298). CPU11 transmits the produced | generated reservation screen to the portable terminal 2 (step S299). The CPU 21 of the mobile terminal 2 receives the reservation screen (step S2911). The CPU 21 displays the received reservation screen on the display unit 24. The CPU 21 receives the next reservation date and time via the input unit 23 (step S2912).

  The CPU 21 of the portable terminal 2 determines whether or not the transmission button 243 on the reservation screen has been clicked (step S2913). If the CPU 21 determines that the send button 243 has not been clicked (NO in step S2913), the CPU 21 waits until it is clicked. If the CPU 21 determines that it has been clicked (YES in step S2913), the process proceeds to step S2914. The CPU 21 transmits the received next reservation date and time to the server computer 1 (step S2914).

  The CPU 11 of the server computer 1 determines whether or not the next reservation date and time transmitted from the mobile terminal 2 is before the previous reservation date and time (step S2915). If CPU 11 determines that it is not before the previous reservation date and time (NO in step S2915), CPU 11 returns the process to step S298. In this case, a text sentence such as “Please specify a date and time prior to the previous reservation date and time” may be added. If the CPU 11 determines that the transmitted next reservation date / time is earlier than the previous reservation date / time (YES in step S2915), the CPU 11 shifts the processing to step S2916. Note that the processing in step S2915 may be executed on the mobile terminal 2 side.

  When the CPU 11 of the server computer 1 determines that the next reservation date / time is earlier than the previous reservation date / time, the CPU 11 deletes the previous reservation date / time in the reservation DB 155 (step S2916). The CPU 11 stores the next reservation date and time in the reservation DB 155 in association with the patient ID (step S2917). As described above, the update contents of the reservation DB 155 are also reflected in the reservation DB 355 of the doctor computer 3. The CPU 11 transmits a reservation confirmation screen to the mobile terminal 2 (step S2918). The reservation confirmation screen may include a text sentence indicating that the reservation has been completed at the next reservation date and time. The CPU 21 receives the reservation confirmation screen and displays it on the display unit 24 (step S2919). Thereby, it becomes possible to perform an early examination for a patient who does not have a medication effect.

  The fourth embodiment is as described above, and the others are the same as those of the first to third embodiments. Therefore, the corresponding parts are denoted by the same reference numerals and detailed description thereof is omitted.

Embodiment 5
The fifth embodiment relates to a form in which a reservation process is performed on the doctor computer 3 side. 30 and 31 are flowcharts showing the procedure of the reservation process. The CPU 31 of the doctor computer 3 outputs information related to the appointment appointment to the portable terminal 2 by the process described in the first embodiment (step S301). The CPU 21 of the portable terminal 2 receives the information related to the medical appointment and displays the information related to the medical appointment shown in FIG. When making a medical appointment, the patient clicks through the input unit 23 a hyperlink displayed on the display unit 24 where the medical appointment can be processed. The CPU 21 transmits the patient ID and the examination reservation request to the doctor computer 3 with the click of the hyperlink as a trigger (step S302).

  The CPU 31 of the doctor computer 3 receives the patient ID and the examination reservation request from the portable terminal 2 (step S303). The CPU 31 reads out the reservation acceptance screen template from the storage unit 35 (step S304). The CPU 31 refers to the reservation DB 355 and determines whether or not there is a previous reservation date and time corresponding to the patient ID (step S305). If the CPU 31 determines that the previous reservation date does not exist (NO in step S305), the CPU 31 proceeds to step S306. CPU31 produces | generates the reservation reception screen which added patient ID and time limit information to the reservation reception screen template (step S306).

  The CPU 31 of the doctor computer 3 transmits the generated reservation acceptance screen to the mobile terminal 2 (step S307). The CPU 21 of the portable terminal 2 receives the reservation acceptance screen (step S308). CPU21 displays the reservation reception screen on the display part 24 of the portable terminal 2, and receives next reservation date and time via the input part 23 (step S309). The CPU 21 determines whether or not the send button 243 has been clicked (step S311). If the CPU 21 determines that the transmission button 243 has not been clicked (NO in step S311), the CPU 21 waits until the transmission button 243 is clicked.

  If the CPU 21 of the portable terminal 2 determines that the send button 243 has been clicked (YES in step S311), the CPU 21 transmits the accepted next reservation date and time to the doctor computer 3 (step S312). The CPU 31 of the doctor computer 3 receives the next reservation date and time. The CPU 31 refers to the received next reservation date and time and the current date and time to determine whether or not the next reservation date and time is within the time limit (within one week) added in step S306 (step S313). If the CPU 31 determines that it is not within the time limit (NO in step S313), the process returns to step S306.

  If the CPU 31 determines that the next reservation date and time is within the time limit (YES in step S313), the process proceeds to step S314. The CPU 31 stores the next reservation date and time in the reservation DB 355 in association with the patient ID (step S314). CPU31 transmits a reservation confirmation screen to portable terminal 2 (Step S315). The CPU 21 displays a reservation confirmation screen on the display unit 24 (step S316).

  If the CPU 31 determines that there is a previous reservation date and time corresponding to the patient ID (YES in step S305), the process proceeds to step S317. The CPU 31 reads the previous reservation date / time from the reservation DB 355 (step S317). CPU31 produces | generates the reservation screen which added patient ID and the last reservation date to the reservation reception screen template (step S318). CPU31 transmits the produced | generated reservation screen to the portable terminal 2 (step S319). The CPU 21 of the mobile terminal 2 receives the reservation screen (step S3111). The CPU 21 displays the received reservation screen on the display unit 24. The CPU 21 receives the next reservation date and time via the input unit 23 (step S3112).

  The CPU 21 determines whether or not the send button 243 has been clicked (step S3113). If the CPU 21 determines that the send button 243 has not been clicked (NO in step S3113), it waits until it is clicked. If the CPU 21 determines that it has been clicked (YES in step S3113), the process proceeds to step S3114. The CPU 21 transmits the received next reservation date and time to the doctor computer 3 (step S3114).

  The CPU 31 of the doctor computer 3 determines whether or not the next reservation date is before the previous reservation date (step S3115). If CPU 31 determines that it is not before the previous reservation date and time (NO in step S3115), CPU 31 returns the process to step S318. If the CPU 31 determines that it is before the previous reservation date and time (YES in step S3115), the process proceeds to step S3116.

  The CPU 31 deletes the previous reservation date and time recorded in the reservation DB 355 (step S3116). The CPU 31 stores the next reservation date and time in the reservation DB 355 in association with the patient ID (step S3117). As described above, the update contents of the reservation DB 355 may be reflected in the reservation DB 155 of the server computer 1. The CPU 31 transmits a reservation confirmation screen (step S3118). The reservation confirmation screen may include a text sentence indicating that the reservation has been completed at the next reservation date and time. The CPU 21 of the portable terminal 2 receives the reservation confirmation screen and displays it on the display unit 24 (step S3119). Thereby, it becomes possible to perform an early examination for a patient who does not have a medication effect.

  The fifth embodiment is as described above, and the other parts are the same as those of the first to fourth embodiments. Therefore, the corresponding parts are denoted by the same reference numerals and detailed description thereof is omitted.

Embodiment 6
The sixth embodiment relates to a mode in which an application already installed in the mobile terminal 2 is deleted when a patient belongs to a predetermined area. FIG. 32 is an explanatory diagram showing a record layout of the reservation DB 355. The reservation DB 355 further stores a beacon ID in association with the patient ID. The beacon ID is identification information for specifying the beacon 4 provided at the hospital reception, entrance, or the like. FIG. 33 is an explanatory diagram showing a record layout of the reservation DB 155. The reservation DB 355 of the storage unit 15 of the server computer 1 stores the storage contents of the reservation DB 155 of each hospital.

  34 and 35 are flowcharts showing the procedure of the deletion process. As described in the first embodiment, the CPU 21 of the mobile terminal 2 determines whether or not the effect information has been transmitted (step S341). When CPU 21 determines that the effect information has been transmitted (YES in step S341), the process proceeds to step S342. The CPU 21 uninstalls the application installed in step S205 (step S342). If the CPU 21 determines that the effect information is not transmitted (NO in step S341), that is, if the ineffective information is transmitted, the process proceeds to step S343.

  CPU21 transmits ineffective information to the server computer 1 (step S343). The CPU 11 of the server computer 1 receives the ineffective information (step S344). Thereafter, the patient performs the above-described reservation process and goes to the hospital. When the mobile terminal 2 belongs to the communication range of the beacon 4 provided near the reception of the hospital, for example, the CPU 21 of the mobile terminal 2 transmits the patient ID and the beacon ID to the server computer 1 (step S345). Note that the beacon 4 may transmit the patient ID and the beacon ID to the server computer 1.

  CPU11 of the server computer 1 receives patient ID and beacon ID from the portable terminal 2 (step S346). CPU11 reads reservation date and time and beacon ID from reservation DB155 (step S347). The CPU 11 determines whether today is the same as the reservation date (step S348). If the CPU 11 determines that they do not match (NO in step S348), the process ends. If the CPU 11 determines that they match (YES in step S348), the process proceeds to step S349.

  The CPU 11 determines whether or not the read beacon ID matches the received beacon ID. If the CPU 11 determines that they do not match (NO in step S349), the process ends. If the CPU 11 determines that they match (YES in step S349), the process proceeds to step S351. In the embodiment, the process in step S348 is performed before the process in step S349. However, the present invention is not limited to this. The process of step S348 may be performed after step S349. Further, the process of step S348 may not be performed. In addition, although the example which judges the communication range of the beacon 4 as a predetermined area | region was given in this embodiment, it is not restricted to this. Even if the latitude and longitude of the hospital are stored and the latitude and longitude acquired by the GPS module 28 of the patient's portable terminal 2 belong to the stored latitude and longitude, it is determined that the hospital belongs to the predetermined area. good.

  CPU11 outputs the uninstallation command of the application installed in the portable terminal 2 (step S351). The CPU 21 of the mobile terminal 2 receives the uninstall command (step S352). The CPU 21 uninstalls the application stored in the storage unit 25 (step S353). Thereby, it becomes possible to delete the application of the portable terminal 2 of the patient who visited the hospital.

  The sixth embodiment is as described above, and the other parts are the same as those of the first to fifth embodiments. Accordingly, the corresponding parts are denoted by the same reference numerals, and detailed description thereof is omitted.

Embodiment 7
The seventh embodiment relates to a form in which the doctor computer 3 outputs an uninstall command for an application installed in the mobile terminal 2. 36 and 37 are flowcharts showing the procedure of the deletion process. As described in Embodiment 1, the CPU 21 of the portable terminal 2 determines whether or not the effect information has been transmitted (step S361). When CPU 21 determines that the effect information has been transmitted (YES in step S361), the process proceeds to step S362. The CPU 21 uninstalls the application installed in step S205 (step S362). If the CPU 21 determines that the effect information is not transmitted (NO in step S361), that is, if the ineffective information is transmitted, the process proceeds to step S363.

  The CPU 21 transmits ineffective information to the doctor computer 3 (step S363). The CPU 31 receives ineffective information (step S364). Thereafter, the patient performs the above-described reservation process and goes to the hospital. When the mobile terminal 2 belongs to the communication range of the beacon 4 provided near the reception of the hospital, for example, the CPU 21 transmits the patient ID and the beacon ID to the doctor computer 3 (step S365). The beacon 4 may transmit the patient ID and the beacon ID to the doctor computer 3.

  The CPU 31 of the doctor computer 3 receives the patient ID and the beacon ID (step S366). CPU31 reads reservation date and time and beacon ID from reservation DB155 (step S367). The CPU 31 determines whether today is the same as the reservation date (step S368). If the CPU 31 determines that they do not match (NO in step S368), it ends the process. If the CPU 31 determines that they match (YES in step S368), the process proceeds to step S369.

  The CPU 31 determines whether or not the read beacon ID matches the received beacon ID (step S369). When CPU 31 determines that they do not match (NO in step S369), CPU 31 ends the process. If the CPU 31 determines that they match (YES in step S369), the process proceeds to step S371.

  CPU31 outputs the uninstallation command of the application installed in the portable terminal 2 (step S371). The CPU 21 receives an uninstall command (step S372). The CPU 21 uninstalls the application stored in the storage unit 25 (step S373). Thereby, it becomes possible to delete the application of the portable terminal 2 of the patient who visited the hospital.

  The seventh embodiment is as described above, and the others are the same as those of the first to sixth embodiments. Therefore, the corresponding parts are denoted by the same reference numerals, and detailed description thereof is omitted.

Embodiment 8
FIG. 38 is a functional block diagram showing operations of the server computer 1 and the doctor computer 3 in the above-described form. When the CPU 11 executes the control program 15P, the server computer 1 operates as follows. The accepting unit 101 accepts the setting of a timing value for confirming the effect associated with the medication prescribed to the patient. The transmission unit 102 transmits a message inquiring about the effect of the medicine to the patient terminal at the timing value. When the output unit 103 receives an answer indicating that there is no effect associated with taking a medicine from the patient's terminal, the output unit 103 outputs information related to the examination reservation to the patient's terminal.

  When the CPU 31 executes the control program 35P, the doctor computer 3 operates as follows. When receiving an answer indicating that there is no effect associated with drug administration from the patient's terminal, the determination unit 301 determines whether there is a medical appointment for the patient. When the cancellation unit 302 determines that a medical appointment is present, the canceling unit 302 cancels the medical appointment. When the setting unit 303 determines that the examination reservation exists, the setting unit 303 sets an examination appointment date prior to the examination appointment.

  FIG. 39 is a block diagram illustrating a hardware group of the server computer 1 according to the eighth embodiment. A program for operating the server computer 1 includes a portable recording medium 1A such as a CD-ROM, a DVD (Digital Versatile Disc) disk, a memory card, or a USB (Universal Serial Bus) memory in a reading unit 10A such as a disk drive. It may be read and stored in the storage unit 15. Further, a semiconductor memory 1B such as a flash memory storing the program may be mounted in the server computer 1. Further, the program can be downloaded from another server computer (not shown) connected via a communication network N such as the Internet. The contents will be described below.

  The server computer 1 shown in FIG. 39 reads a program for executing the above-described various software processes from the portable recording medium 1A or the semiconductor memory 1B, or from another server computer (not shown) via the communication network N. to download. The program is installed as the control program 15P, loaded into the RAM 12, and executed. Thereby, it functions as the server computer 1 described above.

  The eighth embodiment is as described above, and the others are the same as those of the first to seventh embodiments. Therefore, the corresponding parts are denoted by the same reference numerals, and detailed description thereof is omitted.

  With respect to the embodiments including the above first to eighth embodiments, the following additional notes are disclosed.

(Appendix 1)
On the computer,
Accept the timing settings to check the effects of taking the medication prescribed to the patient,
At the timing, a message for inquiring about the effect of the drug is sent to the patient's terminal,
A program for executing a process of outputting information related to a medical examination appointment to the patient's terminal when receiving an answer indicating that there is no effect associated with taking the medicine from the patient's terminal.
(Appendix 2)
When receiving a response from the patient's terminal that there is no effect associated with taking the drug, determine whether there is a medical appointment for the patient,
The program according to appendix 1, which executes a process of canceling the appointment when it is determined that the appointment is present.
(Appendix 3)
The program according to appendix 2, which executes a process of setting a medical appointment date earlier than the medical appointment when it is determined that the medical appointment exists.
(Appendix 4)
Get the set number of doses,
Get completion information indicating that the medication has been completed,
The program according to any one of appendices 1 to 3, which executes a process of transmitting a message for inquiring about the effect of a medicine to the terminal of the patient when the number of acquired completion information reaches a set number of times of medication. .
(Appendix 5)
The program according to any one of appendices 1 to 4, which executes a process of outputting an installation instruction of an application related to taking a prescribed medicine after receiving the timing setting.
(Appendix 6)
The program according to appendix 5, which executes a process of outputting an instruction to delete the application to the terminal after receiving an answer indicating that there is an effect associated with taking a medicine from the terminal of the patient.
(Appendix 7)
A process of outputting an instruction to delete the application to the terminal when receiving an answer from the terminal of the patient that there is no effect associated with taking the medicine and determining that the terminal belongs to a predetermined area; The program according to appendix 5 or 6 to be executed.
(Appendix 8)
A reception unit for receiving a setting of timing for confirming an effect associated with taking a medicine prescribed to a patient;
At the timing, a transmission unit that transmits a message for inquiring about the effect of the drug to the patient's terminal,
An information processing apparatus comprising: an output unit configured to output information related to a medical examination appointment to the patient's terminal when receiving an answer indicating that there is no effect associated with drug administration from the patient's terminal.
(Appendix 9)
Accept the timing settings to check the effects of taking the medication prescribed to the patient,
At the timing, a message for inquiring about the effect of the drug is sent to the patient's terminal,
An information processing method for causing a computer to execute a process of outputting information related to a medical examination appointment to the patient's terminal when receiving an answer indicating that there is no effect associated with medication from the patient's terminal.
(Appendix 10)
In an information processing system in which a first information processing apparatus and a second information processing apparatus are connected via a communication network,
The first information processing apparatus
A reception unit for receiving a setting of timing for confirming an effect associated with taking a medicine prescribed to a patient;
At the timing, a transmission unit that transmits a message for inquiring about the effect of the drug to the patient's terminal,
When receiving an answer indicating that there is no effect associated with taking a medicine from the terminal of the patient, an output unit that outputs information related to a medical appointment to the terminal of the patient, and
The second information processing device includes:
When receiving an answer indicating that there is no effect associated with taking a drug from the terminal of the patient, a determination unit that determines whether or not there is a medical appointment for the patient;
An information processing system comprising: a cancellation unit that cancels a medical appointment when it is determined that a medical appointment exists.
(Appendix 11)
The second information processing device includes:
The information processing system according to supplementary note 10, further comprising: a setting unit that sets a medical appointment date prior to the medical appointment when it is determined that the medical appointment exists.

DESCRIPTION OF SYMBOLS 1 Server computer 1A Portable recording medium 1B Semiconductor memory 2 Portable terminal 3 Doctor's computer 4 Beacon 10A Reading part 11 CPU
12 RAM
13 Input unit 14 Display unit 15 Storage unit 15P Control program 16 Communication unit 18 Clock unit 21 CPU
23 Input unit 24 Display unit 25 Storage unit 25P Control program 26 Communication unit 28 GPS module 29 Short-range communication module 31 CPU
32 RAM
33 Input unit 34 Display unit 35 Storage unit 35P Control program 36 Communication unit 101 Reception unit 102 Transmission unit 103 Output unit 151 Patient DB
152 Chart DB
153 Medication DB
154 Beacon DB
155 Reservation DB
241 YES button 242 NO button 243 Send button 301 Judgment unit 302 Cancellation unit 303 Setting unit 351 Patient DB
352 chart DB
355 Reservation DB
N communication network

Claims (7)

On the computer,
Accept the timing settings to check the effects of taking the medication prescribed to the patient,
At the timing, a message for inquiring about the effect of the drug is sent to the patient's terminal,
When receiving a response from the patient's terminal that there is no effect associated with taking the medicine, output information related to the appointment to the patient's terminal ,
When receiving a response from the patient's terminal that there is no effect associated with taking the drug, determine whether there is a medical appointment for the patient,
A program for executing processing for canceling a medical appointment when it is determined that a medical appointment exists . If it is determined that the examination reservation is present, the program according to claim 1 for executing a process of setting the previous examination reservation date than the examination reservation. A reception unit for receiving a setting of timing for confirming an effect associated with taking a medicine prescribed to a patient;
At the timing, a transmission unit that transmits a message for inquiring about the effect of the drug to the patient's terminal,
When receiving an answer indicating that there is no effect associated with taking a drug from the patient's terminal, an output unit that outputs information related to a medical appointment to the patient's terminal ;
When receiving an answer indicating that there is no effect associated with taking a drug from the terminal of the patient, a determination unit that determines whether or not there is a medical appointment for the patient;
An information processing apparatus comprising: a cancellation unit that cancels a medical appointment when it is determined that a medical appointment exists . Accept the timing settings to check the effects of taking the medication prescribed to the patient,
At the timing, a message for inquiring about the effect of the drug is sent to the patient's terminal,
When receiving an answer indicating that there is no effect associated with taking a medicine from the terminal of the patient, information related to the examination reservation is output to the terminal of the patient .
When receiving a response from the patient's terminal that there is no effect associated with taking the drug, determine whether there is a medical appointment for the patient,
An information processing method for causing a computer to execute a process of canceling a medical appointment when it is determined that a medical appointment exists . On the computer,
Get the set number of doses,
Get completion information indicating that the medication has been completed,
If the number of acquired completion information has reached the set dosing times, it transmits a message inquiring the effect of the drug to the terminal of the patient,
A program for executing a process of outputting information related to a medical examination appointment to the patient's terminal when receiving an answer indicating that there is no effect associated with taking the medicine from the patient's terminal. An acquisition unit for acquiring the set number of times of medication;
A second acquisition unit for acquiring completion information indicating that the medication has been completed;
If the number of acquired completion information has reached the set dosing times, a transmitting unit that transmits the message inquiring the effect of the drug to the terminal of the patient,
An information processing apparatus comprising: an output unit configured to output information related to a medical examination appointment to the patient's terminal when receiving an answer indicating that there is no effect associated with drug administration from the patient's terminal. On the computer,
Get the set number of doses,
Get completion information indicating that the medication has been completed,
If the number of acquired completion information has reached the set dosing times, it transmits a message inquiring the effect of the drug to the terminal of the patient,
An information processing method for executing a process of outputting information related to a medical appointment addressed to the patient's terminal when an answer indicating that there is no effect associated with the medication is received from the patient's terminal.

Images