JP6249619B2 - Information processing apparatus, information processing method, and program - Google Patents

Description

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

The use of electronic prescriptions, which are electronic versions of conventional paper prescriptions, has been proposed. The electronic prescription is data obtained by digitizing information described in a conventional paper prescription. The electronic prescription is managed by an IC card, a mobile phone, a mobile terminal, a server, or the like. Replacing paper prescriptions with electronic prescriptions improves patient convenience by eliminating paper, prevents handwriting errors when delivering prescriptions, and provides a hand for dispensing systems when dispensing with prescriptions An effect such as input error prevention is also expected.
In addition, a dispensing system using the above-described electronic prescription has also been proposed (see Patent Document 1). According to this technique, prescription information in an electronic prescription is input to the dispensing system. The dispensing system determines whether or not the input prescription information includes prescription information within the period of use and undispensed, and transmits prescription information that matches the conditions to the database server of the pharmacy. Thereby, in a pharmacy, dispensing is performed based on prescription information.

  By the way, the format of the paper prescription is provided with columns for describing the period of use and the date of delivery of the prescription. Here, the use period is a period during which the prescription is valid. Usually, if the period of use is not described in the paper prescription, four days including the date of delivery of the prescription are treated as a substantial period of use. On the other hand, if the use period is described, the described use period is directly used as the use period. Normally, the period of use is not described, but if special circumstances such as a long-term trip of the patient are recognized, the doctor can issue a prescription specifying the period of use for the purpose of extending the period of use.

JP 2010-277582 A

  However, in the conventional electronic prescription, it is not considered that the use period is not recorded in the prescription information. For this reason, when there is prescription information in which the use period is not recorded, it is difficult to appropriately determine whether or not the prescription information is within the use period.

An object of this invention is to start the output of the notification regarding a prescription at an appropriate timing according to the patient's circumstances .

Therefore, the information processing apparatus of the present invention provides delivery date information acquisition means for acquiring delivery date information indicating the delivery date of the prescription from prescription information relating to the prescription, and usage period information indicating the usage period of the prescription in the prescription information. Use period information determining means for determining whether the use period information is included, and when the use period information is included in the prescription information, the use period indicated by the use period information is set as the use period of the prescription When the prescription information does not include the use period information, a use period setting unit that sets a use period of the prescription based on the delivery date information, and a notification output unit that outputs a notification regarding the prescription when have, the notification output means, when the use period of use period information indicates is set as the period of use of the prescription by the use period setting means, the use The output of the first notification period information is output at a timing based on the use period indicated, the second notification when the use period of the prescription based on the delivery date information is set by the use period setting means The output is started at a different timing.

ADVANTAGE OF THE INVENTION According to this invention, the output of the notification regarding a prescription can be started at the appropriate timing according to the patient's situation .

1 is a diagram illustrating an overall configuration of a system according to a first embodiment. It is a figure which shows an example of the electronic prescription data which a portable terminal has. It is a figure which shows the hardware constitutions of a hospital terminal, a patient terminal, a pharmacy terminal, and a patient family terminal. It is a figure which shows the hardware constitutions of a portable terminal. It is a figure which shows the hardware constitutions of IC card. It is a flowchart which shows the dispensing notification determination process based on a date. It is a flowchart which shows a dispensing notification process. It is a flowchart which shows a use period setting process. It is a figure which shows an example of pharmacy detailed data. It is a flowchart which shows a non-dispensing notification process. It is a figure which shows the example of a display of undispensed notification information. It is a flowchart which shows family pharmacy search processing. It is a flowchart which shows the pharmacy search process near the present position. It is a flowchart which shows the pharmacy search process on a normal path | route. It is a figure which shows an example of present position information. It is a figure which shows an example of the plot result. It is a flowchart which shows the dispensing notification determination process based on an event. It is a figure which shows an example of an event list. It is a figure which shows an example of an importance table. It is a figure which shows an example of a notification space | interval table. It is a figure which shows an example of a notification method table. It is a flowchart which shows a notification interval setting process. It is a flowchart which shows an electronic prescription output process. It is a figure which shows an example of a printing image. It is a flowchart which shows the prescription electronic process of paper. It is a flowchart which shows a use period setting process. It is a figure which shows an example of the scan image of a prescription. It is a figure which shows an example of the scan image of a prescription. It is a figure which shows an example of the scan image of a prescription. It is a figure which shows an example of the scan image of a prescription. It is a flowchart which shows a barcode prescription reading process. It is a figure which shows an example of the prescription of the paper to which the barcode was provided. It is a figure which shows an example of the prescription of the paper to which the barcode was provided.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

(First embodiment)
<System configuration>
FIG. 1 is a diagram showing an overall configuration of a prescription system according to the first embodiment. The prescription system according to the present embodiment includes a hospital terminal 121, a pharmacy terminal 124, a portable terminal 122 as an information processing device, a patient terminal 123, and a patient family terminal 125.
The hospital terminal 121 is a terminal installed in a medical facility such as a hospital, generates prescription information indicating the contents of a prescription prescribed by a doctor, and stores the generated prescription information in electronic prescription data. The pharmacy terminal 124 receives the prescription information and stores the received prescription information in the electronic prescription data. Further, when dispensing based on the prescription information is performed, the pharmacy terminal 124 stores the dispensing information related to dispensing in the electronic prescription data in association with the prescription information.

The portable terminal 122 and the patient terminal 123 are terminals used by patients. The patient family terminal 125 is a terminal used by the patient's family. The portable terminal 122 receives prescription information from the hospital terminal 121 and receives dispensing information from the pharmacy terminal 124. The portable terminal 122 stores the received prescription information and dispensing information in the electronic prescription data.
The patient terminal 123 and the patient family terminal 125 receive prescription information from the mobile terminal 122. As another example, the patient terminal 123 and the patient family terminal 125 may receive prescription information and dispensing information from the hospital terminal 121 and the pharmacy terminal 124.

In the prescription system according to this embodiment, the patient brings his / her own portable terminal 122 closer to the hospital terminal 121 after examination by a doctor. Thereby, the prescription information corresponding to the prescription for the patient is transmitted from the hospital terminal 121 to the portable terminal 122 via a wireless module (described later) included in the portable terminal 122 and the hospital terminal 121. The prescription information is stored in the electronic prescription data (FIG. 2) that the portable terminal 122 has. The above process can be implemented as an alternative process to the process of issuing a paper prescription.
The portable terminal 122 that has accumulated the prescription information outputs a dispensing notification to an output device such as a display at a predetermined timing based on the prescription information in the electronic prescription data. Moreover, the portable terminal 122 can also transmit an e-mail or the like as a dispensing notification to at least one of the patient terminal 123 and the patient family terminal 125.
Furthermore, the portable terminal 122 records GPS log information by continuously measuring its own location information. Then, the portable terminal 122 refers to the GPS log information when providing the pharmacy information that can be dispensed to the user together with the dispensing notification.

When a patient requests dispensing at a pharmacy, the patient brings his mobile terminal 122 close to the pharmacy terminal 124. Thereby, prescription information is transmitted from the portable terminal 122 to the pharmacy terminal 124 via a wireless module (described later) included in the portable terminal 122 and the pharmacy terminal 124. Thereby, prescription information is accumulated in the electronic prescription data of the pharmacy terminal 124. Then, in the pharmacy, a dispensing procedure is performed based on the prescription information received by the pharmacy terminal 124. The above process can be implemented as an alternative process of the dispensing process using a paper prescription.
When dispensing at the pharmacy is completed, the pharmacy terminal 124 stores dispensing information indicating that dispensing is completed in the electronic prescription data in association with the prescription information for which dispensing has been completed. At this time, the pharmacy terminal 124 transmits the dispensing information to the hospital terminal 121 and the portable terminal 122 together with the prescription ID for identifying the corresponding prescription information. Upon receiving the dispensing information, the hospital terminal 121 stores the dispensing information in association with the prescription ID in the electronic prescription data. Similarly, when receiving the dispensing information, the portable terminal 122 stores the dispensing information in association with the prescription ID in the electronic prescription data.

Note that the timing at which the hospital terminal 121 receives dispensing information is not limited to the embodiment. As another example, the hospital terminal 121 may receive dispensing information from the pharmacy terminal 124 periodically.
The mobile terminal 122 transmits the updated content to the patient terminal 123 and the patient family terminal 125 every time the electronic prescription data is updated. Note that the timing at which the mobile terminal 122 transmits the update content is not limited to the embodiment. As another example, the portable terminal 122 may transmit the update content periodically.

FIG. 2 is a diagram illustrating an example of electronic prescription data that the portable terminal 122 has. As shown in FIG. 2, the portable terminal 122 according to the present embodiment manages prescription information of a plurality of medicines as one electronic prescription data. One prescription information is recorded as one record in each row of the electronic prescription data.
In FIG. 2, four pieces of prescription information 61 to 64 are recorded. Further, each prescription information includes a prescription ID, a drug name, a delivery date (delivery date information), a use period (use period information), a quantity, a usage and a dose, hospital information, a dispensing method, a dispensed flag, and pharmacy information. It is out.

The prescription ID is an identifier capable of uniquely specifying prescription information. The drug name is a name of a drug that can uniquely specify a prescribed drug. The delivery date is the date when the prescription information is issued. The usage period is a date indicating a period during which the prescription information is valid. In the usage period shown in FIG. 2, the last day of the usage period is recorded. When the period of use has passed, the patient or the like cannot receive a prescription of a medicine based on prescription information.
A dose is the dose of a drug. The amount is the daily dose for internal medicine, the total dose for external medicines and injections, and the single dose for oral medicine. Dosage and dosage are dose per dose, number of doses per day, and dose timing.

The hospital information is information related to the hospital to which the prescription information is issued. In the present embodiment, the name of the hospital is used as an example of the hospital information. As another example, in addition to the name of the hospital, the hospital information includes the hospital ID for identifying the hospital, the contact information of the hospital, the location of the hospital, the address of the doctor in charge, that is, the doctor who performed the prescription, the name of the doctor, etc. You can leave. Furthermore, the hospital information may include a digital signature of prescription information for authenticating that the hospital has delivered the prescription information. The digital signature is calculated by performing a signature operation on the prescription information using a hospital signature key. Alternatively, the signature calculation may be performed using the doctor's signature key. Alternatively, it may include both a digital signature calculated using a hospital signature key and a digital signature calculated using a doctor's signature key.
The dispensing method is special information related to prescription information. In the example shown in FIG. 2, special prescription information “prescription ID3 and single package” and “prescription ID2 and single package” are recorded in the prescription information 62 and 63, respectively. In this example, the medicine C specified by the prescription ID3 and the medicine B specified by the prescription ID2 may be packaged and dispensed.
As described above, the prescription ID, drug name, delivery date, usage period, amount, usage and dose, hospital information, and dispensing method are information generated in the hospital terminal 121. The portable terminal 122 acquires a prescription ID, a medicine name, a delivery date, a usage period, a dosage, a usage and a dose, hospital information, and a dispensing method from the hospital terminal 121.

The dispensed flag is information indicating whether or not the medicine indicated in the prescription information has been dispensed. In the example of FIG. 2, “1” indicates that dispensing has been completed, and “0” indicates that dispensing has not occurred. The initial value “0” is set for the dispensed flag in the hospital terminal 121, and the mobile terminal 122 acquires the initial value “0”. Then, when dispensing is performed, the mobile terminal 122 receives information from the pharmacy terminal 124 and rewrites the dispensing flag to “1” accordingly. The dispensed flag is an example of dispensing information indicating whether dispensing is being performed.
The pharmacy information is information related to the pharmacy where the dispensing based on the prescription information has been performed. The pharmacy information is information generated by the pharmacy terminal 124 after dispensing in the pharmacy (that is, when the dispensed flag is “1”). In the present embodiment, as an example of pharmacy information, a pharmacy ID for identifying a pharmacy and a pharmacy name are used.

As another example, the pharmacy information may include a pharmacy contact information, a pharmacy location, a pharmacy address, a pharmacist name, and the like in addition to the pharmacy ID and the pharmacy name. The pharmacy information may include a digital signature of the prescription information for authenticating that the pharmacy has dispensed based on the prescription information. The digital signature is calculated by performing a signature operation on the prescription information using a pharmacy signature key. Alternatively, the signature calculation may be performed using the pharmacist's signature key. Alternatively, both a digital signature obtained by signature calculation using a pharmacy signature key and a digital signature obtained by signature calculation using a pharmacist signature key may be included.
In addition to the above information, the prescription information may include the amount of the dispensed drug, the date of dispensing, the contents of the question inquiry to the doctor, the changed points, and the like. In this case, the electronic prescription data records these information as prescription information.

  The hospital terminal 121 and the pharmacy terminal 124 store prescription information of a plurality of patients as electronic prescription data. Specifically, the prescription information in the electronic prescription data of the hospital terminal 121 and the pharmacy terminal 124 stores the patient ID in addition to the information of the prescription information in the electronic prescription data of the portable terminal 122. The patient ID is an identifier that can uniquely identify a patient.

3A to 3C are diagrams illustrating the hardware configuration of the hospital terminal 121, the portable terminal 122, the patient terminal 123, the pharmacy terminal 124, and the patient family terminal 125. FIG. 3A is a diagram illustrating the host computer 111. The hospital terminal 121, patient terminal 123, pharmacy terminal 124, and patient family terminal 125 have a hardware configuration of the host computer 111. The host computer 111 is, for example, a commonly used personal computer.
As shown in FIG. 3A, the host computer 111 includes a CPU 112, a ROM 113, a RAM 114, a display 115, a DVD 116, an HD 117, a NIC 118, a wireless module 119, an I / F 1110, and a clock 1119. These units are connected via a bus 1117.

The CPU 112 is an electronic circuit. The CPU 112 controls the operation of each unit in the host computer 111. The CPU 112 also executes a program loaded on the RAM 114. The display 115 displays various information generated under the control of the CPU 112.
The ROM 113 stores a BIOS for starting the host computer 111 and a boot program. The ROM 113 includes a non-volatile and non-rewritable ROM and a non-volatile and rewritable flash ROM. The RAM 114 stores an OS and application programs executed by the CPU 112. The RAM 114 is also used as a temporary work area. The DVD 116 and HD 117 store various data such as programs such as an OS and applications, the above-described electronic prescription data, and GPS logs.

The NIC 118 is an interface for enabling communication with another host computer by connecting a wired communication cable. The wireless module 119 is a module that enables wireless communication with other host computers, mobile terminals (described later), and IC cards. The clock 1119 is a module for calculating the date and time. The I / F 1110 is an interface for connecting the printer 1111, the scanner 1112, the mouse 1113, the keyboard 1114, and the barcode reader 1115 to the host computer 111.
The host computer 111 can output a printed matter including a paper prescription by the printer 1111, or can digitize a printed matter including the paper prescription by the scanner 1112. In addition, the host computer 111 can read a barcode added to a paper prescription by the barcode reader 1115. The barcode on the paper prescription will be described later. The user can input various instructions and data to the host computer 111 using the mouse 1113 and the keyboard 1114.

FIG. 3B is a diagram illustrating the mobile terminal 1116. The mobile terminal 122 has the hardware configuration of the mobile terminal 1116. The mobile terminal 1116 is, for example, a commonly used mobile phone, smartphone, PDA (Personal Data Assistance), or the like.
As illustrated in FIG. 3B, the mobile terminal 1116 includes a CPU 112, a ROM 113, a RAM 114, a display 115, a wireless module 119, a GPS 1120, an IC card 1118, and a clock 1119. Similar to the host computer 111, these units are connected via a bus 1117. In the figure, the same components as those of the host computer 111 are denoted by the same reference numerals, and the description thereof is omitted.

The mobile terminal 1116 of this embodiment does not have the HD 117. For this reason, the ROM 113 stores various data such as an OS, a program such as an application, and electronic prescription data. In addition, the mouse 1113 and the keyboard 1114 are not connected to the mobile terminal 1116 in the present embodiment. Therefore, it is assumed that the user uses a sensor (not shown) provided in the display as these alternative input means. A user of the mobile terminal 1116 inputs various instructions and information to the mobile terminal 1116 using a finger or a pen. The mobile terminal 1116 receives an input from the user by a sensor.
The GPS 1120 is a module that receives radio waves from a GPS satellite (not shown) and can measure the current position of the mobile terminal 1116 based on the contents of signals included in the received radio waves. The mobile terminal 1116 receives the current time as well as the current position from the GPS satellite.

Note that the mobile terminal 122 as the mobile terminal 1116 according to the present embodiment receives a radio wave transmitted from a satellite using the GPS 1120 in order to specify the current position, and receives current position information by the received radio wave. As another example, the mobile terminal 122 may receive radio waves from a base station such as a mobile phone or a PHS phone, a wireless LAN access point, or the like, and specify location information based on the received radio waves. Thus, the process for the portable terminal 122 to specify the local position is not limited to the embodiment.
The IC card 1118 is a chip having physical tamper resistance. The tamper resistance is a mechanism that allows the IC card 1118 to self-destruct when an attacker attempts to physically analyze the configuration, program, data, etc. in the IC card 1118. This mechanism can prevent an attacker from analyzing the IC card 1118 and exposing or tampering with programs, data, and the like recorded in the IC card 1118.

FIG. 3C is a diagram illustrating a detailed configuration of the IC card 1118 included in the mobile terminal 1116. The IC card 1118 in this embodiment includes a CPU 112, a ROM 113, a RAM 114, a wireless module 119, and a clock 1119. These units are connected via a bus 1117. In the figure, the same components as those of the host computer 111 are denoted by the same reference numerals, and description thereof is omitted.
Further, the IC card 1118 in this embodiment does not have the HD 117. For this reason, it is assumed that the ROM 113 stores programs such as an OS and applications, and various data such as electronic prescription data. For example, by storing the electronic prescription data in the IC card 1118, it becomes possible to prevent the electronic prescription data from being counterfeited and falsified.
Note that the following processing by the hospital terminal 121 is realized by the CPU 112 of the hospital terminal 121 reading out a program stored in the ROM 113 or the HD 117 and executing this program. The same applies to the processing by the portable terminal 122, the patient terminal 123, the pharmacy terminal 124, and the patient family terminal 125. That is, the processing by each of the devices 122 to 125 is realized by the CPU 112 of each of the devices 122 to 125 reading out a program stored in the ROM 113 or the HD 117 and executing this program.

As another example, the mobile terminal 1116 may not have the IC card 1118. In this case, the mobile terminal 1116 may use the IC card 1118 by communicating with an external IC card using the wireless module 119. As another example, the mobile terminal 1116 does not have the IC card 1118 and may store information necessary for the following processing in a recording medium provided in the ROM 113 or the like.
As another example, the hospital terminal 121, the patient terminal 123, the pharmacy terminal 124, or the patient family terminal 125 may have a hardware configuration of the mobile terminal 1116.

<Dispensing notification determination process based on date and time>
Next, the dispensing notification determination process based on the date and time by the mobile terminal 122 will be described with reference to FIG. FIG. 4 is a flowchart showing a dispensing notification determination process based on the date and time. In addition, when prescription information is written in the electronic prescription data in the ROM 113, the portable terminal 122 sends a dispensing notification to the patient by a dispensing notification determination process based on the date and time.
Note that the mobile terminal 122 performs dispensing notification to the patient by dispensing notification determination processing based on events, as well as dispensing notification determination processing based on date and time. The dispensing notification determination process based on the event will be described later with reference to FIG.

In the dispensing notification determination process based on the date and time, first, in S11, the CPU 112 of the portable terminal 122 uses the clock 1119 to acquire the current date and time when the process is executed (hereinafter simply referred to as the current date and time). Here, the current date and time is an example of processing execution timing. S11 is an example of an execution timing specifying process for specifying the execution timing.
Next, in S12, the CPU 112 acquires the notification date and time recorded in the ROM 113. Here, the notification date and time is information indicating the date and time when the dispensing notification is performed. The portable terminal 122 appropriately sets the notification date and time in the ROM 113 based on the prescription information stored in the electronic prescription data in the process described later. The process for setting the notification date and time will be described later with reference to FIG.

Next, in S <b> 13, the CPU 112 determines whether or not the notification date / time is set in the ROM 113. When the notification date and time is set, the CPU 112 advances the process to S14. If the notification date has not been set, the CPU 112 advances the process to S15.
In S14, the CPU 112 calculates the absolute value of the difference between the current date and time acquired in S11 and the notification date and time acquired in S12. The CPU 112 further determines whether or not the calculated absolute value of the difference is smaller than a threshold value. If the calculated absolute value of the difference is smaller than the threshold, the CPU 112 advances the process to S18. When the calculated absolute value of the difference is greater than or equal to the threshold, the CPU 112 advances the process to S112. That is, in S14, the CPU 112 determines whether or not the period between the execution timing and the notification date / time is shorter than the threshold value, the process proceeds to S18 if it is shorter, and the process proceeds to S112 if it is longer.

In S112, the CPU 112 advances the process to S11 after sleeping for a certain period. On the other hand, in S <b> 15, the CPU 112 acquires the notification interval recorded in the ROM 113. Here, the notification interval is a time interval at which dispensing notification is performed. It is assumed that the portable terminal 122 stores a predetermined value in the ROM 113 in advance as an initial value of the notification interval.
As another example, the user of the mobile terminal 122 may input an arbitrary value as the notification interval to the mobile terminal 122 using a sensor of the display 115. In this case, the ROM 113 stores a value input by the user as a notification interval.
The mobile terminal 122 can increase the notification interval of the dispensing notification as the notification interval is larger, and can shorten the notification interval of the dispensing notification as the notification interval is smaller.

Next, in S <b> 16, the CPU 112 acquires the previous notification date and time recorded in the ROM 113. The ROM 113 stores an initial value “0” as the previous notification date. The previous notification date and time is overwritten and updated in S19 described later.
In S17, the CPU 112 calculates the absolute value of the difference between the current date and time acquired in S11 and the previous notification date and time acquired in S16. The CPU 112 further determines whether or not the calculated absolute value of the difference is smaller than the notification interval acquired in S15. If the calculated absolute value of the difference is smaller than the threshold, the CPU 112 advances the process to S18. When the calculated absolute value of the difference is greater than or equal to the threshold, the CPU 112 advances the process to S112.
That is, in S17, the CPU 112 advances the process to S18 if the time corresponding to the notification interval has elapsed from the previous notification date and time, and advances the process to S1112 if it has not yet elapsed.
In the present embodiment, the portable terminal 122 advances the process to S18 when the previous notification date and time is the initial value “0” so that the dispensing notification process in S18 is always executed during the first process. And

In S18, the CPU 112 executes a dispensing notification process. In the dispensation notification process, the CPU 112 appropriately performs dispensation notification when the prescription information of undispensed information exists in the electronic prescription data. The dispensing notification process will be described later in detail with reference to FIG. After the dispensing notification process, in S19, the CPU 112 records the current date and time acquired in S11 in the ROM 113 as the notification date and time.
As another example, the CPU 112 may acquire the current date and time at the time of execution of S19 again from the clock 1119 and record the acquired current date and time in the ROM 113 as the notification date and time. In this case, the current date and time acquired in S19 is an example of execution timing.

Next, in S110, the CPU 112 determines whether or not the user of the portable terminal 122 has instructed the end of the dispensing notification determination process based on the date and time. If termination is instructed, the CPU 112 advances the process to S111. If termination is not instructed, the CPU 112 advances the process to S112. The end instruction may be given to the portable terminal 122 by the user of the portable terminal 122 using the sensor of the display 115. In step S <b> 111, the CPU 112 overwrites the notification date and time with the initial value “0”, and then ends the series of processes.
As described above, in the dispensing notification determination process based on the date and time, the portable terminal 122 repeatedly executes the dispensing notification process at a predetermined notification interval when the notification date and time are not set. On the other hand, when the notification date is set, the portable terminal 122 executes the dispensing notification process at a timing determined from the set notification date.

<Dispensing notification process>
Next, the dispensing notification process (S18) described with reference to FIG. 5 will be described. FIG. 5 is a flowchart showing detailed processing in the dispensing notification processing by the mobile terminal 122. First, in S <b> 31, the CPU 112 of the mobile terminal 122 acquires one prescription information from the electronic prescription data (FIG. 2) recorded in the ROM 113. Next, in S32, the CPU 112 determines whether or not a medicine corresponding to the target prescription information is dispensed based on the acquired prescription information, that is, the dispensed flag of the target prescription information to be processed.
If the dispensed flag is “0”, the CPU 112 determines that the dispensing has not been performed, and advances the process to S33. If the dispensed flag is “1”, the CPU 112 determines that dispensing has been completed, and advances the process to S38.

In S33, the CPU 112 executes a use period setting process for the target prescription information. In the use period setting process, the CPU 112 sets the use period of the target prescription information based on the target prescription information. The usage period setting process will be described in detail later with reference to FIG.
After the usage period setting process, in S34, the CPU 112 determines whether or not the current date and time is within the usage period based on the current date and time acquired in S11 (FIG. 4) and the usage period set in S33. If it is within the usage period, the CPU 112 advances the process to S35. If it is outside the usage period, the CPU 112 advances the process to S36.

In S35, the CPU 112 executes an undispensed notification process. In the undispensed notification process, the CPU 112 generates undispensed notification information that prescription information on undispensed information exists, and displays this on the display 115 of the portable terminal 122. Note that the process of S35 is an example of an undispensed notification information output process in which the undispensed notification information is output to the display 115 as an output device at the notification process execution timing and displayed. The undispensed notification process will be described in detail later with reference to FIG.
On the other hand, in S36, the CPU 112 acquires hospital information from the prescription information acquired in S31. Next, in S <b> 37, the CPU 112 generates reissuance notification information including the acquired hospital information and the need to reissue prescription information, and displays this on the display 115 of the portable terminal 122. The process of S37 is an example of a reissue notification information output process.
Next, in S38, the CPU 112 determines whether there is unprocessed prescription information in the electronic prescription data. If unprocessed prescription information exists, the CPU 112 advances the process to S31. When there is no unprocessed prescription information, the CPU 112 ends the dispensing notification process.

Next, the usage period setting process (S33) described in FIG. 5 will be described. FIG. 6 is a flowchart showing detailed processing in the usage period setting processing by the mobile terminal 122. First, in S39, the CPU 112 determines whether or not the use period is included in the prescription information acquired in S31 (use period information determination process). If the usage period is not included, the CPU 112 advances the process to S310. If the usage period is included, the CPU 112 advances the process to step S311.
In the present embodiment, the CPU 112 determines that the usage period is not included in the prescription information when “NULL” is recorded as the usage period of the prescription information. On the other hand, when date data is recorded as the usage period of the prescription information, the CPU 112 determines that the usage period is included in the prescription information.
In the example illustrated in FIG. 2, “NULL” is stored in the usage period of the prescription information 61 to 63. That is, the prescription information 61 to 63 does not include the use period. Therefore, CPU112 advances a process to S310, when making prescription information 61-63 into a process target. On the other hand, in the prescription information 64 shown in FIG. 2, “2012/8/30” is stored as the usage period. That is, the prescription information 64 includes a usage period. Accordingly, when the prescription information 64 is to be processed, the CPU 112 advances the process to S311.

As another example, the CPU 112 determines that there is usage period data when a date within a predetermined range is recorded as the usage period, and uses when a date outside the predetermined range is recorded. It may be determined that there is no period data. For example, when the predetermined range is “2000/1/1 to 2100/12/31”, and “1900/1/1” or “9999/12/31” is recorded as the usage period, the CPU 112 Determines that there is no usage period data. On the other hand, when “2012/8/30” is recorded as the usage period, the CPU 112 determines that there is usage period data.
As another example, the CPU 112 may determine the presence / absence of a usage period based on date data. For example, if date data is stored as the usage period, the CPU 112 determines that there is usage period data. Further, the CPU 112 determines that there is no usage period data when no data is stored and when data other than date data is stored.

Returning to FIG. 6, in S <b> 310, the CPU 112 acquires a delivery date (delivery date information) included in the target prescription information. Further, the CPU 112 calculates a date obtained by adding 3 days to the acquired delivery date as the last day of the usage period. Here, S310 is an example of a delivery date information extraction process for extracting delivery date information from the prescription information.
For example, in the case of the prescription information 61 shown in FIG. 2, the delivery date is “2012/8/1”. Therefore, the CPU 112 calculates “2012/8/4” as the last day of the usage period. In addition, the date of adding 3 days to the date of delivery is the last day of the usage period. In the “Rules for Insurance Medical Institutions and Insurance Medical Care”, the usage period of the prescription is “4 days including the delivery date (Sunday, This is due to the fact that “including holidays”.
It should be noted that the processing for calculating the usage period is not limited to the embodiment, and it is obvious that various processes such as “four days including the delivery date (including Sundays and holidays)” are included. is there. In addition, the processing for calculating the period of use may be performed by adding a predetermined number of days other than 3 days in accordance with changes in the “Rules for Insurance Medical Institutions and Insurance Medical Care”, and not including Sundays and holidays. A predetermined number of days may be added.

On the other hand, in S311, the CPU 112 subtracts an arbitrary number of days (shown as α in the figure) from the use period included in the target prescription information, and sets the result as the notification date and time. The notification date and time set in S311 is acquired in S12 (FIG. 4) described above. Note that the arbitrary number of days is set in advance in the mobile terminal 122.
Next, in S312, the CPU 112 sets the usage period included in the target prescription information as the usage period of the target prescription information. This is due to the fact that the “Rules for Insurance Medical Institutions and Insurance Medical Nutrition” stipulates that “submitted to the insurance pharmacy within 4 days including the date of delivery, unless otherwise specified”. To do. After the usage period is set in S310 or S312, the CPU 112 ends the usage period setting process.

Thus, the CPU 112 can set the usage period of the prescription information when the usage period is included in the prescription information in the usage period setting process. On the other hand, when the usage period is not included in the prescription information, the CPU 112 can set a date obtained by adding three days to the delivery date as the usage period.
For example, in the electronic prescription data shown in FIG. 2, the usage period of the prescription information 61 is set to “2012/8/4”. In addition, the usage period of the prescription information 62, 63 is set to “2012/8/18”. The usage period of the prescription information 64 is set to “2012/8/30”.

Furthermore, when the prescription information includes a use period, in the process of S311, the CPU 112 can set the notification date and time several days before the use period. As described above, the usage period data is recorded as an exceptional measure for extending the usage period of prescription information when dispensing cannot be performed within 4 days including the delivery date due to special circumstances of the patient.
Therefore, even if dispensing notification is made within 4 days from the date of delivery, it is assumed that the user cannot dispense. Therefore, when this exceptional measure is applied, it is possible to prevent useless notification of dispensing to a patient who cannot dispense by notifying several days before the use period.

<Undispensed notification process>
Next, the undispensed notification process (S35) described with reference to FIG. 5 will be described. FIG. 8 is a flowchart showing detailed processing in the undispensed notification processing by the mobile terminal 122. First, in S <b> 41, the CPU 112 of the mobile terminal 122 generates undispensed notification information based on the target prescription information, and displays the generated undispensed notification information on the display 115.
FIG. 9 is a diagram illustrating a display example of undispensed notification information. As shown in FIG. 9, the undispensed notification information in this embodiment includes three buttons 413, 414, and 415. The user of the mobile terminal 122 can press any button using the sensor of the display 115 of the mobile terminal 122.
When the user presses the button, the CPU 112 selects the type of the dispensing pharmacy and switches the subsequent processing in S42 of FIG. Specifically, when the user presses the button 413, the CPU 112 advances the process to S43. When the user presses the button 414, the CPU 112 advances the process to S44. When the user presses the button 415, the CPU 112 advances the process to S45.

In S43, S44, and S45, the CPU 112 executes family pharmacy information acquisition processing, pharmacy information acquisition processing on the normal route, and pharmacy information acquisition processing near the current position, respectively. In the present embodiment, the family pharmacy is a dispensing pharmacy that is frequently used by users of the mobile terminal 122. Moreover, the pharmacy on the normal route is a dispensing pharmacy that exists in the vicinity of a route such as a commuting route or a commuting route that is normally used by the user of the mobile terminal 122. The pharmacy near the current position is a dispensing pharmacy existing near the current position of the mobile terminal 122.
In the family pharmacy search process, the pharmacy search process on the normal route, and the pharmacy search process near the current position, the CPU 112 searches for the pharmacy to be presented to the user, and acquires the pharmacy ID indicating the detected pharmacy. To do. Details of the family pharmacy search process, the pharmacy search process on the normal route, and the pharmacy search process near the current position will be described later.

Next, in S46, the CPU 112 determines whether or not a pharmacy ID has been acquired by any one of S43, S44, or S45. When acquiring the pharmacy ID, the CPU 112 sets the acquired pharmacy ID as the target pharmacy ID to be processed, and advances the process to S47. CPU112 advances a process to S411, when not acquiring pharmacy ID.
In S47, the CPU 112 refers to pharmacy detailed data (described later), and acquires the business date and time associated with the target pharmacy ID. Next, in S48, the CPU 112 refers to pharmacy detailed data (described later) and acquires facility information associated with the target pharmacy ID. Next, in S49, with reference to pharmacy detailed data (described later), the stock status of the medicine indicated in the prescription information associated with the target pharmacy ID is acquired.

Here, pharmacy detailed data in the present embodiment will be described. FIG. 7 is a diagram illustrating an example of detailed pharmacy data referred to by the CPU 112 in the undispensed notification process. Detailed pharmacy data is stored in an area that the CPU 112 can refer to, such as the ROM 113 of the portable terminal 122. The storage location of the detailed pharmacy data is not limited to the embodiment.
As another example, at least one of the hospital terminal 121 and the pharmacy terminal 124 may store the pharmacy detailed data. In this case, the portable terminal 122 may refer to the pharmacy detailed data by accessing a terminal that stores the pharmacy detailed data.
As another example, the prescription system may include a pharmacy detailed data management device that manages pharmacy detailed data. In this case, the portable terminal 122 may refer to the pharmacy detailed data by accessing the pharmacy detailed data management device.

The pharmacy detailed data 700 stores a pharmacy ID, a pharmacy name, a location, a business date and time, facility information, a drug name, and an inventory status in association with each other. The pharmacy ID is information for identifying the pharmacy. The pharmacy name is the name of the pharmacy. The location is location information indicating the location where the pharmacy is located. The business date and time is information indicating the business day and business hours of the pharmacy. The facility information is information indicating facilities that the pharmacy has for prescription. The drug name is the name of the drug owned by the pharmacy. The stock status is the stock amount of medicines owned by the pharmacy. The inventory status may further include a scheduled delivery date and time, a scheduled delivery amount, and the like.
The pharmacy detailed data only needs to associate the pharmacy name, location, business date and time, facility information, drug name, and inventory status with the pharmacy ID, and the data structure for this is not limited to the embodiment. As another example, the detailed drug data includes location data that associates a pharmacy ID with a pharmacy name, location, business date, and facility information, and medication data that associates a pharmacy ID with a drug name and inventory status. As a separate table.

Next, in S410, the CPU 112 determines whether or not the medicine indicated in the prescription information can be dispensed in the pharmacy corresponding to the target pharmacy ID. Specifically, based on the facility information in the pharmacy detailed data 700, the CPU 112 determines whether or not the date and time when the process is executed is included in the business date and time. Furthermore, CPU112 determines whether the dispensing by the dispensing method contained in prescription information is possible based on the equipment information acquired in S48. For example, in the prescription information 62 and 63 shown in FIG. 6, unpacking is designated as the dispensing method. In this case, in S410, based on the facility information in the pharmacy detailed data 700, the CPU 112 determines whether or not the pharmacy has facilities for packaging. Further, the CPU 112 refers to the stock status acquired in S49, and based on the stock status in the pharmacy detailed data 700, the CPU 112 determines whether or not the pharmacy has an amount of medicine capable of prescribing the medicine shown in the prescription information. judge.
In all the above determinations, when it is determined that the medicine can be prescribed, the CPU 112 determines that the pharmacy corresponding to the target pharmacy ID can be dispensed, and advances the process to S412. If it is determined that prescription of medicine is not possible, the CPU 112 advances the process to S411.
In S <b> 412, the CPU 112 generates undispensed notification information for notifying that there is prescription information that has not been dispensed, along with the pharmacy name. Then, the CPU 112 displays the undispensed notification information on the display 115.

On the other hand, in S411, the CPU 112 determines whether to select another notification method. Specifically, CPU 112 displays on display 115 a window (not shown) for accepting selection of another notification method from the user of portable terminal 122. When the user gives an instruction using the sensor of the display 115, the CPU 112 accepts the instruction content. When receiving an instruction to select another notification method, the CPU 112 advances the process to S42. When receiving an instruction not to select another notification method, the CPU 112 ends the undispensed notification process.
As described above, in the prescription system according to the present embodiment, the mobile terminal 122 notifies the user of information on appropriate pharmacies that can be dispensed, while notifying that prescription information for undispensed drugs exists. it can.

<Family pharmacy search processing>
Next, the family pharmacy search process (S43) described with reference to FIG. 8 will be described. FIG. 10 is a flowchart showing detailed processing in the family pharmacy search processing by the portable terminal 122. First, in S51, the CPU 112 of the mobile terminal 122 determines whether or not a family pharmacy has already been searched. If the search has been completed, the CPU 112 advances the process to step S517. If not already searched, the CPU 112 advances the process to S52.
When the family pharmacy is detected in the family pharmacy search process, the CPU 112 stores the pharmacy information of the family pharmacy in the ROM 113 in S55 described later. Therefore, in S51, the CPU 112 determines whether or not the family pharmacy has been searched based on whether or not the pharmacy information of the family pharmacy is stored in the ROM 113.

In S517, the CPU 112 determines whether or not to search for the family pharmacy again. In step S517, the CPU 112 displays a window for instructing whether or not to search again on the display 115. The user can instruct whether to search again using the sensor of the display 115 of the CPU 112. If the re-search is instructed, the CPU 112 advances the process to S52. If the re-search is not instructed, the family pharmacy search process is terminated.
In S52, the CPU 112 refers to the electronic prescription data (FIG. 2) stored in the ROM 113, the user requests dispensing based on prescription information in the past, and searches for pharmacy information of the pharmacy where dispensing has been performed. . Specifically, the CPU 112 refers to the dispensed flag of each prescription information in the electronic prescription data, and searches for prescription information whose dispensing flag is “1”.

Next, in S53, the CPU 112 determines whether or not a pharmacy that has been dispensed in the past has been detected in S52. If at least one pharmacy is detected, the CPU 112 advances the process to S54. When the pharmacy is not detected, the CPU 112 ends the family pharmacy search process.
In S54, the CPU 112 calculates the number of dispensing for each pharmacy acquired in S52, and sorts the pharmacies in order of the number of dispensing. In S55, the CPU 112 stores the pharmacy ID of the pharmacy having the highest number of dispensings in the ROM 113 as the pharmacy ID of the family pharmacy as a result of the sorting in S52, and ends the family pharmacy search process.
Thus, the portable terminal 122 can search for a family pharmacy based on the past dispensing pharmacy information recorded in the electronic prescription data by the family pharmacy search process.

  As another example, in S55, the CPU 112 may store the pharmacy IDs of a plurality of pharmacies that are equal to or more than a predetermined number of times of dispensing in the ROM 113 as the pharmacy ID of the family pharmacy. As another example, in S55, the CPU 112 may store, in the ROM 113, the pharmacy IDs of a plurality of pharmacies having a predetermined rank or higher as the pharmacy ID of the family pharmacy.

<Pharmacy search process near current location>
Next, the pharmacy search process (S45) near the current position described with reference to FIG. 8 will be described. FIG. 11 is a flowchart showing detailed processing in the pharmacy search processing near the current position by the mobile terminal 122. First, in S <b> 56, the CPU 112 acquires current position information of the mobile terminal 122 at the time of processing execution by the GPS 1120. Next, in S57, the CPU 112 acquires a search range recorded in advance in the ROM 113. It is assumed that a user of the CPU 112 inputs a desired value in advance as a search range, and the ROM 113 of the mobile terminal 122 stores the search range input by the user in advance.
Next, in S58, the CPU 112 searches for pharmacies that exist within the search range with the current position as a reference. Specifically, the CPU 112 transmits current position information, a search range, and a character string “pharmacy” as a search query to a map service (not shown). The map service searches for pharmacies that exist within the search range based on the current position, and transmits the search result to the portable terminal 122. In response to this, the CPU 112 of the portable terminal 122 acquires the search result.

Next, in S59, the CPU 112 determines whether a pharmacy is detected in S58 based on the search result. When at least one pharmacy is detected, the CPU 112 advances the process to S510. When the pharmacy is not detected, the CPU 112 ends the pharmacy search process near the current position.
In S510, the CPU 112 stores the pharmacy ID of the pharmacy obtained by the pharmacy search acquired in S58 in the ROM 113 as the pharmacy ID of the pharmacy near the current position, and ends the process. In this embodiment, in S510, when a plurality of pharmacies are detected in S58, the CPU 112 stores the pharmacy ID of the pharmacy closest to the current position in the ROM 113 as the pharmacy ID of the pharmacy near the current position. To do.
Thus, the mobile terminal 122 can search for an appropriate pharmacy according to the position of the mobile terminal 122 by the pharmacy search process near the current position.

  As another example, in S510, when a plurality of pharmacies are detected in S58, the CPU 112 may store each of the detected pharmacy IDs of the plurality of pharmacies in the ROM 113.

<Pharmacy search process on normal route>
Next, the pharmacy search process (S44) on the normal route described with reference to FIG. 8 will be described. FIG. 12 is a flowchart showing detailed processing in the pharmacy search processing on the normal route by the mobile terminal 122. First, in S511, the CPU 112 determines whether or not a pharmacy on the normal route has already been searched. In the pharmacy search process on the normal route, when a pharmacy on the normal route is detected, the CPU 112 stores the pharmacy ID of the pharmacy on the normal route in the ROM 113 in S516 described later. That is, in S511, the CPU 112 determines whether or not a pharmacy on the normal route has been searched based on whether or not the pharmacy ID of the pharmacy on the normal route is stored in the ROM 113.
If already searched, the CPU 112 advances the process to step S518. If not already searched, the CPU 112 advances the process to step S512. In S512, the CPU 112 specifies a normal route. Here, the process of specifying the normal route will be described. In the present embodiment, the mobile terminal 122 continuously acquires the current position information by the GPS 1120 and accumulates the acquired current position information in the ROM 113 as GPS log information.
The CPU 112 of the mobile terminal 122 refers to the GPS log information, sets the current position information included in the GPS log information as coordinates on the map, and connects the coordinates with line segments in the order of the current time. The CPU 112 calculates the overlap of the line segments obtained by the above processing, and sets the line segments whose overlap is equal to or greater than a predetermined threshold as normal route information. The route through which the user of the mobile terminal 122 often passes increases the overlap of the aforementioned line segments. Therefore, the CPU 112 can calculate the normal route by the above process.

Here, an example of a normal route calculation process will be described with reference to FIGS. 13A and 13B. It is assumed that current position information 519 to 525 shown in FIG. 13A is stored in the ROM 113 of the portable terminal 122 as GPS log information. The current position information 519 indicates the current position information acquired at “Longitude: 35.56488 / Latitude 139.682086” at “2012/1/10 07:00:00”. It should be noted that the “dot” column in FIG. 13A is provided for explanation and is not included in the GPS log information. The CPU 112 plots the longitude and latitude on the map according to the current position information shown in FIG. 13A.
FIG. 13B is a diagram illustrating a plot result. Points 526 to 529 shown in FIG. 13B are obtained by the current position information 519 to 525 shown in FIG. 13A. The current position information 519 to 525 is plotted at the points shown in the “point” column in the table in FIG. 13A, respectively. As shown in FIG. 13B, the current position information 519 and 523 is plotted at the same point 526. This indicates that the current position information is acquired at the same position at different dates and times. The same applies to the current position information 520 and 524 and the current position information 521 and 525.

The CPU 112 connects the points 526 to 529 with line segments in the order of the current time, and calculates the overlap of the line segments. In the example shown in FIG. 13B, the line segments 526-527 and 527-528 overlap with each other. Further, the line segment 528-292 and the line segment 529-526 have an overlap of “1”. When the threshold value is “2”, the line segments 526-527 and the line segments 527-528, which are line segments whose overlap is “2” or more, are specified as the normal route.
Note that the CPU 112 only needs to specify the normal route based on the GPS log information stored in the ROM 113, and the specific processing for that purpose is not limited to the embodiment.

Returning to FIG. 12, after specifying the normal route, the CPU 112 acquires the search range stored in advance in the ROM 113 in step S <b> 513. Next, in S514, the CPU 112 searches for pharmacies that exist within the search range with the normal route as a reference, and acquires a search result. Next, in S515, the CPU 112 determines whether or not a pharmacy is detected in S514. If at least one pharmacy is detected, the CPU 112 advances the process to S516. When the pharmacy is not detected, the CPU 112 ends the pharmacy search process on the normal route.
In S516, the CPU 112 stores the pharmacy ID as the pharmacy search result acquired in S514 in the ROM 113 as the pharmacy ID of the pharmacy near the current position, and ends the process. In the present embodiment, in S516, when a plurality of pharmacy IDs are included in the search results acquired in S514, the CPU 112 stores the pharmacy ID closest to the current position in the ROM 113 as the pharmacy ID of the pharmacy near the current position. I decided to. Note that the processing of S514, S515, and S516 is the same as the processing of S58, S59, and S510 described with reference to FIG.

Thus, the mobile terminal 122 can search for an appropriate pharmacy based on the GPS log information of the mobile terminal 122 by the pharmacy search process on the normal route.
As another example, in S510, the CPU 112 may store a plurality of pharmacy IDs in the ROM 113 when the search result acquired in S58 includes a plurality of pharmacy IDs.

According to the dispensing notification determination process based on the date and time described above, the portable terminal 122 determines that the prescription information of undispensed information is present when there is undispensed prescription information and the current date and time is within the usage period. The patient can be notified of the remaining. On the other hand, if there is prescription information for undispensed drugs, but the current date and time are not included in the usage period, the mobile terminal 122 can notify the patient that reissue of prescription information is necessary.
Furthermore, the dispensing notification determination process based on the date and time allows the mobile terminal 122 to execute the dispensing notification process based on a preset notification interval or notification date and time. Therefore, the user of the portable terminal 122 can receive a dispensing notification or a reissue notification at an appropriate timing.

  In the dispensing notification determination process based on the date and time, the output device that is the output destination of the dispensing notification and the reissue notification is not limited to the display 115. As another example, the portable terminal 122 may output a dispensing notification and a reissue notification as audio information from a speaker. As another example, the mobile terminal 122 may transmit the dispensing notification information and the reissue notification information as an e-mail to the patient terminal 123 or the patient family terminal 125.

The dispensing notification determination process based on the date and time may be executed in at least one of the patient terminal 123 and the patient family terminal 125. In this case, the button 414 is not included in the undispensed notification information in step S42 described with reference to FIG. Then, after S42, the patient terminal 123 and the patient family terminal 125 execute either the family pharmacy search process (S43) or the pharmacy search process near the current position (S45).
As another example, the undispensed notification information displayed on the display 115 in the dispensing notification determination process based on the date and time executed at the patient terminal 123 or the patient family terminal 125 may not include pharmacy information. Further, in this case, the patient terminal 123 and the patient family terminal 125 do not execute the processes of S42 to S412 described with reference to FIG.
As another example, the dispensing notification determination process based on the date and time may be executed in at least one of the hospital terminal 121 and the pharmacy terminal 124. In this case, as described above, the undispensed notification information does not include the pharmacy information, and the hospital terminal 121 and the pharmacy terminal 124 do not execute the processes of S42 to S412.

<Dispensing notification determination process based on event>
Next, a dispensing notification determination process based on an event by the mobile terminal 122 will be described with reference to FIG. FIG. 14 is a flowchart showing a dispensing notification determination process based on an event. In the dispensing notification determination process based on the event, the portable terminal 122 executes the dispensing notification process at a timing based on the occurrence of a preset event.
The portable terminal 122 stores an event list shown in FIG. 15 in the ROM 113 in advance as a premise for performing a dispensing notification determination process based on an event. The event list has a plurality of event items. The event list 29 shown in FIG. 15 has four event items 25 to 28. Each event item includes an event ID, an event name, a dispensing notification setting, and an event monitoring method.

The event ID is an identifier that can uniquely identify an event item. The event name is a name that uniquely identifies the event item. The dispensing notification setting is information indicating whether or not to perform dispensing notification when the event specified by the event item occurs. In the event list 29 according to the present embodiment, the dispensing notification setting “1” indicates that the dispensing notification is performed, and the dispensing notification setting “0” indicates that the dispensing notification is not performed.
In the dispensing notification setting, “0” is set as an initial value. When the user of the portable terminal 122 selects a desired event for which the dispensing notification process is to be executed using the sensor of the display 115, the CPU 112 of the portable terminal 122 receives the selection by the user and is selected. Change the event dispensing notification setting to “1”. The event monitoring method is information for specifying a monitoring method for detecting that the event has occurred.

Returning to FIG. 14, in S <b> 21, the CPU 112 of the mobile terminal 122 acquires an event item for which the dispensing notification setting “1” is set among all event items included in the event list. The portable terminal 122 acquires the event items 25 and 27 from the event list 29 shown in FIG. Next, in S22, the CPU 112 monitors the event according to the event monitoring method set in the event item acquired in S21.
Next, in S23, the CPU 112 determines whether or not a target event to be monitored has occurred. If an event has occurred, the CPU 112 advances the process to S18. If no event occurs, the CPU 112 advances the process to S22.

In S18, the CPU 112 performs a dispensing notification process. This dispensing notification process is the same as the dispensing notification process (S18) during the dispensing notification determination process based on the date and time described with reference to FIG. 4, and the detailed process is described with reference to FIGS. However, the processing is the same as described above.
After the dispensing notification process, in S24, the CPU 112 determines whether or not the user of the portable terminal 122 has instructed the end of the dispensing notification determination process by an event. If termination is instructed, the CPU 112 ends a series of processing. If the termination is not instructed, the CPU 112 advances the process to S22.

Thus, in the dispensing determination process based on the event, the portable terminal 122 repeats the dispensing notification every time a registered event occurs, and ends a series of processes in accordance with an end instruction from the user.
By the dispensing notification determination process based on the event described above, the portable terminal 122 indicates that the prescription information of undispensed information is present when there is undispensed prescription information and the current date and time is within the use period. The patient can be notified of the remaining. On the other hand, if there is prescription information for undispensed drugs, but the current date and time are not included in the usage period, the mobile terminal 122 can notify the patient that reissue of prescription information is necessary.
Furthermore, the dispensing notification determination process based on the event allows the mobile terminal 122 to execute the dispensing notification process every time a preset event occurs. Therefore, the user of the portable terminal 122 can receive a dispensing notification or a reissue notification at an appropriate timing.

  In the dispensing notification determination process based on the event, the output device that is the output destination of the dispensing notification and the reissue notification is not limited to the display 115. As another example, the portable terminal 122 may output a dispensing notification and a reissue notification as audio information from a speaker. As another example, the mobile terminal 122 may transmit the dispensing notification information and the reissue notification information as an e-mail to the patient terminal 123 or the patient family terminal 125.

When a conventional paper prescription is replaced with an electronic prescription, the physical paper prescription is lost at the patient's hand. This increases the possibility of forgetting the prescription itself. As a result, patients often forget to dispense during the prescription usage period. In particular, this possibility is further increased when the usage period of the electronic prescription cannot be appropriately determined.
On the other hand, in the prescription system in the present embodiment, the mobile terminal 122 uses the prescription according to the “rules for insurance medical institutions and insurance medical care charge” in the dispensing notification determination process based on the date and time and the dispensing notification determination process based on the event. Identify how long the information has been used. Furthermore, the portable terminal 122 can perform a dispensing notification or a reissue notification to the patient based on the specified use period in these processes. Thereby, the forgetting of the medicine within the use period by the patient in the electronic prescription can be reduced.

  Note that the mobile terminal 122 may simultaneously execute the dispensing notification determination process based on the date and time described with reference to FIG. 4 and the like, and the dispensing notification determination process based on the event described with reference to FIG. In this case, the portable terminal 122 can execute the dispensing notification process at a predetermined notification interval, a specified notification date and time, and a timing when a registration event occurs.

<Example of change>
Next, a first modification of the prescription system according to the first embodiment will be described. In the prescription system according to the first embodiment, in the portable terminal 122, the notification interval referred to by the CPU 112 of the portable terminal 122 in the dispensing notification determination process based on the event is stored in the ROM 113 in advance. Instead of this, the mobile terminal 122 may determine the notification interval according to the type of medicine included in the target prescription information to be processed.
Furthermore, in the prescription system according to the first embodiment, the portable terminal 122 displays dispensing notification information on the display 115 to perform dispensing notification to the user (patient). Instead, the portable terminal 122 may perform dispensing notification by a plurality of methods. Furthermore, the portable terminal 122 may determine an appropriate notification method from a plurality of notification methods according to the type of medicine included in the target prescription information.

Specific processing will be described below. The portable terminal 122 stores an importance level table, a notification interval table, and a notification method table in the ROM 113 in advance. FIG. 16A is a diagram illustrating an example of an importance level table. In the importance level table, drug names and importance levels are associated with each other. FIG. 16B is a diagram illustrating an example of a notification interval table. In the notification interval table, the importance and the notification interval are associated with each other. FIG. 16C is a diagram illustrating an example of a notification method table. In the notification method table, the importance and the notification method are associated with each other.
In the notification method table shown in FIG. 16C, one or more notification methods among “mobile terminal notification”, “personal mail notification”, and “agent mail notification” are associated with each importance level. Yes. It is assumed that the notification method indicated by “◯” in the figure is associated. The “mobile communication notification” is a method for displaying a dispensing notification on the display 115 of the mobile terminal 122 as the mobile terminal 1116 or the like. “Principal email notification” is a method of sending a dispensing notification to the patient's email address. “Agent email notification” is a method of sending a dispensing notification to the email address of an agent such as a patient's family.

FIG. 17 is a follow chart showing notification interval setting processing by the portable terminal 122. The notification interval setting process is executed in response to a start instruction from the user of the mobile terminal 122. The user of the portable terminal 122 can execute the notification interval setting process at a desired timing by inputting a start instruction.
In the notification interval setting process, first, in S131, the CPU 112 of the portable terminal 122 identifies target prescription information to be processed from the electronic prescription data. Further, the CPU 112 acquires the medicine name from the target prescription information. Next, in S132, the CPU 112 refers to the importance level table and acquires the importance level of the medicine corresponding to the acquired medicine name.

Next, in S133, the CPU 112 refers to the notification interval table and sets the notification interval according to the importance of the acquired medicine. Here, the importance is a value determined according to the drug name, that is, the type of drug. The notification interval is a time interval for executing the dispensing notification. That is, the process of S133 is an example of a time interval determination process that determines a time interval based on the type of medicine.
When the notification interval table illustrated in FIG. 16B is referred to, the notification interval “3 times / Notification intervals of “day”, “twice / day”, and “once / day” are set. Furthermore, in S134, the CPU 112 refers to the notification method table and sets a notification method according to the importance of the acquired medicine.
Next, in S135, the CPU 112 determines whether there is unprocessed prescription information. If unprocessed prescription information exists, the CPU 112 advances the process to S131. When there is no unprocessed prescription information, the CPU 112 ends the notification interval setting process.

Thus, according to this example, the portable terminal 122 can shorten the notification interval for the dispensing notification for the medicine with higher importance. In addition, the mobile terminal 122 can perform dispensing notification for medicines with higher importance by various notification methods. Thereby, it is possible to prevent the patient from forgetting to dispense the medicine with high importance.
The importance level table, the notification interval table, and the notification method table may be stored in a server device (not shown), for example. In this case, the portable terminal 122 transmits the medicine name included in the target prescription information to the server device. Then, the notification interval setting process is executed in the server device. The server device transmits the notification interval and the notification method obtained as a result of the notification interval setting process to the mobile terminal 122. The portable terminal 122 receives the notification interval and the notification method from the server device, and uses the received notification interval and notification method.

As another example, only the importance level table may be stored in a server device (not shown). In this case, the server device receives the medicine name from the portable terminal 122 and transmits the importance corresponding to the medicine name to the portable terminal 122. Then, the mobile terminal 122 receives the importance, and determines the notification interval and the notification method based on the received importance by referring to the notification interval table and the notification method table included in the mobile terminal 122.
The notification method is not limited to “mobile terminal notification”, “personal mail notification”, and “agent mail notification”. The portable terminal 122 may set and execute various other notification methods.

(Second Embodiment)
Next, a prescription system according to the second embodiment will be described. In the prescription system according to the second embodiment, the mobile terminal 122 transmits electronic prescription data to the patient terminal 123. Then, the patient terminal 123 uses a printer 1111 to print a calendar representing the usage period of each prescription information included in the electronic prescription data and a map representing a pharmacy.
In the prescription system according to the second embodiment, prescription information is first transmitted from the hospital terminal 121 to the patient's portable terminal 122 after the examination in the hospital, as in the prescription system according to the first embodiment. And prescription information is accumulate | stored in the electronic prescription data in a patient's portable terminal 122. FIG.
When the patient desires to print the prescription information in the mobile terminal 122, the patient brings the mobile terminal 122 closer to the patient terminal 123. Thereby, prescription information is transmitted from the portable terminal 122 to the patient terminal 123 via the wireless module 119 of the portable terminal 122 and the patient terminal 123. The patient terminal 123 generates a calendar image indicating the expiration date of the prescription information and a map indicating a pharmacy suitable for prescription, and prints it using the printer 1111.

<Electronic prescription output processing>
FIG. 18 is a flowchart showing electronic prescription output processing by the patient terminal 123. First, in S71, the CPU 112 of the patient terminal 123 acquires one prescription information from the electronic prescription data recorded in the HD 117. Next, in S33, the CPU 112 of the patient terminal 123 uses the acquired prescription information as target prescription information to be processed, and executes a use period setting process. This use period setting process is the same process as the use period setting process described with reference to FIG. 6 in the first embodiment.
Subsequently, in S72, the CPU 112 determines whether there is unprocessed prescription information in the electronic prescription data. If there is unprocessed prescription information, the CPU 112 advances the process to S71. If there is no unprocessed prescription information, the CPU 112 advances the process to S73.
In S73, the CPU 112 executes a calendar generation process using the usage period acquired in S33. FIG. 19 is a diagram illustrating an example of a print image including a calendar image generated by the patient terminal 123. A calendar image 78 in the print image 710 shown in FIG. 19 is generated based on the electronic prescription data shown in FIG. In the calendar image 78 shown in FIG. 19, the date when the prescription information is used is indicated by white letters (4th, 18th, and 30th in the figure). Here, the expiration date is the last day of the usage period. That is, the calendar image 78 is an image obtained by combining the usage periods on the calendar.

In FIG. 2, for the prescription information 61 to 63 whose usage period is “NULL”, the last day of the usage period “2012/8/4” and “2012/18” are set in S33 of the electronic prescription output process. Correspondingly, in the calendar image 78, the last day of these use periods is set correctly. As for the prescription information 64, “2012/8/30”, which is the last day of the usage period recorded in the electronic prescription data, is set in the calendar image 78.
As described above, in the prescription system according to the present embodiment, the patient terminal 123 sets an appropriate use period for each prescription information and displays it on the calendar regardless of whether or not the use period is recorded in the electronic prescription. Can do.
Although the patient terminal 123 displays the date on the calendar with white letters, the present invention is not limited to this. For example, the patient terminal 123 may display the expiration dates as a list in order of date, or may display other prescription information such as hospital information, delivery date, and drug name in addition to the expiration dates. Thus, the patient terminal 123 can output the expiration date of prescription information by various methods.

Next, in S74, the CPU 112 of the patient terminal 123 selects a type of pharmacy to be displayed on the map in accordance with an instruction from the user. More specifically, the CPU 112 causes the display 115 to display a window (not shown) in which the pharmacy type can be selected. Then, the CPU 112 receives the pharmacy type input by the user using the mouse 1113 or the keyboard 1114.
If the family pharmacy is instructed, the CPU 112 advances the process to S43. When the pharmacy on the normal route is instructed, the CPU 112 advances the process to S44. The process of S43 is the same as the family pharmacy search process described with reference to FIG. The processing of S44 is the same as the pharmacy search processing on the normal route described with reference to FIG. In addition, the patient terminal 123 shall acquire GPS log information regularly from the portable terminal 122 as a premise of the pharmacy search process on a normal route, and shall store this in ROM113 grade | etc.,.
As another example, when the patient terminal 123 includes the GPS 1120, the CPU 112 may be able to select a pharmacy near the current position in selecting the pharmacy type. In this case, when a pharmacy near the current position is selected, S45 (FIG. 8) is executed.

Next, in S75, the CPU 112 determines whether or not a pharmacy ID has been acquired in S43 or 44. When the pharmacy ID is acquired, the CPU 112 advances the process to S76. When not acquiring, CPU112 advances a process to S77. In S76, the CPU 112 executes map data generation processing based on the pharmacy ID acquired in S43 or S44.
In the map data generation process, for example, map data 79 in the print image 710 shown in FIG. 19 is generated. Note that map data 79 shown in FIG. 19 is an example of map data when a family pharmacy is selected in S74. When the pharmacy ID of the family pharmacy is acquired in S43, the CPU 112 generates a map image including the family pharmacy based on the location in the detailed pharmacy data specified by the acquired pharmacy ID. Further, as shown in the map data 79, the location of the user of the patient terminal 123 and the location of the company may be included in the map image.

In step S <b> 77, the CPU 112 generates a print image 710 as final output data, and then outputs the generated print image 710 using the printer 1111. The other configurations and processes of the prescription system according to the second embodiment are the same as the configurations and processes of the prescription system according to the first embodiment.
Thus, in the prescription system concerning this embodiment, the expiration date with respect to each prescription information and the map which shows an appropriate pharmacy can be outputted to a paper medium.

(Third embodiment)
The prescription system according to the third embodiment is applied when a paper prescription is issued. When a paper prescription is submitted to the dispensing pharmacy, the patient terminal 123 reads the description of the paper prescription by the scanner 1112 and accumulates it in the electronic prescription data as prescription information.
The prescription system according to the third embodiment will be described below. In the prescription system according to the third embodiment, the patient receives a paper prescription from the hospital after the examination at the hospital, as in the past. Then, the patient submits a paper prescription to the dispensing pharmacy at the time of dispensing request. In the dispensing pharmacy, the pharmacy terminal 124 scans a paper prescription using the scanner 1112, executes character recognition processing (OCR processing) on the scanned prescription image, and stores the character-recognized prescription information in the pharmacy terminal 124. Is stored in the electronic prescription data.
As a result, the pharmacist can refer to the electronic prescription data in the pharmacy terminal 124 and perform appropriate dispensing. In particular, in the present embodiment, the pharmacist can appropriately determine the usage period of the prescription and can perform appropriate dispensing according to the usage period. For example, only prescription information within the period of use can be dispensed.

<Electronic prescription processing for paper>
FIG. 20 is a flowchart showing the paper prescription digitization process by the pharmacy terminal 124. First, in S81, the CPU 112 of the pharmacy terminal 124 scans a paper prescription using the scanner 1112 and acquires a prescription image as prescription information (prescription information acquisition processing).
Next, in S82, the CPU 112 specifies a prescription form using the prescription image. Here, the form is information for identifying which information in the prescription is recorded in which region in the prescription image, that is, the layout. For example, it is specified that “patient name” is recorded in a rectangular area having vertices at (10, 10), (10, 210), (1010, 10), and (1010, 210) in the prescription image. The

Next, in S83, the CPU 112 executes a usage period setting process to set a usage period. The usage period setting process will be described later in detail with reference to FIG. After the use period setting process, in step S84, the CPU 112 outputs each digitized prescription information to the HD 117 as electronic prescription data (for example, FIG. 2), and ends the paper prescription digitization process.
Next, the usage period setting process (S83) described with reference to FIG. 20 will be described. FIG. 21 is a flowchart showing detailed processing in the usage period setting processing by the pharmacy terminal 124. First, in S85, the CPU 112 of the pharmacy terminal 124 specifies the expiration date area in the prescription image based on the form specified in S82 (use period area specifying process). Next, in S86, the pharmacy terminal 124 executes a character cut process within the expiration date area specified in S85. Here, the expiration date area specifying process (S85) and the expiration date area character cutting process (S86) will be described.

22A and 22B are examples of a scan image of a prescription in which a use period is described. In the scanned images shown in FIGS. 22A and 22B, the area 91 is specified as the use period area in S85. Furthermore, the period of use is described in the area 91. For this reason, in S86, “flat”, “sei”, “2”, “4”, “year”, “1”, “0”, “month”, “1”, “4”, “day” Each character area is cut out as a rectangular area (that is, the number of characters is “11”).
On the other hand, FIG. 23A and FIG. 23B are examples of a scan image of a prescription in which the period of use is not described. In the scanned images shown in FIGS. 23A and 23B, the area 92 is specified as the use period area in S85. In the area 92, the use period is not described. Therefore, no character region is cut out from the region 92 in S86 (that is, the number of characters is “0”).

After the character cutting process, in S87, the CPU 112 regards the number of rectangular areas in the expiration date area as the number of characters and counts the number of characters (character number counting process). Then, the CPU 112 compares the number of characters with a threshold value set in advance in the ROM 113 or the like. If the number of characters is greater than the threshold, the CPU 112 advances the process to S812. If the number of characters is equal to or less than the threshold, the CPU 112 advances the process to S88.
For example, when the threshold value is “0”, when the scan image shown in FIG. 22A is obtained, the CPU 112 advances the process to S812, and when the scan image shown in FIG. 23A is obtained. The CPU 112 advances the process to 88.

In S88, the CPU 112 specifies the delivery date area in the prescription image based on the form specified in S82. Next, in S89, the CPU 112 executes a character cut process in the delivery date area specified in S88. In the example illustrated in FIG. 23B, the area 93 is specified as the delivery date area. Further, when character cut processing is executed in the specified area 93, the result is “flat”, “sei”, “2”, “4”, “year”, “1”, “0”, “month” The character areas “”, “1”, and “day” are cut out as rectangular areas.
Next, in S810, the CPU 112 executes a character recognition process (OCR process) for the rectangular area corresponding to each character area cut out in S89. Next, in S811, the CPU 112 sets a date obtained by adding 3 days to the delivery date recognized by the OCR process as the last day of the usage period. In the example shown in FIG. 23B, “October 4, 2012” is set as the last day of the usage period.

On the other hand, in S812, the CPU 112 executes a character recognition process (OCR process) for each rectangular area corresponding to the character area cut out in S86. Next, in S813, the CPU 112 sets the description content of the usage period recognized by the OCR process as the last day of the usage period.
In step S <b> 814, the CPU 112 executes character cutting processing on an area of the paper prescription that has not been subjected to character recognition processing. In step S815, the CPU 112 executes character recognition processing (OCR processing) for the area subjected to character cut processing. The CPU 112 stores each piece of information obtained by the character recognition process in the electronic prescription data, and ends a series of processes.

As described above, in the prescription system according to the third embodiment, regardless of the use period described in the paper prescription, the use period is set in accordance with the “Insurance Medical Institution and Insurance Medical Care Rules”, and the electronic It can be recorded as prescription data.
The other configurations and processes of the prescription system according to the third embodiment are the same as the configurations and processes of the prescription systems according to the other embodiments.

(Fourth embodiment)
The prescription system according to the fourth embodiment is applied when a paper prescription on which a barcode as a pattern code is drawn is issued. In the barcode, prescription information such as the patient name, delivery date and time, and expiration date is embedded according to a predetermined format.
Hereinafter, the prescription system according to the fourth embodiment will be described. In the prescription system according to the fourth embodiment, the patient receives a paper prescription after the medical examination at the hospital. Then, the patient submits a paper prescription to the dispensing pharmacy at the time of dispensing request. In the dispensing pharmacy, the pharmacy terminal 124 uses the barcode reader 1115 to read the content of the barcode attached to the paper prescription, that is, prescription information. The pharmacy terminal 124 accumulates the read prescription information in the electronic prescription data provided in itself.
As a result, the pharmacist can perform appropriate dispensing using the electronic prescription data in the pharmacy terminal 124. In particular, in the present embodiment, the pharmacist can appropriately determine the usage period of the prescription and can perform appropriate dispensing according to the usage period.

<Barcode prescription reading process>
FIG. 24 is a flowchart showing barcode prescription reading processing by the pharmacy terminal 124. First, in S <b> 101, the CPU 112 of the pharmacy terminal 124 inputs a barcode added to a paper prescription using the barcode reader 1115. Next, in S102, the CPU 112 reads the content of the barcode and acquires pattern code information as prescription information (prescription information acquisition processing).
FIG. 25A and FIG. 25B are diagrams illustrating an example of a paper prescription with a barcode attached thereto. In the bar code 103 shown in FIG. 25A and the bar code 104 shown in FIG. 25B, the contents described in the prescription to which the bar codes 103 and 104 are assigned are embedded according to a predetermined format. In the present embodiment, it is assumed that CSV (Comma Separated Values) format data as shown in 105 and 106 is embedded.

Each line of CSV data (separated by a line feed code “CRLF”) corresponds to each description item in the prescription. In each row of CSV data, “item identifier” and “item content” are recorded in order from the top. The item identifiers “01”, “02”, “03”, “04” and “05” are “patient name”, “birth date”, “delivery date”, “expiration date” and “prescription information”, respectively. Is assigned.
The prescription information 105 is obtained from the barcode 103 shown in FIG. 25A. In addition, prescription information 106 is obtained from the barcode 104 shown in FIG. 25B. In the prescription information 105 obtained from the barcode 103 shown in FIG. 25A, use period information “H241014” corresponding to the use period “October 14, 2012” described in the paper prescription is embedded. On the other hand, the prescription information 106 obtained from the barcode 104 shown in FIG. 25B corresponds to the fact that the usage period is not described in the paper prescription information, and does not include the usage period information.
Note that the format of the data in the barcode is not limited to the CSV format. Various formats such as XML (Extensible Markup Language) can be adopted as the format of data in the barcode.

In S102 of FIG. 24, after the barcode is read, in S33, the CPU 112 executes a use period setting process based on the obtained prescription information. This use period setting process is the same as the use period setting process described with reference to FIG. 6 in the first embodiment.
For example, it is assumed that prescription information 105 shown in FIG. 25A is obtained. The prescription information 105 includes data of usage period information “H241014”. For this reason, in S39, the CPU 112 advances the process to S311. On the other hand, it is assumed that prescription information 106 shown in FIG. 25B is obtained. This prescription information 106 does not include usage period information. Therefore, in S39, the CPU 112 advances the process to S310.
In S84, the CPU 112 outputs the digitized prescription information to the HD 117 as electronic prescription data (for example, FIG. 2). In S84, the CPU 112 may output data other than the usage period data included in the CSV data to the electronic prescription data in addition to the usage period set in S33.
The other configurations and processes of the prescription system according to the fourth embodiment are the same as the configurations and processes of the prescription systems according to the other embodiments.

  As described above, in the prescription system according to the fourth embodiment, regardless of whether or not the usage period is embedded in the barcode attached to the paper prescription, The usage period can be set according to the “Rules”. Furthermore, the set use period can be stored in the electronic prescription data.

<Other embodiments>
The present invention can also be realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media. Then, the computer (or CPU, MPU, etc.) of the system or apparatus reads and executes the program.

  As mentioned above, according to each embodiment mentioned above, the mechanism which specifies the suitable use period of an electronic prescription can be provided.

  The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to such specific embodiments, and various modifications can be made within the scope of the gist of the present invention described in the claims.・ Change is possible.

Claims (27)

From the prescription information on the prescription, a delivery date information acquisition means for acquiring delivery date information indicating a delivery date of the prescription,
Use period information determining means for determining whether the prescription information includes use period information indicating a use period of the prescription;
When the usage period information is included in the prescription information, the usage period indicated by the usage period information is set as the usage period of the prescription, and when the usage period information is not included in the prescription information , Based on the delivery date information, use period setting means for setting a use period of the prescription,
A notification output means for outputting a notification relating to the prescription;
Have
The notification output means is output at a timing based on the use period indicated by the use period information when the use period indicated by the use period information is set as the use period of the prescription by the use period setting means . processing of the output of the notification, characterized in that starting with the second alert output and a different timing when the life of the prescription based on the delivery date information is set by the use period setting means apparatus. The notification output means, wherein, when said use period information by use period setting means is used period indicated is set as the use period of the prescription, the after the end of the period of use the use period information indicating a predetermined period before without outputting the first notification to the timing, the information processing apparatus according to claim 1, characterized in that to start the output of the first notification after said timing. The notification output unit is configured to detect the first notification when a predetermined event is detected even when the use period indicated by the use period information is set as the use period of the prescription by the use period setting unit. The information processing apparatus according to claim 2, wherein: The notification output means, when said period of use of the prescription based on the delivery date information is set by a period setting means, before Kita timing the output of the second notification in the previous timing from The information processing apparatus according to claim 2, wherein the information processing apparatus is started. The notification output means, when the use period of the prescription is set based on the delivery date information by the use period setting means, after the start of the output of the second notification, at the predetermined time interval . 5. The information processing apparatus according to claim 4, wherein the output of the notification of 2 is repeated.   The information processing apparatus according to claim 1, wherein the notification includes information on an insurance pharmacy specified based on position information of the information processing apparatus.   The information processing apparatus according to claim 6, wherein the insurance pharmacy is a pharmacy capable of dispensing a medicine based on the prescription information. Storage means for storing the prescription information and the dispensation information indicating whether or not the dispensation corresponding to the prescription information is performed;
The notification output means includes the prescription information that is not dispensed based on the dispensing information when the date and time when the process is executed is within the use period set by the use period setting means. The information processing apparatus according to any one of claims 1 to 7, wherein the information is output.   The notification output means notifies that a prescription for the prescription information that is not dispensed needs to be reissued based on the dispensing information when the date and time at the time of processing execution is outside the use period. The information processing apparatus according to claim 8, wherein the information processing apparatus outputs the information processing apparatus. A time interval determining means for determining a time interval for outputting the second notification based on the type of medicine shown in the prescription information;
10. The information processing according to claim 1, wherein the notification output unit outputs the second notification based on the time interval determined by the time interval determination unit. apparatus.   The information processing apparatus according to claim 1, wherein the notification output unit outputs a calendar image obtained by combining the usage period set by the usage period setting unit on a calendar. Prescription information acquisition means for acquiring a prescription image corresponding to a paper prescription as the prescription information;
Based on the layout of the paper prescription, use period area specifying means for specifying a use period area in which the use period is displayed from the prescription image;
A character number counting means for counting the number of characters displayed in the use period area, and
The information processing apparatus according to claim 1, wherein the usage period information determination unit determines whether the usage period information is included based on the number of characters. A prescription information acquisition means for acquiring pattern code information drawn on a paper prescription as the prescription information;
The information processing apparatus according to claim 1, wherein the usage period information determination unit determines whether or not the usage period information is included in the pattern code information. An information processing method executed by an information processing apparatus,
A delivery date information acquisition step for acquiring delivery date information indicating a delivery date of the prescription from prescription information related to the prescription;
A use period information determination step for determining whether the prescription information includes use period information indicating a use period of the prescription;
When the use period information is included in the prescription information, the use period indicated by the use period information is set as the use period of the prescription, and when the use period information is not included in the prescription information , A use period setting step for setting a use period of the prescription based on the delivery date information;
A notification output step for outputting a notification about the prescription;
Including
The notification output step is a first output at a timing based on the use period indicated by the use period information when the use period indicated by the use period information is set as the use period of the prescription in the use period setting step. processing of the output of the notification, characterized in that starting with the second alert output and a different timing when the life of the prescription based on the delivery date information in the use period setting step is set Method. The notification output step, when said the use period information by use period setting step is used period indicated is set as the use period of the prescription, before a predetermined period after the end of the use period indicated by the use period information said without outputting the first notification to the timing information processing method according to claim 14, characterized in that to start the output of the first notification after said timing. The notification output step includes the first notification when a predetermined event is detected even when the usage period indicated by the usage period information is set as the usage period of the prescription in the usage period setting step. The information processing method according to claim 15, wherein: The notification output step, when said period of use of the prescription based on the delivery date information by using the period setting step is set, before Kita timing the output of the second notification in the previous timing from 17. The information processing method according to claim 15 or 16, characterized by starting an operation. In the notification output step, when the usage period of the prescription is set based on the delivery date information in the usage period setting step, the output of the second notification is started at a predetermined time interval after the start of the output of the second notification . The information processing method according to claim 17, wherein the output of the notification of 2 is repeated.   The information processing method according to any one of claims 14 to 18, wherein the notification includes information on an insurance pharmacy identified based on position information of the information processing apparatus.   The information processing method according to claim 19, wherein the insurance pharmacy is a pharmacy capable of dispensing a medicine based on the prescription information. Computer
From the prescription information on the prescription, a delivery date information acquisition means for acquiring delivery date information indicating a delivery date of the prescription,
Use period information determining means for determining whether the prescription information includes use period information indicating a use period of the prescription;
When the usage period information is included in the prescription information, the usage period indicated by the usage period information is set as the usage period of the prescription, and when the usage period information is not included in the prescription information , Based on the delivery date information, use period setting means for setting a use period of the prescription,
A program for functioning as a notification output means for outputting a notification related to the prescription,
The notification output means is output at a timing based on the use period indicated by the use period information when the use period indicated by the use period information is set as the use period of the prescription by the use period setting means . the output of the notification, the program characterized by starting the output of the second notification when the use period of the prescription based on the delivery date information is set at different timings by the use period setting means. The notification output means, wherein, when said use period information by use period setting means is used period indicated is set as the use period of the prescription, the after the end of the period of use the use period information indicating a predetermined period before without outputting the first notification to the timing program according to claim 21, characterized in that to start the output of the first notification after said timing. The notification output unit is configured to detect the first notification when a predetermined event is detected even when the use period indicated by the use period information is set as the use period of the prescription by the use period setting unit. The program according to claim 22, wherein the program is output. The notification output means, when said period of use of the prescription based on the delivery date information is set by a period setting means, before Kita timing the output of the second notification in the previous timing from 24. The program according to claim 22 or 23, wherein the program starts. The notification output means, when the use period of the prescription is set based on the delivery date information by the use period setting means, after the start of the output of the second notification, at the predetermined time interval . 25. The program according to claim 24, wherein the output of the notification of 2 is repeated.   The program according to any one of claims 21 to 25, wherein the notification includes information on an insurance pharmacy specified based on position information of the computer.   27. The program according to claim 26, wherein the insurance pharmacy is a pharmacy capable of dispensing a medicine based on the prescription information.

Images