Medication history management system and medication history management program

Abstract

To provide a medication history management system and a medication history management program which easily reduce the time and labor required for medication history management.SOLUTION: A medication history management system 10 comprises a server 1, a client terminal 2, and a printer 3. The server includes: an output processing unit 112 for outputting medication history information regarding the use days of medicine; and a change processing unit 113 for changing medication history information with regard to use days other than the target day corresponding to the same group as the target day in accordance with a user operation of changing medication history information including an operation of designating one or a plurality of days corresponding to a group as a target day.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a medication history management system and a medication history management program for managing the medication history regarding the use date of medications.

Background Art

[0002] As a related art, there is known a system that causes a client terminal to display a management screen including a medication history such as a prescription history of medications and a medication administration history of medications according to a therapy for each patient (see, for example, Patent Document 1). In the system according to the related art, the control unit displays cells (medication history areas) corresponding to each combination of a date and a type of medication or regimen in a matrix form on the management screen. Then, in each of the cells, the control unit displays the presence or absence of taking the medication on the date corresponding to the cell or drug administration according to the regimen.

[0003] In the system according to the related art, the control unit updates medication history data and regimen history data based on prescription data input from an upper system, and displays the medication history based on the medication history data and the regimen history data. Users such as pharmacists often refer to the management screen for the purpose of referring to past data.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] Incidentally, regarding medications such as oral anticancer drugs, unlike injectable drugs which are administered by doctors or nurses, patients often manage their own use (taking) of the medication, making it difficult to manage medication history using a system. For example, if the prescription date included in the prescription data is set as the start date of use on the management screen, and the actual start date of use when the patient begins using the medication differs from the prescription date, then accurately managing the medication history requires correcting multiple cells on the management screen. Therefore, for pharmacists and other users, this correction work can increase the effort required to manage medication history per patient, leading to an increased burden.

[0006] The objective of the present invention is to provide a medication history management system and a medication history management program that make it easier to reduce the effort involved in managing medication history. [Means for solving the problem]

[0007] A medication history management system according to one aspect of the present invention comprises an output processing unit and a modification processing unit. The output processing unit outputs medication history information relating to the date of drug use. The modification processing unit includes an operation to designate one or more of the aforementioned dates of use corresponding to a group as target dates, and modifies the medication history information for usage dates other than the target dates that correspond to the same group as the target dates, in accordance with a user operation to modify the medication history information.

[0008] A medication history management system according to another aspect of the present invention comprises an output processing unit, a modification processing unit, and a type-based restriction processing unit. The output processing unit outputs medication history information relating to the date of use of a drug selected from a plurality of types. The modification processing unit modifies the medication history information according to user operations. The type-based restriction processing unit restricts the modification of the medication history information by the modification processing unit according to the type of drug.

[0009] A medication history management system according to another aspect of the present invention comprises an output processing unit, a modification processing unit, and a daily restriction processing unit. The output processing unit outputs medication history information relating to the dates of drug use. The modification processing unit modifies the medication history information according to a user operation that includes an operation to specify one or more of the dates of use as target dates. The daily restriction processing unit restricts the modification of the medication history information by the modification processing unit according to the target dates.

[0010] A medication history management program according to another aspect of the present invention is a program that causes a computer to perform an output step of outputting medication history information relating to the date of drug use, an operation of specifying one or more of the aforementioned dates of use corresponding to a group as target dates, and a modification step of modifying the medication history information for usage dates other than the target dates that correspond to the same group as the target dates, in accordance with a user operation to modify the medication history information. [Effects of the Invention]

[0011] According to the present invention, it is possible to provide a medication history management system and a medication history management program that make it easier to reduce the effort required for medication history management. [Brief explanation of the drawing]

[0012] [Figure 1] Figure 1 is a block diagram showing an example of a medication history management system according to an embodiment of the present invention. [Figure 2] Figure 2 shows an example of the relationship between the target date and the type of change in medication history information used in a medication history management system according to an embodiment of the present invention. [Figure 3] Figure 3 shows an example of a display screen shown in a medication history management system according to an embodiment of the present invention. [Figure 4] Figure 4 shows an example of a display screen related to the processing of changing the start date, which is displayed in a medication history management system according to an embodiment of the present invention. [Figure 5] Figure 5 shows an example of a display screen related to the processing of changing the start date, which is displayed in a medication history management system according to an embodiment of the present invention. [Figure 6] FIG. 6 is a diagram showing an example of a display screen related to the binding process, which is displayed on the medication history management system according to an embodiment of the present invention. [Figure 7] FIG. 7 is a diagram showing an example of a display screen related to the binding process, which is displayed on the medication history management system according to an embodiment of the present invention. [Figure 8A] FIG. 8A is a diagram showing an example of a display screen related to the binding process, which is displayed on the medication history management system according to an embodiment of the present invention. [Figure 8B] FIG. 8B is a diagram showing an example of a display screen related to a binding process different from that in FIG. 8A, which is displayed on the medication history management system according to an embodiment of the present invention. [Figure 9] FIG. 9 is a diagram showing an example of a display screen related to the binding process, which is displayed on the medication history management system according to an embodiment of the present invention. [Figure 10] FIG. 10 is a diagram showing an example of a display screen related to the splitting process, which is displayed on the medication history management system according to an embodiment of the present invention. [Figure 11A] FIG. 11A is a diagram showing an example of a display screen related to the splitting process, which is displayed on the medication history management system according to an embodiment of the present invention. [Figure 11B] FIG. 11B is a diagram showing an example of a display screen related to a splitting process different from that in FIG. 11A, which is displayed on the medication history management system according to an embodiment of the present invention. [Figure 12] FIG. 12 is a diagram showing an example of a display screen related to the process of adding a usage date, which is displayed on the medication history management system according to an embodiment of the present invention. [Figure 13] FIG. 13 is a diagram showing an example of a display screen related to the pattern change process, which is displayed on the medication history management system according to an embodiment of the present invention. [Figure 14A] FIG. 14A is a diagram showing an example of a display screen related to the pattern change process, which is displayed on the medication history management system according to an embodiment of the present invention. [Figure 14B] FIG. 14B is a diagram showing an example of a display screen related to a pattern change process different from that in FIG. 14A, which is displayed on the medication history management system according to an embodiment of the present invention. [Figure 15]FIG. 15 is a diagram showing an example of a display screen related to the cancellation process, which is displayed on the medication history management system according to an embodiment of the present invention. [Figure 16] FIG. 16 is a flowchart for explaining an example of the procedure of the medication history management process executed in the medication history management system according to an embodiment of the present invention. [Figure 17] FIG. 17 is a flowchart for explaining another example of the procedure of the medication history management process executed in the medication history management system according to an embodiment of the present invention. [Figure 18] FIG. 18 is a diagram showing an example of a display screen related to the merging (continuous administration) process, which is displayed on the medication history management system according to an embodiment of the present invention. [Figure 19] FIG. 19 is a diagram showing an example of a display screen related to the merging (intermittent administration) process, which is displayed on the medication history management system according to an embodiment of the present invention. [Figure 20] FIG. 20 is a diagram showing an example of a display screen related to the process of changing the prescribed dose, which is displayed on the medication history management system according to an embodiment of the present invention.

Mode for Carrying Out the Invention

[0013] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings to facilitate understanding of the present invention. The following embodiments are an example of embodying the present invention and do not have the character of limiting the technical scope of the present invention. Also, the configurations and processing functions described in the following embodiments can be arbitrarily combined by selection.

[0014] [Medication History Management System 10] As shown in Figure 1, the medication history management system 10 according to an embodiment of the present invention comprises a server 1, a client terminal 2, and a printer 3, etc. The server 1, the client terminal 2, and the printer 3 are connected wirelessly or via wired communication through a communication network NT1. The communication network NT1 includes LAN (Local Area Network), WAN (Wide Area Network), the Internet, or an intranet. Furthermore, a higher-level system 5 is connected to the server 1 via the communication network NT1. The medication history management system 10 may have multiple instances of at least one of the server 1, the client terminal 2, and the printer 3. In Figure 1, as an example, multiple (2) client terminals 2 are provided.

[0015] Users of the medication history management system 10 include, for example, pharmacists, doctors, nurses, medical staff, or facility managers at medical institutions such as hospitals, nursing homes, or pharmacies. In this embodiment, as an example, the medication history management system 10 is used in a hospital, and the users of the medication history management system 10 are the hospital's pharmacists (hospital pharmacists).

[0016] The aforementioned medication history management system 10 has a function to manage information such as medication history for each patient. In particular, in this embodiment, the medication history management system 10 is used to manage information such as the type of drug, the date of drug use (including administration date and day of administration), and the amount used (regimen information) related to cancer chemotherapy (hereinafter simply referred to as "therapy"). In other words, the medication history management system 10 according to this embodiment is a therapy management system for managing information related to therapy, and as one of its functions, it has a function to manage medication history information of drugs such as anticancer drugs according to therapy.

[0017] Furthermore, in this embodiment, unless otherwise specified, the "drugs" subject to management of drug history in the drug history management system 10 are anticancer drugs used in therapy. Anticancer drugs include multiple types of drugs, including injectable drugs and oral drugs, and the "drugs" subject to management of drug history in the drug history management system 10 include at least two types of drugs: injectable drugs and oral drugs. In addition, the "use" of drugs as used in this disclosure includes "taking" the drug when it is an oral drug, and "administration" when it is an injectable drug. In other words, if the drug is an oral drug, the "use date" is the "taking date," and if the drug is an injectable drug, the "use date" is the "administration date." Similarly, the "start date of use" corresponds to the "start date of taking" for oral drugs and the "start date of administration" for injectable drugs, respectively.

[0018] The medication history management system 10 has a function to output medication history information, at least relating to the patient's medication history. In this disclosure, "medication history information" refers to information about the date of drug use for each patient, and is information that shows the drug use history for each patient. For example, the medication history information may include information that identifies the date on which the patient actually used the drug, or information that identifies the date on which the patient plans to use the drug. In other words, the medication history information includes not only information about usage dates that are in the past relative to the present, but also information about usage dates that are in the future relative to the present. Therefore, the medication history information may include information about future medication plans and past medication history. In this embodiment, as an example, the user uses the medication history management system 10 primarily for the purpose of referring to past medication history information, and therefore, the medication history information is basically information about past usage dates.

[0019] In the aforementioned medication history management system 10, the server 1 can display various information such as medication history and adverse events for each patient on the client terminal 2 in response to user operations on the client terminal 2. The client terminal 2 controls the display screen based on display data transmitted from the server 1, or controls the display screen by referring to various data stored in the server 1. The server 1 can also accept operation input from the user to the client terminal 2.

[0020] Specifically, in this embodiment, a server-client system is configured by the server 1 and the client terminal 2, and the case in which the server 1 performs various processes such as display and printing in response to user operations on the client terminal 2 will be described. Therefore, in this embodiment, the "display," "operation," "selection," and "input" described below will be described as being performed using the client terminal 2. However, similar displays and operations may be performed on the server 1.

[0021] The aforementioned higher-level system 5 is, for example, a medical-related system such as an electronic medical record system or a regimen ordering system. The higher-level system 5 is a system separate from the medication history management system 10, and it is sufficient that it can communicate and cooperate with the medication history management system 10; it is not necessary that it has a "higher" relationship with the medication history management system 10. The higher-level system 5 is capable of receiving input such as prescription data regarding the prescription or use of drugs such as anticancer drugs to patients according to their therapy, and test data regarding the results of various tests performed on patients. The higher-level system 5 inputs the prescription data and test data, etc., into the server 1 in response to user operations, or automatically inputs them into the server 1 at predetermined timings such as a pre-set closing time. Alternatively, the server 1 may be configured to actively read the prescription data and test data, etc., from the higher-level system 5. Multiple higher-level systems 5 may be provided, and furthermore, multiple higher-level systems 5 may include different types of systems. Furthermore, at least one of the prescription data and the test data may be directly entered into the medication history management system 10 by user operation on the client terminal 2 or the server 1.

[0022] Here, the prescription data includes, for example, patient data, prescription ID, cool information, therapy identification information, drug identification information, date of use, prescription date, dosage, method of use, attending physician, attending pharmacist, department, ward, etc. The prescription data may further include information such as preparation date and start date of use. The patient data includes, for example, patient identification information to identify individual patients such as patient ID or patient name, as well as various information about the patient, such as the patient's age, sex, medical history, prescription history, alcohol consumption, smoking status, family information, and physical information such as the patient's height, weight, and body surface area. The date of use indicates the date on which the drug is used (taken or administered) based on the prescription data. Hereinafter, the date of use indicated in the prescription data will be referred to as the "prescription date of use". The dosage indicates the amount of drug used based on the prescription data.

[0023] Specifically, each of the prescription data entries represents information about one day's worth of medication for one patient. Hereinafter, a set of prescription data corresponding to one cycle as defined in the therapy will be referred to as a "prescription data group." In other words, the prescription data group includes multiple prescription data entries relating to the prescription or use of medication for one cycle for a patient. Here, "one cycle" refers to a unit of use (oral administration or administration) of anticancer drugs and other medications performed on a patient according to the therapy, including the period of use and the period of rest when the medication is not used. The therapy may include one or more cycles.

[0024] However, the prescription data group is not limited to containing multiple prescription data; if the number of days of drug use corresponding to one cycle is one day, then one prescription data is included in one prescription data group. In another embodiment, for example, data corresponding to one cycle may be entered into the medication history management system 10 as a single prescription data. The timing at which multiple prescription data belonging to the prescription data group are entered into the server 1 may be the same time or at different times.

[0025] The aforementioned cycle information includes cycle identification information for identifying individual cycles, as well as various information related to the cycle, such as the start date of use, the last date of use, the number of days of use, and the usage pattern. The start date of use is information indicating the first day (earliest day) of the one or more days of drug use in the cycle to which the prescription data belongs. The last date of use is information indicating the last day of the one or more days of drug use in the cycle to which the prescription data belongs. The number of days of use is information indicating the number of days of drug use in the cycle to which the prescription data belongs. The usage pattern is information indicating the pattern of drug use in the cycle to which the prescription data belongs, and includes, for example, "every-other-day use" where the drug is used every other day, "continuous use" where the drug is used every day, and patterns such as using the drug for m days and then taking n days off (m and n are integers of 0 or more).

[0026] The aforementioned cool identification information is an example of information for identifying a cool, such as a cool ID or cool name. In the higher-level system 5, the same cool ID is assigned to prescription data belonging to the same cool of a therapy corresponding to a patient. Therefore, each of the sets of prescription data corresponding to the same cool, that is, multiple prescription data included in one set of prescription data, contains the same cool identification information representing the same cool. For example, the cool ID is unique information for each combination of patient, therapy, and cool. This makes it possible for the medication history management system 10 to identify the prescription data belonging to the same cool based on the cool ID. Alternatively, instead of the cool ID, cool identification information that can identify each cool in the therapy (such as information for the first cool, second cool, third cool, etc.) may be used.

[0027] The aforementioned therapy identification information is an example of information for identifying a therapy, such as a therapy ID or therapy name. The aforementioned drug identification information is an example of information for identifying a drug, such as a drug code or drug name. The aforementioned prescription data may include, in place of or together with, the therapy identification information, the specific details of the therapy indicated by the therapy identification information.

[0028] Incidentally, anticancer drugs are generally more difficult to handle than general medicines in terms of side effects, and are therefore used according to a plan called a regimen, which shows the type, amount, duration, and procedure of drugs in chronological order. In the regimen, the basic dosage and usage pattern are specified for the use of oral anticancer drugs (oral anticancer drugs) or injectable anticancer drugs (injectable anticancer drugs). Here, since the use (administration) of the injectable anticancer drugs to patients is carried out by a doctor or nurse, the use of the injectable anticancer drugs is managed by the higher-level system 5, which is the electronic medical record system or the regimen ordering system. Therefore, the medication history management system 10 can manage the medication history of the injectable anticancer drugs by acquiring regimen order data (regimen data) for the injectable anticancer drugs from the higher-level system 5.

[0029] On the other hand, unlike injectable drugs (the aforementioned injectable anticancer drugs) which are administered by doctors or nurses, oral anticancer drugs are often managed by the patient themselves, making it difficult to manage their medication history in the system. In other words, since doctors or nurses do not directly intervene in the administration of oral anticancer drugs, it is difficult to manage the use of oral anticancer drugs in the higher-level system 5, such as the electronic medical record system or the regimen ordering system. Furthermore, since oral anticancer drugs can be ordered without being bound by a regimen like injectable anticancer drugs, it is preferable to appropriately modify the medication history of oral anticancer drugs according to the actual usage (administration) situation and duration. For example, if the prescription date included in the prescription data is set as the start date of use in the medication history management system 10, and the actual start date of use when the patient begins using the drug differs from the prescription date, then modification work on the medication history management system 10 is necessary to accurately manage the medication history. Therefore, for users of the medication history management system 10, the correction work may increase the effort required to manage the medication history of each patient, leading to an increased burden.

[0030] In light of these circumstances, the medication history management system 10 according to this embodiment adopts a configuration that makes it easier to reduce the effort required for medication history management. Specifically, the medication history management system 10 includes a change processing unit 113 that changes the medication history information according to user operations. Furthermore, the medication history management system 10 includes a type-based restriction processing unit 114 and a daily restriction processing unit 115 that impose restrictions on the changes to the medication history information made by the change processing unit 113. Details of the functions of the change processing unit 113, the type-based restriction processing unit 114, and the daily restriction processing unit 115 will be described in "[Medication History Management Method]" and subsequent sections.

[0031] [Client Terminal 2] The client terminal 2 is a personal computer equipped with a control unit 21, a storage unit 22, a communication interface 23, a display unit 24, an operation unit 25, and a drive device 26, etc. Each of the client terminals 2 is located in a medical institution (in this embodiment, a hospital) where the medication history management system 10 is used, and is an operation terminal operated by a user. For example, the client terminal 2 is used by a pharmacist who prepares medications to be administered to patients in the medical institution. The client terminal 2 may also be a portable information processing device such as a smartphone, tablet, wearable device, or laptop computer.

[0032] The control unit 21 includes control devices such as a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), and EEPROM (registered trademark). The CPU is a processor that performs various arithmetic operations. The ROM is a non-volatile memory unit in which information such as control programs for causing the CPU to perform various operations is pre-stored. The RAM is a volatile memory unit, and the EEPROM is a non-volatile memory unit. The RAM and EEPROM are used as temporary memory (work area) for the various operations performed by the CPU. The control unit 21 then uses the CPU to perform various operations according to the various control programs pre-stored in the ROM, EEPROM, or the memory unit 22.

[0033] The storage unit 22 is a non-volatile storage unit such as a hard disk or SSD (Solid State Drive) that stores various control programs and various data executed by the control unit 21. Specifically, the storage unit 22 includes a program storage unit that stores an operating system (OS) and application programs such as browser software. The browser software is application software that displays various operation screens on the display unit 24 by accessing the server 1 via the communication network NT1, and transmits input operations on the operation screens using the operation unit 25 to the server 1. For example, when address information such as a URL (Universal Resource Locator) corresponding to the server 1 is entered at a predetermined location on the operation screen displayed by the browser software, the control unit 21 accesses the server 1 based on the address information.

[0034] The aforementioned communication I / F23 is a communication interface having a network card or the like that performs data communication wirelessly or via wired connection between the server 1 and external devices such as the printer 3 via the communication network NT1, according to a predetermined communication protocol.

[0035] The display unit 24 is a device such as a liquid crystal display or an organic EL (Electro-Luminescence) display that displays various information according to control instructions from the control unit 21. For example, the control unit 21 performs various processes according to the browser software, and based on the display data received from the server 1, it displays various information based on said display data on the display unit 24.

[0036] The operation unit 25 is a device operated by the user to input various information into the client terminal 2. Specifically, the operation unit 25 includes a keyboard and a pointing device (such as a mouse) that accept input operations on various operation screens displayed on the display unit 24. The operation unit 25 may also include a touch panel that accepts touch operations on various operation screens displayed on the display unit 24, or a voice input device that accepts input of various information by voice recognition. The control unit 21 then accepts user operations on the operation unit 25 by executing various processes according to the browser software and inputs the content of said user operations to the server 1.

[0037] The drive device 26 is a device that reads the OS or browser software from a computer-readable recording medium 261 on which the OS or browser software is stored non-temporarily. The drive device 26 may be integrated with the client terminal 2, or it may be attached externally to the client terminal 2 by being detachably connected to the client terminal 2. The recording medium 261 may be a CD, DVD, BD, or USB memory, and the drive device 26 may be a CD drive, DVD drive, BD drive, or USB port. In the client terminal 2, the control unit 21 installs the OS or browser software read from the recording medium 261 using the drive device 26 into the program storage unit 22.

[0038] Specifically, the server 1 displays various screens on the display unit 24 of the client terminal 2 by transmitting data written in a web page description language such as HTML (Hyper Text Markup Language) to the client terminal 2. In addition, the control unit 21 of the client terminal 2 transmits operation signals to the server 1 in response to operation input to the operation unit 25.

[0039] [Printer 3] The printer 3 is an image forming device, such as a color printer or monochrome printer, capable of performing a printing process to record information contained in print data input from the server 1 or the client terminal 2 via the communication network NT1 onto a sheet such as paper. For example, in medical institutions such as hospitals or pharmacies, the printer 3 may be used to print prescriptions based on the prescription data. The printer 3 is also used to print the display screen D1 (see Figure 3), which will be described later, in the medication history management system 10.

[0040] [Server 1] As shown in Figure 1, the server 1 is a computer equipped with a control unit 11, a storage unit 12, a communication interface 13, a display unit 14, an operation unit 15, and a drive device 16, etc. The server 1 may be located outside of a medical institution such as a hospital or pharmacy where the medication history management system 10 is used. Furthermore, the server 1 may be an information processing device such as a smartphone, tablet terminal, or laptop computer.

[0041] The control unit 11 has the same configuration as the control unit 21 and includes control devices such as a CPU, ROM, RAM, and EEPROM, and uses the CPU to execute various processes according to various control programs pre-stored in the ROM, EEPROM, or storage unit 12.

[0042] The storage unit 12 is a non-volatile storage unit such as a hard disk or SSD that stores various control programs and various data executed by the control unit 11. The storage unit 12 also includes a program storage unit 121, a master storage unit 122, and an information storage unit 123.

[0043] The program storage unit 121 is a memory area that stores medication history management programs and the like, which cause the control unit 11 to execute various processes related to the medication history management method described later. The program storage unit 121 also stores programs such as the operating system (OS).

[0044] The master memory unit 122 is a memory area where various types of master information are stored, such as a drug master, a patient master, and a therapy master. The drug master includes information corresponding to each drug, such as the type of drug (including oral and injectable drugs), drug ID (including YJ code, etc.), drug name, JAN code, RSS code, drug bottle code, dosage form, unit, specific gravity, compatibility, excipients, precautions, allergy information, and package insert information. The patient master includes information corresponding to each patient, such as patient ID, patient name, age, gender, medical history, prescription history, alcohol consumption, smoking status, family information, medical department, ward, room, and attending physician.

[0045] The aforementioned therapy master is an example of basic therapy information in which predetermined therapies and the content of those therapies are pre-associated. Specifically, the therapy master pre-associates at least the therapy with basic usage date identification information for identifying the usage dates for one cycle in which the drug is used according to that therapy. Hereinafter, the drug corresponding to the therapy defined in the therapy master will be referred to as the "basic usage drug," the identification information for the basic usage drug will be referred to as the "basic usage drug information," and the usage dates on which the basic usage drug is used according to the therapy defined in the therapy master will be referred to as the "basic usage dates."

[0046] Specifically, the therapy master includes information such as the therapy name, the number of cycles, the name of the drug (used), basic dosage information, basic usage day information, permissible dosage range, and usage period. The permissible dosage range may be stored in the master storage unit 122 as separate information from the therapy master, associated with the combination of the therapy name and the drug name. The number of cycles is the total number of cycles predetermined for the therapy. Note that a therapy ID may be used instead of the therapy name, and a drug ID may be used instead of the drug name.

[0047] The aforementioned basic usage information is determined by the patient's unit weight (1 kg) or unit body surface area (1 m²). 2 This information indicates the amount of drug used per unit, and is used to calculate the amount of the basic drug to be used for the patient according to the therapy. Hereinafter, the amount calculated based on the basic usage amount identification information will be referred to as the basic usage amount.

[0048] The basic usage day identification information is information used to identify the basic usage days for one cycle in which the basic drug is used according to the therapy. For example, the basic usage day identification information indicates the number of days (~th day) from an arbitrary start date to the basic usage day. In other words, the basic usage day identification information is used together with the start date to identify the final usage day, the number of days used, and the usage pattern. The basic usage day identification information may also be information that can identify each of the basic usage days, such as the number of days between each of those basic usage days. Furthermore, the basic usage days for one cycle in the therapy are not limited to multiple days, but may be just one day.

[0049] The aforementioned permissible usage range is information for determining the appropriateness of the amount of the drug used as shown in the prescription data, and is determined, for example, by the ratio of the amount used to the basic usage amount. For example, if the ratio of the amount used in the prescription data to the basic usage amount is within the permissible usage range, then the dosage in the prescription data is appropriate. The usage period is the length of one cycle and is predetermined as a period that includes the period during which the drug is used and the drug-free period during which the drug is not used.

[0050] The master information stored in the master storage unit 122 is read from a computer-readable recording medium 161 by the drive device 16 and stored in the storage unit 12. Various types of master information may be pre-stored in the storage unit 12, or the server 1 may receive them from an external device via the communication network NT1. The control unit 11 can update the various types of master information stored in the master storage unit 122 at any time based on information obtained from the higher-level system 5 or other systems, or information read from the recording medium using the drive device 16. The control unit 11 can also edit various types of master information in response to user operations using the server 1 or the client terminal 2.

[0051] The information storage unit 123 is a storage area where various types of information, such as prescription data, examination data, regimen data (data on regimen orders for the injectable anticancer drugs), and medication history data, are stored in association with each patient. The control unit 11 stores the prescription data, regimen data, and examination data, etc., input from the higher-level system 5 in the information storage unit 123 in association with the patient. The control unit 11 also stores the patient's medication history information (including the history of therapies, etc.) as medication history data in the information storage unit 123.

[0052] Specifically, the control unit 11 generates the medication history data based on the prescription data, for example, and stores it in the information storage unit 123. The medication history information stored in the information storage unit 123 as medication history data includes at least information regarding the date of drug use for each patient, and, for example, similar to the prescription data, includes information such as patient data, prescription ID, cycle information, therapy identification information, drug identification information, date of use, prescription date, and amount used. The cycle information included in the medication history data includes information such as cycle identification information, start date of use, last date of use, number of days of use, and usage pattern, similar to the prescription data.

[0053] According to the aforementioned medication history data, it is possible to understand, at least, "when" and "which medications" the patient used, in chronological order. The medication history data may also include information such as the attending physician, attending pharmacist, medical department, and ward. Furthermore, the medication history information as described in the medication history data may include not only past dates on which the patient actually used the medication, but also information regarding future dates on which the patient plans to use the medication.

[0054] The control unit 11 updates various data in the information storage unit 123 based on information obtained from the higher-level system 5 or other systems, or information read from the recording medium by the server 1 or the client terminal 2. Furthermore, the control unit 11 can update various data in the information storage unit 123 with data directly input into the medication history management system 10 by user operations on the client terminal 2 or the server 1. In other words, the control unit 11 can edit (modify) the medication history data in response to user operations using the server 1 or the client terminal 2, and by editing the medication history data in response to user operations, it is possible to record medication history information for each patient.

[0055] The timing for updating various data in the information storage unit 123 by the control unit 11 is, for example, when new data is generated in the higher-level system 5, when a preset time arrives, when a preset time interval has elapsed, or when an update operation is performed by the user.

[0056] The communication interface 13 has the same configuration as the communication interface 23 and performs data communication with the client terminal 2 and external devices such as the printer 3 via the communication network NT1. The communication interface 13 also performs data communication with the higher-level system 5.

[0057] The display unit 14 is a device such as a liquid crystal display or an organic EL display that displays various information according to control instructions from the control unit 11. The operation unit 15 has the same configuration as the operation unit 25 and is a device operated by the user to input various information to the server 1. The control unit 11 receives user operations to the operation unit 15 and executes processing according to the content of the user operations.

[0058] The drive device 16 has the same configuration as the drive device 26 and is a device that reads the medication history management program from a computer-readable recording medium 161 on which the medication history management program is recorded non-temporarily. Then, in the server 1, the control unit 11 installs the medication history management program read from the recording medium 161 using the drive device 16 into the program storage unit 121 of the storage unit 12. The medication history management program may be stored in the storage unit 12 in advance, or the server 1 may receive it from an external device via the communication network NT1.

[0059] Incidentally, as shown in Figure 1, the control unit 11 of the server 1 includes an acquisition processing unit 111, an output processing unit 112, a modification processing unit 113, a type-specific restriction processing unit 114, and a daily restriction processing unit 115. Specifically, the control unit 11 functions as various processing units such as the acquisition processing unit 111, the output processing unit 112, the modification processing unit 113, the type-specific restriction processing unit 114, and the daily restriction processing unit 115 by executing various processes related to the medication history management method described later, in accordance with the medication history management program. In other words, in this embodiment, the server 1 embodies the main functions of the medication history management system 10. To put it another way, the medication history management system 10 according to this embodiment only needs to include the server 1, and the client terminal 2 and the printer 3, etc., do not need to be included as components. The control unit 11 may include a plurality of processors, and any of the plurality of processors may function as the various processing units. Also, some or all of the various processing units may be composed of electronic circuits.

[0060] Furthermore, in another embodiment, some or all of the functions of the server 1 may be provided on the client terminal 2. For example, some or all of the medication history management program may be installed on the client terminal 2, and the control unit 21 of the client terminal 2 may appropriately acquire necessary information from the server 1 and execute various processes related to the medication history management method described later. In this case, the client terminal 2 embodies the main functions of the medication history management system 10. Moreover, in the medication history management system 10, the server 1 and the client terminal 2 may cooperate to execute various processes related to the medication history management method described later.

[0061] The acquisition processing unit 111 executes an acquisition process to acquire the prescription data. The prescription data is data relating to the drug that is subject to drug history management in the drug history management system 10. The acquisition processing unit 111 can also acquire regimen order data (regime data) for the injectable anticancer drug. In this embodiment, as an example, the drug subject to drug history management is an anticancer drug, so the acquisition processing unit 111 acquires the prescription data and regimen data for the anticancer drug. However, the regimen data exists only for the injectable anticancer drug and not for the oral anticancer drug. Specifically, the acquisition processing unit 111 acquires the prescription data and regimen data by reading them from the information storage unit 123. In other words, the acquisition processing unit 111 acquires the prescription data and regimen data from the information storage unit 123, which is input from the higher-level system 5 to the server 1 and stored in the information storage unit 123 of the storage unit 12.

[0062] Furthermore, the acquisition processing unit 111 acquires basic usage information that includes at least one of the basic usage date identification information for one cycle of the therapy indicated in the prescription data, or the basic usage dates for one cycle identified based on the basic usage date identification information, based on the therapy master. Specifically, the acquisition processing unit 111 acquires the basic usage date identification information corresponding to the therapy indicated in the prescription data by reading it from the therapy master stored in the master storage unit 122. In this embodiment, the acquisition processing unit 111 acquires only the basic usage date identification information from the basic usage dates. In other embodiments, the acquisition processing unit 111 may acquire the basic usage date identification information from an external system via the communication network NT1. In other embodiments, the acquisition processing unit 111 may acquire only the basic usage dates, or the basic usage information that includes both the basic usage date identification information and the basic usage dates.

[0063] The output processing unit 112 executes an output process (output step) to output the medication history information relating to the date of use of the drug. Here, the output processing unit 112 outputs the medication history information based on the prescription data. Specifically, the output processing unit 112 generates the medication history data (medication history information) based on the prescription data, for example, and writes the medication history information to the information storage unit 123 by outputting the medication history data to the information storage unit 123. Furthermore, the output processing unit 112 reads the medication history data stored in the information storage unit 123, for example, generates the display screen D1 (see Figure 3) including the medication history information, and outputs the medication history information by displaying the display screen D1 on, for example, the display unit 24 of the client terminal 2. In other words, in this embodiment, the "output" aspect of the output process includes writing to memory (the storage unit 12) and presenting it to the user (more specifically, "display").

[0064] More specifically, the output processing unit 112 generates the drug history information using the prescription data acquired by the acquisition processing unit 111, the regimen data acquired by the acquisition processing unit 111, and the basic usage information. For example, in the case of drug history information for an oral anticancer drug, the output processing unit 112 calculates the date of the basic usage date, with the start date of use as the starting date, based on the start date of use included in the prescription data and the basic usage date identification information for one cycle included in the basic usage information. In other words, the output processing unit 112 calculates the date of the basic usage date as the date after the number of days indicated in the basic usage date identification information, calculated from the start date of use. This identifies information such as the start date of use, the last use date, the number of days used, and the usage pattern for one cycle. The output processing unit 112 outputs the information identified in this way as the drug history information. Furthermore, if the medication history information pertains to the injectable anticancer drug, the output processing unit 112 can identify the medication history information by, for example, using information such as the start date of use, the last date of use, the number of days used, and the usage pattern included in the regimen data.

[0065] However, the "output" in relation to the output processing is not limited to writing to memory (the storage unit 12) and display, but may also include, for example, printing, audio output, data output, transmission to other systems (other devices), writing to a database, and writing to memory other than the storage unit 12. For example, the output processing unit 112 may simply write the medication history information to the information storage unit 123, and it is not essential to display the display screen D1 on, for example, the display unit 24 of the client terminal 2. Conversely, the output processing unit 112 may simply display the display screen D1 on, for example, the display unit 24 of the client terminal 2, and it is not essential to write the medication history information to the information storage unit 123. Furthermore, the output processing unit 112 may output the medication history information to a device other than the medication history management system 10 (including the higher-level system 5). Furthermore, the output processing unit 112 may output the medication history information by, for example, printing the display screen D1. In this case, the output processing unit 112 outputs (sends) print data including the medical history information to the printer 3.

[0066] Furthermore, the medication history information output by the output processing unit 112 is updated as needed. Specifically, when the data that forms the basis of the medication history information is updated, the output processing unit 112 regenerates the medication history information according to the updated data, thereby updating the medication history information. For example, if the medication history information for an oral anticancer drug for a certain patient is stored in the information storage unit 123, and the acquisition processing unit 111 acquires new prescription data for that patient, the output processing unit 112 updates the medication history information for that patient based on the new prescription data. Similarly, for example, if the medication history information for an injectable anticancer drug for a certain patient is stored in the information storage unit 123, and the acquisition processing unit 111 acquires new regimen data for that patient, the output processing unit 112 updates the medication history information for that patient based on the new regimen data.

[0067] The modification processing unit 113 executes a modification process (modification step) to modify the medication history information in accordance with a user operation to modify the medication history information. In this embodiment, as an example, the user operation to modify the medication history information is, for example, a predetermined operation by the user on the operation unit 25 of the client terminal 2 while the display screen D1 is displayed on the display unit 24 of the client terminal 2. According to the modification process, the medication history information stored in the information storage unit 123 is modified. Therefore, when the medication history information is modified by the modification process, the output processing unit 112 displays the display screen D1, which includes the modified medication history information stored in the information storage unit 123, on, for example, the display unit 24 of the client terminal 2. In other words, the modification of the medication history information by the modification process is reflected in the medication history information stored in the information storage unit 123 and the medication history information included in the display screen D1.

[0068] However, the modification of the medication history information by the modification processing in the modification processing unit 113 does not involve any modification of the prescription data and regimen data. In other words, as described above, when the data that forms the basis of the medication history information, such as the prescription data or regimen data, is updated, the output processing unit 112 regenerates the medication history information according to the updated data, and thus the medication history information is updated. The modification processing performed by the modification processing unit 113 differs from such updates to the medication history information in that it modifies the medication history information managed by the medication history management system 10 independently, while leaving the prescription data and regimen data unchanged. In short, the user operation to modify the medication history information does not involve any modification (change) of the prescription data.

[0069] Furthermore, in this embodiment, the user operation to change the medication history information includes an operation to specify at least one or more of the usage dates as "target dates". Specifically, for example, when the display screen D1 is displayed on the display unit 24 of the client terminal 2, the user specifies one of the usage dates included in the medication history information shown on the display screen D1 as a target date. For example, if the medication history information represents "continuous use" of the drug used daily for a period of two weeks from the start date of use, the user specifies the target date by specifying (selecting) any day within that two-week period from the start date of use. When the user operation to change the medication history information, which includes the operation to specify the target date, is performed, the modification processing unit 113 modifies the medication history information according to the user operation.

[0070] Furthermore, in this embodiment, the modification processing unit 113 can perform various types of modifications to the medication history information. In this embodiment, as an example, the types of modifications to the medication history information by the modification processing unit 113 include, for example, "change start date," "combine," "split," "add usage date," "change pattern," and "cancel" (see Figure 2). These various modification processes will be explained in detail in the section "[Medication History Management Method]" and subsequent sections.

[0071] The type-specific restriction processing unit 114 performs a type-specific restriction process (type-specific restriction step) that restricts the modification of the medication history information by the modification processing unit 113 according to the type of drug. Specifically, the types of drugs include oral drugs (the oral anticancer drug) and injectable drugs (the injectable anticancer drug). The type-specific restriction processing unit 114 restricts the modification of the medication history information by the modification processing unit 113 depending on whether the drug subject to management of the medication history information is an oral drug or an injectable drug. In this embodiment, the type-specific restriction processing unit 114 permits modification of the medication history information if the type of drug is an oral drug, and prohibits at least some of the processing related to modification of the medication history information if the type of drug is an injectable drug. In other words, if the type of drug is an injectable drug, the type-specific restriction processing unit 114 either prohibits all processing related to modification of the medication history information or prohibits only some of the processing related to modification of the medication history information. In this embodiment, if the former, that is, the type of drug, is the injectable drug, the type-specific restriction processing unit 114 prohibits all processing related to changing the drug history information. For example, if the type of drug is the injectable drug (the injectable anticancer drug), the type-specific restriction processing unit 114 prohibits or disables the user operation to change the drug history information, thereby preventing the change of the drug history information.

[0072] The daily restriction processing unit 115 performs a daily restriction process (daily restriction step) that restricts the modification of the medication history information by the modification processing unit 113 according to the target date. Specifically, the target date specified by the user operation that modifies the medication history information can be arbitrarily selected from a plurality of usage dates, including, for example, the start date of use, the last date of use, and an intermediate usage date (see Figure 2). The intermediate usage date is a day between the start date of use and the last date of use among the plurality of usage dates included in the medication history information, that is, a day after the start date of use (future) and before the last date of use (past). Therefore, the daily restriction processing unit 115 restricts the modification of the medication history information by the modification processing unit 113 depending on whether the target date is the start date of use, the last date of use, or an intermediate usage date. In this embodiment in particular, the restriction by the daily restriction processing unit 115 includes restrictions for each type of modification of the medication history information.

[0073] Figure 2 shows the relationship between the target date and the type of change (change type) of the medication history information, as performed by the daily restriction processing unit 115 in this embodiment. In Figure 2, combinations of the target date and the change type in which the change of the medication history information is permitted are indicated by "○", and combinations of the target date and the change type in which the change of the medication history information is restricted (prohibited in this case) are indicated by "-". That is, in this embodiment, as an example, with respect to "start date change" among the changes of the medication history information, the daily restriction processing unit 115 permits the change of the medication history information if the target date is the start date of use, and prohibits the change of the medication history information if the target date is the intermediate use date or the final use date. Specifically, if the target date is the intermediate use date or the final use date, the daily restriction processing unit 115 prohibits or disables the user operation for "start date change", thereby prohibiting the change of the medication history information related to "start date change".

[0074] However, the restrictions on changes to the medication history information performed by the type-specific restriction processing unit 114 or the day-specific restriction processing unit 115 are not limited to prohibiting changes, but may also be implemented, for example, by displaying a warning message such as "Are you sure you want to change the medication history information?" when the user performs the operation.

[0075] [Medication history management method] An example of the medication history management method executed by the control unit 11 of the server 1 will be described below. The control unit 11 executes various processes related to the medication history management method when a specific, pre-configured start operation for executing the medication history management program is performed on the client terminal 2. The control unit 11 can execute the medication history management method in substantially parallel to each of the client terminals 2 when the specific start operation is performed on multiple client terminals 2. Furthermore, the medication history management method may be terminated in response to a specific termination operation on the client terminal 2, even while the medication history management method is being executed. The present invention may also be considered as an invention of a method (medication history management method) in which a computer such as the server 1 executes some or all of the processes of the medication history management method.

[0076] Here, the start operation includes connecting the client terminal 2 to the server 1 (starting the application software), and logging in with the input of a user ID and password. On the other hand, the end operation includes logging out and disconnecting the connection between the server 1 and the client terminal 2.

[0077] Furthermore, the control unit 11 of the server 1 basically executes the medication history management method using the screen (display screen D1) displayed on the display unit 24 of the client terminal 2. In this disclosure, "screen" means an image (video) displayed on the display unit 24 (or the display unit 14), and includes illustrations, figures, photographs, text, and videos. In addition to the display screen D1 shown in Figure 3, the main screens displayed on the display unit 24 include the home screen. In this embodiment, as an example, the control unit 11 of the server 1 is configured to transition from the home screen to the display screen D1, etc., in response to user operation.

[0078] In other words, upon the start operation, the home screen is first displayed on the display unit 24 of the client terminal 2. Then, when a specific operation is performed on the home screen with a designated patient, the system transitions from the home screen to the audit screen for that patient. Furthermore, when a specific operation is performed on the audit screen, the system transitions from the inspection screen to the display screen D1. On the various operation screens displayed on the display unit 24 (including the display screen D1), the operation unit 25 accepts user operations.

[0079] In the following example, the client terminal 2 accepts input operations on various operation screens displayed on the display unit 24 using the mouse included in the operation unit 25. In other words, even when the change processing unit 113 is to execute the change processing, the user performs a predetermined operation (user operation) to change the medication history information by operating the mouse included in the operation unit 25.

[0080] Note that buttons on the screen, such as operation button K1, are objects included in the screen displayed on the display unit 24, and the operation of such a button is an operation of the operation unit 25 that selects the button. For example, a user can operate operation button K1 by operating the mouse included in the operation unit 25, moving the cursor M1 to operation button K1 on the display screen D1, and clicking it, etc. Also, in diagrams such as Figure 3 that show the screen displayed on the display unit 24, the dashed lines, leader lines, and reference numerals representing areas are included for explanatory purposes only and are not actually displayed on the display unit 24.

[0081] [Display screen D1] Here, we will first explain the display screen D1 that is displayed on the display unit 24 of the client terminal 2, with reference to Figure 3.

[0082] The display screen D1 includes a medication history display area R1, a legend display area R2, a patient display area R3, a therapy display area R4, and a patient memo area R5. The legend display area R2 displays a legend of symbols used to display the medication history information in the medication history display area R1. In the example in Figure 3, the scheduled date of use (administration) of the injectable anticancer drug is indicated by "☆", the confirmed date of use (administration) of the injectable anticancer drug is indicated by "△", the date of use (administration) of the injectable anticancer drug is indicated by "★", and the date of use (taking) of the oral anticancer drug is indicated by "●". The patient display area R3 displays various information about the patient, including patient identification information such as patient ID and patient name. The therapy display area R4 displays various information about the therapy, including therapy identification information such as therapy name. The patient memo area R5 displays various information registered after the audit as patient memos.

[0083] The medication history display area R1 displays the medication history information for the patient shown in the patient display area R3. In the example in Figure 3, the medication history information in the medication history display area R1 is displayed in a calendar format (seven-day calendar) that shows the date and day of the week in a table format. Specifically, the medication history information is displayed in a monthly calendar format, such as "June 2020", "July 2020", "August 2020", and "September 2020". Here, as an example, the medication history information is displayed in a calendar format that is divided horizontally (left and right) by the day of the week from Sunday to Saturday, and vertically (up and down) by the week from the 1st week to the 5th week (or the 6th week). The calendar for each month includes date cells C1 representing dates from "1" to "31" (or "30") and cells C2 representing the medication history information, with one or more cells C2 associated with one date cell C1. Here, as an example, three cells C2 are associated with one date cell C1, and these three cells C2 are positioned below the corresponding date cell C1. In other words, for each day, three rows of cells C2 representing the medication history information are provided vertically (up and down). Hereafter, when distinguishing between the three cells C2 corresponding to one date cell C1, these three cells will be referred to as the first row, second row, and third row, from top to bottom.

[0084] Furthermore, multiple calendars (four in this case) are displayed horizontally (left to right) in the medication history display area R1. Operation buttons K1 and K2 are displayed on both sides of the medication history display area R1 in the display screen D1. The control unit 11 sequentially switches the calendars displayed in the medication history display area R1 to past calendars in response to the operation of operation button K1. That is, when operation button K1 is operated in the state shown in Figure 3, the calendar for "May 2020" is displayed in the medication history display area R1 and the calendar for "September 2020" is hidden. The control unit 11 sequentially switches the calendars displayed in the medication history display area R1 to future calendars in response to the operation of operation button K2. That is, when operation button K1 is operated in the state shown in Figure 3, the calendar for "October 2020" is displayed in the medication history display area R1 and the calendar for "June 2020" is hidden.

[0085] In the aforementioned medication history display area R1, the symbols displayed in cell C2 indicate the medication history information. For example, in Figure 3, the three cells C2 corresponding to the date cell C1 of "July 6, 2020" display "★" representing the day the injectable anticancer drug was used (administered) and "●" representing the day the oral anticancer drug was used (taken). This displays the medication history information that "July 6, 2020" was the day the injectable anticancer drug was used and the oral anticancer drug was used. Furthermore, the display pattern of cell C2 differs for each cycle, and in this embodiment, as an example, the color (display color) of cell C2 differs for each cycle. For example, in Figure 3, the cells C2 corresponding to the date cell C1 for 14 days from "July 6, 2020" to "July 19, 2020" display "●" representing the day the oral anticancer drug was used (taken) and are colored the same. This displays the medication history information indicating that the 14 days from "July 6, 2020" to "July 19, 2020" are the days on which the oral anticancer drug was administered, belonging to the same treatment cycle. The legend for the color (display color) of cell C2, which is set for each treatment cycle, is displayed, for example, in the therapy display area R4.

[0086] Furthermore, in the display screen D1, by positioning the cursor M1 over any date cell C1 or cell C2 in the medication history display area R1, the details of the medication history information corresponding to that date cell C1 or cell C2 are displayed, for example, in tooltip A1. In other words, the user can check the details of the medication history information for any date by operating the mouse included in the operation unit 25 and positioning the cursor M1 over any date cell C1 or cell C2 in the display screen D1 using the operation unit 25. In addition, the date cell C1 or cell C2 is highlighted by the mark M2 when the cursor M1 is positioned over it. In the example in Figure 3, the cursor M1 is positioned over the date cell C1 for "August 7, 2020," which highlights the date cell C1 with the mark M2, and the details of the medication history information for "August 7, 2020" are displayed as text in tooltip A1.

[0087] Furthermore, the calendar for each month displayed in the medication history display area R1 includes a slider bar K3 (see Figure 4), and the display can be scrolled vertically (up and down) by operating the slider bar K3.

[0088] [Change Processing] The medication history management system 10 according to this embodiment includes a change processing unit 113 in the control unit 11 that performs the change processing to modify the medication history information in accordance with user operations. Therefore, the medication history management method executed by the control unit 11 includes the change processing to modify the medication history information. In other words, the medication history information included in the display screen D1 can be modified as appropriate by the change processing.

[0089] Specifically, the modification process is executed when the user performs the operation to modify the medication history information, which includes specifying at least one or more of the usage dates as "target dates" on the display screen D1. In this embodiment, as an example, the user operates the mouse included in the operation unit 25 and right-clicks while the cursor M1 is positioned over any of the cell C2 in the medication history display area R1 to specify any one of the usage dates as "target dates". For example, if the cursor M1 is positioned over the cell C2 in the second row of "July 6, 2020" and a right-click is performed, "July 6, 2020" will be specified as the target date. Here, since the target date is the usage date, the cell C2 specified (selected) by the user operation is limited to the cell C2 that displays "★" indicating the usage date of the injectable anticancer drug, or "●" indicating the usage date of the oral anticancer drug. In other words, even if the cursor M1 is positioned over the blank cell C2 and a right-click operation is performed, this operation does not constitute a user operation to change the medication history information. However, the user operation is not limited to the above example; for example, it could be an operation to specify the date cell C1, or an operation to specify the target date in a pull-down format or text input format.

[0090] As described above in this embodiment, the medication history information includes the cycle information, which includes the cycle identification information, the start date of use, the last date of use, the number of days used, and the usage pattern. Therefore, the modification process modifies the medication history information by modifying the cycle information within the medication history information. As an example, consider a case where the medication history information displays that the 14 days from "July 6, 2020" to "July 19, 2020" are the dates on which the oral anticancer drug belongs to the same cycle, and the start date of use is to be changed. In this case, the modification processing unit 113 modifies the medication history information for the 14 days from "July 6, 2020" to "July 19, 2020" by changing the start date of use and the last date of use within the cycle information. If the start date of use is changed from "July 6, 2020" to "July 1, 2020", the medication history information will be changed to indicate that the 14 days from "July 1, 2020" to "July 14, 2020" are the dates on which the oral anticancer drug was used, belonging to the same treatment cycle.

[0091] In this embodiment, the usage dates designated as target dates are associated with groups. When a usage date corresponding to any of the groups is designated as a target date, the change process modifies the medication history information for usage dates other than the target date that correspond to the group, in addition to or in place of the medication history information for the target date. In other words, the change to the medication history information by the change process extends not only to the target date specified by the user operation, but also to one or more usage dates belonging to the same group as the target date, and the medication history information for multiple usage dates belonging to the same group is changed collectively. In short, in the medication history management system 10 according to this embodiment, the change processing unit 113 includes an operation to designate one or more usage dates corresponding to a group as target dates, and modifies the medication history information for usage dates other than the target date that correspond to the same group as the target date, in accordance with the user operation to change the medication history information.

[0092] Therefore, when a user modifies the medication history information for multiple usage dates at once, they do not need to perform the operation to modify the medication history information for all of those usage dates individually; the operation for some of the usage dates is sufficient. As a result, the user's operation to modify the medication history information for multiple usage dates at once is simplified, which has the advantage of reducing the effort required for medication history management.

[0093] Furthermore, in this embodiment, the group corresponds to one cycle defined in the therapy in which the anticancer drug is used. Therefore, when any of the usage dates is designated as a target date, the medication history information for multiple usage dates belonging to the same cycle as that target date is changed all at once. This makes it possible to change the medication history information for multiple usage dates all at once within the category of a cycle defined in the therapy, which has the advantage of reducing the effort required for medication history management.

[0094] Specifically, in this embodiment, the modification processing unit 113 distinguishes between the cycles using the cycle identification information. For example, the medication history information generated based on multiple prescription data belonging to one prescription data group all pertains to the same cycle and therefore contains the same cycle identification information. So, when any of the usage dates is designated as the target date, the modification processing unit 113 modifies multiple medication history records containing the same cycle identification information as the target date all at once.

[0095] Furthermore, in this embodiment, the modification processing unit 113 modifies the medication history information from the usage date (target date) specified by the user operation. That is, if any of the usage dates are designated as the target date and multiple medication history entries for the same cycle as that target date are modified, then basically, the medication history information from that target date onward is modified. For example, if the usage start date is changed for a 14-day period from "July 6, 2020" to "July 19, 2020", then "July 6, 2020" is designated as the target date, and the medication history information is modified for the usage dates from that target date to "July 19, 2020".

[0096] Furthermore, the medication history management system 10 according to this embodiment includes a type-specific restriction processing unit 114 in the control unit 11 that performs the type-specific restriction processing to restrict changes to the medication history information by the change processing unit 113. Therefore, the medication history management method executed by the control unit 11 includes the type-specific restriction processing. In other words, changes to the medication history information by the change processing can be restricted by the type-specific restriction processing.

[0097] In other words, the output processing unit 112 outputs the medication history information regarding the date of use of the drug selected from multiple types, and the modification processing unit 113 modifies the medication history information according to user operation. Here, the type-specific restriction processing unit 114 restricts the modification of the medication history information by the modification processing unit 113 according to the type of drug. This makes it possible, for example, to modify the medication history information only for a specific type of drug, thereby preventing accidental modification of the medication history information for drugs other than the specified drug. As a result, there is an advantage in that the effort required for medication history management is easily reduced.

[0098] Furthermore, in this embodiment, the type-specific restriction processing unit 114 allows the modification of the medication history information if the type of drug is an oral drug, and prohibits the modification of the medication history information if the type of drug is an injectable drug. For example, in Figure 3, for the second row of cell C2 in "July 6, 2020" that indicates the date of use of the oral anticancer drug, modification of the medication history information is permitted, so the modification process starts when a right-click operation is performed while cell C2 is selected. On the other hand, in Figure 3, for the first row of cell C2 in "July 6, 2020" that indicates the date of use of the injectable anticancer drug, modification of the medication history information is prohibited, so the modification process does not start even if a right-click operation is performed while cell C2 is selected.

[0099] In short, the use of the injectable anticancer drug is usually managed by the higher-level system 5, which is the electronic medical record system or the regimen ordering system, and when the drug history information for the injectable anticancer drug is modified, the prescription data (or regimen data) is modified. Therefore, the drug history management system 10 does not require modification of the drug history information for the injectable anticancer drug. Accordingly, by allowing changes to the drug history information only for oral anticancer drugs that require modification (change) in the drug history management system 10, it is possible to prevent the drug history information for the injectable anticancer drug from being mistakenly modified.

[0100] Here, the output processing unit 112 outputs the medication history information for the oral medication and the medication history information for the injectable medication in a manner that allows for simultaneous display. In other words, the display screen D1 displays the medication history information for the oral anticancer drug and the medication history information for the injectable anticancer drug side by side. Specifically, in multiple (in this case, three) cells C2 corresponding to the same day, the medication history information for the oral anticancer drug and the medication history information for the injectable anticancer drug can be displayed, respectively. As an example, in Figure 3, in the first row of cells C2 corresponding to "July 6, 2020", the medication history information indicating the date of use of the injectable anticancer drug is displayed, and the medication history information indicating the date of use of the oral anticancer drug is displayed in the second row of cells C2. In this way, by displaying the medication history information for the oral medication and the injectable medication simultaneously, it becomes easy to compare the medication history information for the oral medication and the medication history information for the injectable medication. Therefore, for example, when administering the injectable anticancer drug to a patient, it becomes possible to check the patient's medical history information regarding the oral anticancer drug.

[0101] Furthermore, the medication history management system 10 according to this embodiment includes a daily restriction processing unit 115 in the control unit 11 that performs the daily restriction processing to restrict changes to the medication history information by the change processing unit 113. Therefore, the medication history management method executed by the control unit 11 includes the daily restriction processing. In other words, changes to the medication history information by the change processing can be restricted by the daily restriction processing.

[0102] In other words, the output processing unit 112 outputs the medication history information relating to the date of use of the drug, and the modification processing unit 113 modifies the medication history information according to a user operation that includes specifying one or more of the dates of use as the target dates. Here, the daily restriction processing unit 115 restricts the modification of the medication history information by the modification processing unit 113 according to the target dates. This makes it possible, for example, to modify the medication history information only when a specific date of use is specified, thereby preventing the medication history information from being modified by an operation unintended by the user. As a result, there is an advantage in that the effort required for medication history management is easily reduced.

[0103] Furthermore, in this embodiment, the restrictions imposed by the daily restriction processing unit 115 include restrictions for each type of change in the medication history information. Here, the relationship between the target date and the type of change in the medication history information (change type) as performed by the daily restriction processing unit 115 is as shown in Figure 2. As an example, consider a case where the medication history information displays that the 14 days from "July 6, 2020" to "July 19, 2020" are the usage dates of the oral anticancer drug belonging to the same cycle, and the start date of use is to be changed. In this case, if "July 6, 2020," which corresponds to the start date of use, is designated as the target date, the processing related to "splitting," "adding usage dates," and "cancellation" (however, limited to "specified dates only") among the change processing is restricted. On the other hand, if any of the dates between "July 7, 2020" and "July 18, 2020," which correspond to the intermediate usage dates, are designated as the target date, the following modification processes will be restricted: "change start date," "combine," "add usage date," and "change pattern." If "July 19, 2020," which corresponds to the final usage date, is designated as the target date, the following modification processes will be restricted: "change start date," "combine," and "change pattern." This prevents, for example, the execution of a "change start date" process when a date other than the usage start date is designated as the target date, thus preventing incorrect changes to the medication history information.

[0104] In this embodiment, the modification process performed by the modification processing unit 113 includes six types: "change start date," "combine," "split," "add usage date," "change pattern," and "cancel." Therefore, the modification processes for changing the medication history information will be explained individually below with specific examples for each type: "change start date," "combine," "split," "add usage date," "change pattern," and "cancel." Here, "split" includes two types: "split: different cycle" and "split: same cycle," and "cancel" includes two types: "cancel: after specified date" and "specified: only specified date." Figures 4 to 15, which are referenced below, are diagrams that show only the area R10 corresponding to the calendar for "July 2020" from the medication history display area R1 of the display screen D1, and the other parts of the display screen D1 are omitted as appropriate.

[0105] [Start date changed] First, the process for changing the start date among the modification processes for changing the aforementioned medication history information will be explained with reference to Figures 4 and 5.

[0106] The modification of the medication history information by the modification processing unit 113 includes a change to the start date of use. For example, there are cases where the prescription date of the drug in the prescription data is reflected in the medication history information as the start date of use based on the prescription data. In such cases, the start date of use when the drug is actually used differs from the prescription date, so the start date of use in the medication history information differs from the actual start date of use, and the process of changing the start date is necessary.

[0107] As an example, let's assume that, as shown in display screen D101 in Figure 4, the previous medication history information indicates that the 14 days from "July 1, 2020" to "July 14, 2020" were the days the oral anticancer drug was used, belonging to the same cycle. In this case, to change the start date of use from "July 1, 2020" to "July 6, 2020", the user performs the following operations.

[0108] In other words, the user places the cursor M1 over cell C2, which is "July 1, 2020," the start date of use, on the display screen D101 and right-clicks. As a result, "July 1, 2020" is designated as the target date, and the context menu A2 is displayed overlaid on the area R10, as shown in the display screen D102 of Figure 4. The context menu A2 includes items such as "Change Start Date," "Combine," "Split," "Add Usage Date," "Change Pattern," and "Cancel." However, in this embodiment, the daily restriction processing unit 115 restricts each type of change to the medication history information, and when the start date of use is designated as the target date, the processing related to "Split," "Add Usage Date," and "Cancel: Specified Date Only" among the change processing is restricted. Therefore, in the context menu A2 of the display screen D102, the items "Split," "Add Usage Date," and "Cancel: Specified Date Only" are deactivated, for example by being grayed out, and only the items "Change Start Date," "Combine," "Change Pattern," and "Cancel: After Specified Date" are displayed as selectable and active.

[0109] The user moves the cursor M1 over the "Change Start Date" item in the context menu A2 on the display screen D102. This highlights the "Change Start Date" item in the context menu A2 with the mark M3. In this state, the user selects the "Change Start Date" item by left-clicking.

[0110] Next, the user selects the date cell C1 on the display screen D103 shown in Figure 5, which is the date to which the start date of use will be moved. Here, the user moves the cursor M1 over the date cell C1, which is "July 6, 2020", and performs a left-click operation. As a result, the start date of use is changed to "July 6, 2020" for at least the medication history information for the target date (July 1, 2020). Furthermore, the start date of use is also changed to "July 6, 2020" for multiple medication history information for the same cycle (group) as the target date (July 1, 2020) (July 2, 2020 to July 14, 2020). As a result, the start dates of use in the medication history information are changed collectively, as shown on the display screen D104 in Figure 5. The revised medication history information indicates that the 14 days from "July 6, 2020" to "July 19, 2020" are the days on which the oral anticancer drug was administered, belonging to the same treatment cycle.

[0111] [Join] Next, the process described above for modifying the medication history information will be explained with reference to Figures 6 to 9.

[0112] The modification of the medication history information by the modification processing unit 113 includes the merging of two or more of the aforementioned groups. For example, there are cases where the medication for the same cycle or course is prescribed in multiple installments. In such cases, the days on which the oral anticancer drug is actually administered, which belong to the same cycle, may be separated into two or more cycles in the medication history information. Therefore, the merging process is necessary to consolidate these days into the same cycle.

[0113] As an example, let's assume that, as shown in display screen D105 in Figure 6, the previous medication history information indicated that the 7 days from "July 6, 2020" to "July 12, 2020" were the days the oral anticancer drug was administered in the first cycle, and the 7 days from "July 10, 2020" to "July 16, 2020" were the days the oral anticancer drug was administered in the second cycle. In this case, to combine the medication history information from "July 10, 2020" to "July 16, 2020" belonging to the second cycle with the medication history information for the first cycle, the user performs the following operations.

[0114] In other words, the user places the cursor M1 over cell C2, which contains "July 10, 2020," the start date of the second cycle, on display screen D105 and right-clicks. As a result, "July 10, 2020" is designated as the target date, and the context menu A2 is displayed overlaid on area R10, as shown in display screen D106 in Figure 6. When the start date of use is designated as the target date, the processing related to "Split," "Add Usage Date," and "Cancel: Specified Date Only" among the change processing is restricted. Therefore, in the context menu A2 on display screen D106, the items "Split," "Add Usage Date," and "Cancel: Specified Date Only" are deactivated, for example, by being grayed out, and only the items "Change Start Date," "Combine," "Change Pattern," and "Cancel: After Specified Date" are displayed as selectable and active.

[0115] The user moves the cursor M1 over the "Combine" item in the context menu A2 on the display screen D106. This highlights the "Combine" item in the context menu A2 with the mark M3. In this state, the user selects the "Combine" item by left-clicking.

[0116] As a result, a merge menu A3 for specifying the content of the merge is displayed, as shown in Figure 7. The merge menu A3 is displayed as a pop-up overlaid on the area R10, for example, as shown in the display screen D107 of Figure 7. The merge menu A3 includes a register button K4, a close button K5, an input field A31, and a pull-down key K31. The user changes the date displayed in the input field A31 by operating the pull-down key K31. Here, the date displayed in the input field A31 represents the start date after the merge of the medication history information to be merged (in this case, the medication history information of the second cycle). After specifying the date in the input field A31, the user selects the register button K4, and the merge process is executed.

[0117] If the date specified in input field A31 is "July 13, 2020", then the start date of use will be changed to "July 13, 2020" for at least the medication history information for the target date (July 10, 2020). Furthermore, the start date of use will also be changed to "July 13, 2020" for the medication history information for multiple usage dates (July 11, 2020 to July 16, 2020) that belong to the same cycle (group) as the target date (July 10, 2020). In addition, the medication history information for these multiple usage dates (July 10, 2020 to July 16, 2020) will be combined with the medication history information for the first cycle by changing all of the cycle information to the first cycle. As a result, as shown in the display screen D108 of Figure 8A, the modified medication history information indicates that the 14 days from "July 6, 2020" to "July 19, 2020" are the days on which the oral anticancer drug was used, belonging to the same cycle (the first cycle).

[0118] On the other hand, if the date specified in input field A31 is "July 20, 2020", then, as shown in display screen D109 of Figure 8B, the start date of use will be changed to "July 20, 2020" for at least the medication history information for the target date (July 10, 2020). Furthermore, the start date of use will also be changed to "July 20, 2020" for the medication history information for multiple usage dates (July 11, 2020 to July 16, 2020) that belong to the same cycle (group) as the target date (July 10, 2020). In addition, the medication history information for these multiple usage dates (July 10, 2020 to July 16, 2020) will be combined with the medication history information for the first cycle by changing all of the cycle information to the first cycle. As a result, the revised medication history information indicates that the seven days from "July 6, 2020" to "July 12, 2020" and the seven days from "July 20, 2020" to "July 26, 2020" are the days on which the oral anticancer drug was administered, belonging to the same cycle (the first cycle). In this case, the seven days from "July 13, 2020" to "July 19, 2020" are the drug-free period in the first cycle.

[0119] Incidentally, the aforementioned combination is permitted only for the same group of drugs. In other words, two or more groups (cools) combined by the combination process are limited to the same drugs. For example, if the drugs used in the first and second cooldowns are different, the combination of the second cooldown with the first cooldown is prohibited. This helps to prevent erroneous changes to the medication history information.

[0120] Furthermore, when performing the aforementioned merging process, the drug history information to be merged is basically the most recent past drug history information for the group (cycle) to which the target date belongs. As an example, consider a case where, as shown in the display screen D110 in Figure 9, the drug history information before the change indicates that the dates from "July 6, 2020" to "July 12, 2020" are the usage dates of the oral anticancer drug belonging to the first cycle, the dates from "July 13, 2020" to "July 19, 2020" are the usage dates of the oral anticancer drug belonging to the second cycle, and the dates from "July 20, 2020" to "July 26, 2020" are the usage dates of the oral anticancer drug belonging to the third cycle. Here, if the start date of use for the second quarter (July 13, 2020) is specified as the target date, the most recent past group (quarter) is the first quarter, so the merge menu A3 will show the first quarter (July 6, 2020 to July 12, 2020) as the merge target. Also, if the start date of use for the third quarter (July 20, 2020) is specified as the target date, the most recent past group (quarter) is the second quarter, so the merge menu A3 will show the second quarter (July 13, 2020 to July 19, 2020) as the merge target. Note that if the start date of use for the first quarter (July 6, 2020) is specified as the target date, there is no most recent past group (quarter), so the "Merge" item in the context menu A2 will be unavailable. Alternatively, if there are no groups (cools) to be combined, a warning or similar message indicating that there are no recent cools may be displayed on the display screen D1.

[0121] [Split] Next, the division process among the modification processes for changing the medication history information will be explained with reference to Figures 10, 11A, and 11B.

[0122] The modification of the medication history information by the modification processing unit 113 includes the division of the group. For example, there are cases where multiple cycles or courses of the medication are prescribed together at once. In such cases, the days on which the oral anticancer drug is used, which actually have a drug-free period in between, may appear as consecutive days in the medication history information without the drug-free period in between. Therefore, the division process is necessary to divide these days into two or more. Furthermore, the division process may involve dividing the medication history information after division into the same cycle (or the same course) or into different cycles (or different courses).

[0123] In the following example, we will assume that, as shown in display screen D111 in Figure 10, the previous medication history information indicates that the 14 days from "July 6, 2020" to "July 19, 2020" were the days the oral anticancer drug was used, belonging to the same cycle. In this case, to split the medication history information for the 14 days (July 6, 2020 to July 19, 2020) into the first half (July 6, 2020 to July 12, 2020) and the second half (July 20, 2020 to July 26, 2020), with a 7-day drug-free period in between, the user performs the following operations.

[0124] In other words, the user places the cursor M1 over cell C2, which contains "July 13, 2020," the intermediate usage date, on display screen D111 and right-clicks. As a result, "July 13, 2020" is designated as the target date, and the context menu A2 is displayed, as shown in display screen D112 in Figure 10. When the intermediate usage date is designated as the target date, the following modification processes are restricted: "Change Start Date," "Combine," "Add Usage Date," and "Change Pattern." Therefore, in the context menu A2 on display screen D112, the items "Change Start Date," "Combine," "Add Usage Date," and "Change Pattern" are deactivated, for example, by being grayed out, and only the items "Split" and "Cancel" are active and selectable.

[0125] The user moves the cursor M1 over the "Split: Same Cool" item in the context menu A2 on the display screen D112. This highlights the "Split: Same Cool" item in the context menu A2 with the mark M3. In this state, the user selects the "Split: Same Cool" item by left-clicking.

[0126] Next, the user selects the date cell C1 on the display screen D113 shown in Figure 10, which will be the start date for the second half of the divided period. Here, the user moves the cursor M1 over the date cell C1, which is "July 20, 2020," and performs a left-click operation. As a result, the start date of use is changed to "July 13, 2020" for at least the medication history information for the target date (July 13, 2020). Furthermore, the start date of use is also changed to "July 20, 2020" for the medication history information for multiple usage dates (July 14, 2020 to July 19, 2020) that belong to the same cycle (group) as the target date (July 13, 2020). As a result, as shown in the display screen D114 in Figure 11A, the latter half of the medication history information is changed together, with a 7-day drug-free period (July 13th to July 19th, 2020) in between the first half (July 6th to July 12th, 2020). The changed medication history information indicates that the 7 days from "July 6th, 2020" to "July 12th, 2020" (first half) and the 7 days from "July 20th, 2020" to "July 26th, 2020" (second half), separated by a 7-day drug-free period, are the dates on which the oral anticancer drug was administered, belonging to the same cycle.

[0127] On the other hand, if the "Split: Different Cycle" option is selected in context menu A2, the medication history information after splitting will belong to a different cycle (or different course). In this case, as shown in display screen D115 in Figure 11B, the medication history information for the second half (July 20, 2020 to July 26, 2020) will indicate that the dates of use of the oral anticancer drug belong to a different cycle (or different course) than the first half (July 6, 2020 to July 12, 2020).

[0128] [Add use date] Next, the process of adding the date of use, which is part of the modification process for changing the medication history information, will be explained with reference to Figure 12.

[0129] The modification of the medication history information by the modification processing unit 113 includes the addition of usage dates. The usage dates to be added are added from the original usage dates onward, starting from the last usage date. For example, if there are leftover medications or medications brought in by the patient at the time of prescription, the prescription may only include the amount of medication used in the same cycle minus the amount of the leftover medications or medications brought in by the patient. In such cases, the number of usage days in the medication history information may be insufficient compared to the actual number of days the oral anticancer drug was used, so the processing to add usage dates is necessary to add the insufficient number of usage days.

[0130] In the following example, we will assume that, as shown in display screen D116 in Figure 12, the previous medication history information indicates that the nine days from "July 1, 2020" to "July 9, 2020" were the days the oral anticancer drug was administered, belonging to the same cycle. In this case, assuming that there was use (taking) of five days' worth of remaining medication, the user would perform the following operations to add the medication history information related to the aforementioned days of use of that remaining medication.

[0131] In other words, the user places the cursor M1 over cell C2, which contains "July 9, 2020," the last date of use, on display screen D116 and right-clicks. As a result, "July 9, 2020" is designated as the target date, and the context menu A2 is displayed as shown on display screen D117 in Figure 12. When the last date of use is designated as the target date, the processes related to "change start date," "combine," and "change pattern" among the modification processes are restricted. Therefore, in the context menu A2 on display screen D117, the items "change start date," "combine," and "change pattern" are deactivated, for example, by being grayed out, and only the items "split," "add usage date," and "cancel" are displayed as selectable options.

[0132] The user moves the cursor M1 over the "Add Usage Date" item (labeled "Add Dosage Date" in Figure 12, etc.) in the context menu A2 on the display screen D117. This highlights the "Add Usage Date" item in the context menu A2 with the mark M3. In this state, the user selects the "Add Usage Date" item by left-clicking.

[0133] As a result, an additional menu A4 for specifying the content of the additional usage days is displayed, as shown in the display screen D118 of Figure 12. The additional menu A4 is displayed as a pop-up, for example, overlaid on the area R10. The additional menu A4 includes the register button K4, the close button K5, the input field A41, and the pull-down key K41. The user changes the number of days displayed in the input field A41 by operating the pull-down key K41. Here, the number of days displayed in the input field A41 represents the number of usage days to be added. After specifying the number of days in the input field A41, the user selects the register button K4, and the process of adding usage days is executed.

[0134] If the number of days specified in input field A41 is "5", then, as shown in display screen D119 of Figure 12, the last use date for at least the target date (July 9, 2020) in the medication history information will be changed to "July 14, 2020". Furthermore, the last use date for the medication history information for multiple use dates (July 1, 2020 to July 8, 2020) belonging to the same cycle (group) as the target date (July 9, 2020) will also be changed to "July 14, 2020". In addition, the medication history information for all use dates (July 1, 2020 to July 14, 2020), including the added use date, will all be treated as belonging to the same cycle. As a result, the modified medication history information will show that the 14 days from "July 1, 2020" to "July 14, 2020" are the use dates of the oral anticancer drug belonging to the same cycle.

[0135] Here, it is preferable that the display method of the added usage date differs from that of the original usage date. In the display screen D119, the symbol "●" displayed for the original usage date and the symbol "◆" displayed for the added usage date are different. This makes it easier to distinguish the added usage date from the original usage date.

[0136] [Pattern change] Next, the process of changing the pattern among the modification processes for changing the medication history information will be explained with reference to Figures 13, 14A, and 14B.

[0137] The modification of the medication history information by the modification processing unit 113 includes changing the pattern of the date of use. For example, there are cases where the pattern of use of the drug is changed by the patient from the pattern specified in the therapy master, taking into consideration side effects, etc. In such cases, the actual pattern of use of the oral anticancer drug may differ from the pattern of use in the medication history information, so the pattern change process is necessary.

[0138] As an example, let's assume that, as shown in the display screen D120 in Figure 13, the previous medication history information indicates that the seven days from "July 1, 2020" to "July 7, 2020" were the days the oral anticancer drug was used, belonging to the same cycle. In this case, to change the drug usage pattern from "continuous use" to "every other day use," the user performs the following operations.

[0139] In other words, the user places the cursor M1 over cell C2, which contains "July 1, 2020," the start date of use, on display screen D120 and right-clicks. As a result, "July 1, 2020" is designated as the target date, and the context menu A2 is displayed as shown on display screen D121 in Figure 13. When the start date of use is designated as the target date, the processing related to "Split," "Add Usage Date," and "Cancel: Specified Date Only" among the modification processes is restricted. Therefore, in the context menu A2 on display screen D121, the items "Split," "Add Usage Date," and "Cancel: Specified Date Only" are deactivated, for example, by being grayed out, and only the items "Change Start Date," "Combine," "Change Pattern," and "Cancel: After Specified Date" are active and selectable.

[0140] The user moves the cursor M1 over the "Change Pattern" item in the context menu A2 on the display screen D121. This highlights the "Change Pattern" item in the context menu A2 with the mark M3. In this state, the user selects the "Change Pattern" item by left-clicking.

[0141] As a result, a pattern menu A5 for specifying the content of the pattern change is displayed, as shown in the display screen D122 of Figure 13. The pattern menu A5 is displayed as a pop-up, for example, overlaid on the area R10. The pattern menu A5 includes the register button K4, the close button K5, input fields A51 and A52, and pull-down keys K51 and K52. The user changes the first number of days m displayed in input field A51 by operating the pull-down key K51. Furthermore, the user changes the second number of days n displayed in input field A52 by operating the pull-down key K52. Here, the first number of days m displayed in input field A51 and the second number of days n displayed in input field A52 specify that the modified usage pattern is a pattern in which the drug is used for m days and then rested for n days (m and n are integers greater than or equal to 0). This represents the number of additional usage days. After specifying the number of days in the input fields A51 and A52, the user selects the registration button K4, which then executes the pattern change process.

[0142] If the first number of days specified in input field A51 is "1" and the second number of days specified in input field A52 is "1", then, as shown in the display screen D123 of Figure 13, the usage pattern is changed to "every other day use," which is a "one day use, one day rest" pattern. At this time, the usage pattern is set to "every other day use" for all medication history information for the aforementioned usage days belonging to the same cycle (group) as the target day (July 1, 2020). As a result, the changed medication history information indicates that the 13 days from "July 1, 2020" to "July 13, 2020" belong to the same cycle and that the medication is used every other day ("every other day use").

[0143] By the way, depending on the settings of the first number of days m displayed in input field A51 and the second number of days n displayed in input field A52, it is possible to change the usage pattern to various usage patterns, not limited to "every other day use". For example, if the first number of days specified in input field A51 is "1" and the second number of days specified in input field A52 is "2", the usage pattern will be changed to a "1 dose, 2 rest" pattern, as shown in the display screen D124 of Figure 14A, where the drug is used for one day and then rested for two days. Also, if the first number of days specified in input field A51 is "2" and the second number of days specified in input field A52 is "2", the usage pattern will be changed to a "2 dose, 2 rest" pattern, as shown in the display screen D125 of Figure 14B, where the drug is used for two days and then rested for two days. Furthermore, if the first number of days specified in input field A51 is "1" and the second number of days specified in input field A52 is "0", the usage pattern will be changed to a "continuous use" pattern in which the drug is used every day. For example, it is also possible to change the usage pattern from "every other day use" to "continuous use".

[0144] [cancel] Next, the cancellation process among the modification processes for changing the medication history information will be explained with reference to Figure 15.

[0145] The modification of the medication history information by the modification processing unit 113 includes discontinuing the use of the medication. For example, there are cases where a patient does not use the oral anticancer drug, such as when checking the usage (dosing) status of the oral anticancer drug, or when a doctor or other person instructs the patient to discontinue the use (dosing) of the oral anticancer drug. In such cases, even if it is actually a drug-free day, the medication history information may still show it as a drug-use day. Therefore, the discontinuation process is necessary to change (delete) the drug-use day to a drug-free day. Furthermore, the discontinuation process may apply to the period from the designated date (the target date) onward, or to the designated date (the target date) only.

[0146] As an example, let's assume that, as shown in display screen D126 in Figure 15, the previous medication history information indicates that the 14 days from "July 6, 2020" to "July 19, 2020" were days when the oral anticancer drug was used, belonging to the same cycle. In this case, in order to discontinue (remove from medication) the medication history information for one day on "July 13, 2020," or for 7 days from "July 13, 2020" onward, the user performs the following operations.

[0147] In other words, the user places the cursor M1 over cell C2, which contains "July 13, 2020," the intermediate usage date, on the display screen D126 and right-clicks. As a result, "July 13, 2020" is designated as the target date, and the context menu A2 is displayed as shown on the display screen D126. When the intermediate usage date is designated as the target date, the following modification processes are restricted: "Change Start Date," "Combine," "Add Usage Date," and "Change Pattern." Therefore, in the context menu A2 on the display screen D126, the items "Change Start Date," "Combine," "Add Usage Date," and "Change Pattern" are deactivated, for example, by being grayed out, and only the items "Split" and "Cancel" are active and selectable.

[0148] The user moves the cursor M1 over the "Cancel: After the specified date" item in the context menu A2 on the display screen D126. As a result, the "Cancel: After the specified date" item in the context menu A2 is highlighted with the mark M3. In this state, the user selects the "Cancel: After the specified date" item by left-clicking.

[0149] As a result, the cancellation process is executed, and as shown in the display screen D127 of Figure 15, the usage date is deleted and changed to a drug-free day for at least the target date (July 13, 2020) in the drug history information. Furthermore, for the drug history information after the target date (July 13, 2020), among the multiple usage dates (July 6, 2020 to July 19, 2020) belonging to the same cycle (group) as the target date (July 13, 2020), the usage date is deleted and changed to a drug-free day. As a result, the modified drug history information indicates that the seven days from "July 6, 2020" to "July 12, 2020" are usage dates for the oral anticancer drug belonging to the same cycle.

[0150] On the other hand, if the "Cancel: Specified Day Only" option is selected in context menu A2, the usage date will be deleted and changed to a drug-free day only for the medication history information for the target date (July 13, 2020), as shown in display screen D128 in Figure 15. As a result, the modified medication history information will indicate that the 7 days from "July 6, 2020" to "July 12, 2020" and the 6 days from "July 13, 2020" to "July 19, 2020" are usage dates for the oral anticancer drug belonging to the same cycle. Note that the processing related to "Cancel: Specified Day Only" is restricted when the start date of use is designated as the target date. The reason for this is that when the cancellation process is performed for the start date of use, normally, instead of canceling only the start date of use, all usage dates from the start date onward belonging to the same cycle are canceled and a new cycle is created.

[0151] [flowchart] Referring to Figure 16, an example of the procedure for the processing of the control unit 11 related to the modification process that changes the medication history information, in particular, will be described.

[0152] <Step S1> In step S1, the control unit 11 determines whether or not a user operation for the change process is performed on the display screen D1. In this embodiment, if the mouse included in the operation unit 25 of the client terminal 2 is used to right-click with the cursor M1 on the cell C2 of any of the usage dates in the medication history display area R1, the control unit 11 determines that a user operation has been performed (S1: Yes) and proceeds to step S2. On the other hand, if no user operation is performed (S1: No), the control unit 11 terminates the series of processes related to the change process.

[0153] <Step S2> In step S2, the control unit 11 determines whether the drug subject to the modification process is the oral drug (the oral anticancer drug). In this embodiment, the types of drugs include the oral anticancer drug and the injectable anticancer drug. If the cell C2 selected by the user operation represents the date of use of the oral anticancer drug, the control unit 11 determines that the subject of the modification process is the oral drug (S2: Yes), and proceeds to step S3. On the other hand, if the cell C2 selected by the user operation represents the date of use of the injectable anticancer drug, the control unit 11 determines that the subject of the modification process is not the oral drug (S2: No), and proceeds to step S1.

[0154] In other words, in this embodiment, the modification of the medication history information by the modification process is prohibited for the injectable anticancer drug, which is an injectable drug. Therefore, if the control unit 11 determines that the target of the modification process is not an oral drug, that is, an injectable drug (S2: No), it terminates the series of processes related to the modification process without starting the modification process.

[0155] <Step S3> In step S3, the control unit 11 determines whether the target date is the start date of use. That is, if the cell C2 selected by the user operation corresponds to the start date of use, the control unit 11 determines that the target date is the start date of use (S3: Yes), and proceeds to step S4. On the other hand, if the cell C2 selected by the user operation corresponds to the date of the intermediate use date or the final use date, the control unit 11 determines that the target date is not the start date of use (S3: No), and proceeds to step S10.

[0156] <Step S4> In step S4, the control unit 11 determines whether "Change Start Date" has been selected. That is, if the target date is the start date (S3: Yes), then, for example, in the context menu A2, only the items "Change Start Date," "Combine," "Change Pattern," and "Cancel" are displayed as selectable and active. If the user selects the "Change Start Date" item, the control unit 11 determines that "Change Start Date" has been selected (S4: Yes) and proceeds to step S5. On the other hand, if the user selects the "Combine," "Change Pattern," or "Cancel" item, the control unit 11 determines that "Change Start Date" has not been selected (S4: No) and proceeds to step S6.

[0157] <Step S5> In step S5, the change processing unit 113 of the control unit 11 executes the process of changing the start date among the change processes for changing the medication history information. At this time, the change processing unit 113 changes the start date of use not only for the target date but also for the usage dates in the same group (same cycle) as the target date. In this case, the output processing unit 112 of the control unit 11 displays the medication history information after the change (after the start date change) on the display screen D1.

[0158] <Step S6> In step S6, the control unit 11 determines whether "Combine" has been selected. That is, if the target date is the start date (S3: Yes), then, for example, in the context menu A2, only the items "Change Start Date," "Combine," "Change Pattern," and "Cancel" are displayed as selectable and active. If the user selects the "Combine" item, the control unit 11 determines that "Combine" has been selected (S6: Yes) and proceeds to step S7. On the other hand, if the user selects the "Change Pattern" or "Cancel" item, the control unit 11 determines that "Combine" has not been selected (S6: No) and proceeds to step S8.

[0159] <Step S7> In step S7, the modification processing unit 113 of the control unit 11 executes the merging process among the modification processes for modifying the medication history information. At this time, the modification processing unit 113 executes the merging process not only for the target date but also for the usage dates in the same group (same cycle) as the target date. In this case, the output processing unit 112 of the control unit 11 displays the modified (merged) medication history information on the display screen D1.

[0160] <Step S8> In step S8, the control unit 11 determines whether "Pattern Change" has been selected. That is, if the target date is the start date (S3: Yes), then, for example, in the context menu A2, only the items "Change Start Date," "Combine," "Pattern Change," and "Cancel" are displayed as selectable and active. If the user selects the "Pattern Change" item, the control unit 11 determines that "Pattern Change" has been selected (S8: Yes) and proceeds to step S9. On the other hand, if the user selects the "Cancel" item, the control unit 11 determines that "Pattern Change" has not been selected (S8: No) and proceeds to step S15.

[0161] <Step S9> In step S9, the change processing unit 113 of the control unit 11 executes the pattern change process among the change processes for changing the medication history information. At this time, the change processing unit 113 executes the pattern change process not only for the target day but also for the usage days in the same group (same cycle) as the target day. In this case, the output processing unit 112 of the control unit 11 displays the medication history information after the change (after the pattern change) on the display screen D1.

[0162] <Step S10> In step S10, the control unit 11 determines whether the target date is the last use date. That is, if the cell C2 selected by the user operation corresponds to the date of the last use date, the control unit 11 determines that the target date is the last use date (S10: Yes), and proceeds to step S11. On the other hand, if the cell C2 selected by the user operation corresponds to the date of the intermediate use date, the control unit 11 determines that the target date is not the last use date (S10: No), and proceeds to step S13.

[0163] <Step S11> In step S11, the control unit 11 determines whether "Add Usage Date" has been selected. That is, if the target date is the last usage date (S10: Yes), then, for example, only the items "Split", "Add Usage Date", and "Cancel" are displayed as selectable options in the context menu A2. If the user selects the "Add Usage Date" item, the control unit 11 determines that "Add Usage Date" has been selected (S11: Yes) and proceeds to step S12. On the other hand, if the user selects the "Split" or "Cancel" item, the control unit 11 determines that "Add Usage Date" has not been selected (S11: No) and proceeds to step S13.

[0164] <Step S12> In step S12, the change processing unit 113 of the control unit 11 executes the process of adding usage dates, which is part of the change process for changing the medication history information. At this time, the change processing unit 113 executes the usage date addition process not only for the target date but also for usage dates in the same group (same cycle) as the target date. In this case, the output processing unit 112 of the control unit 11 displays the medication history information after the change (after adding the usage dates) on the display screen D1.

[0165] <Step S13> In step S13, the control unit 11 determines whether "Split" has been selected. That is, if the target date is not the last usage date (S10: No), that is, if the target date is an intermediate usage date, then, for example, only the "Split" and "Cancel" items are displayed as selectable options in the context menu A2. If the user selects the "Split" item, the control unit 11 determines that "Split" has been selected (S13: Yes) and proceeds to step S14. On the other hand, if the user selects the "Cancel" item, the control unit 11 determines that "Split" has not been selected (S13: No) and proceeds to step S15.

[0166] <Step S14> In step S14, the change processing unit 113 of the control unit 11 executes the splitting process among the change processing for changing the medication history information. At this time, the change processing unit 113 executes the splitting process not only for the target day but also for the usage days in the same group (same cycle) as the target day. In this case, the output processing unit 112 of the control unit 11 displays the changed (after splitting) medication history information on the display screen D1.

[0167] <Step S15> In step S15, the control unit 11 determines whether "Cancel" was selected. That is, for example, if the user selects the "Cancel" item in the context menu A2, the control unit 11 determines that "Cancel" was selected (S15: Yes) and proceeds to step S16. On the other hand, if the user does not select the "Cancel" item, for example by interrupting the operation for the change process, the control unit 11 determines that "Cancel" was not selected (S15: No) and terminates the series of processes related to the change process.

[0168] <Step S16> In step S16, the change processing unit 113 of the control unit 11 executes the cancellation process among the change processing that modifies the medication history information. At this time, the change processing unit 113 executes the cancellation process not only for the target day but also for the usage days in the same group (same cycle) as the target day. In this case, the output processing unit 112 of the control unit 11 displays the modified (after cancellation) medication history information on the display screen D1.

[0169] The flowchart above is merely an example, and processes may be added or omitted as appropriate, or the order of processes may be changed as appropriate. For example, if the target date is the start date of use (S3:Yes), the control unit 11 may execute steps S4, S6, S8 and S15 in parallel and determine in one step whether "change start date," "combine," "change pattern" or "cancel" is selected. Similarly, if the target date is the last date of use (S10:Yes), the control unit 11 may execute steps S11, S13 and S15 in parallel.

[0170] [Other examples of the processing procedure of the control unit 11] Next, with reference to Figure 17, another example of the processing procedure of the control unit 11 will be described. In this other example, the type-specific restriction processing unit 114 does not prohibit all processing related to the modification of the medication history information when the type of drug is the injectable drug, but only some of the processing related to the modification of the medication history information. Specifically, if the type of drug is the injectable drug, the type-specific restriction processing unit 114 prohibits processing related to the modification of the medication history information other than the discontinuation processing, namely the start date change, the combination, the division, the addition of the usage date, and the pattern change processing, while allowing the discontinuation processing.

[0171] The flowchart shown in Figure 17 is identical to the flowchart in Figure 16, except that steps S101 and S102 are used instead of step S2. Therefore, explanations other than those for steps S101 and S102 will be omitted here.

[0172] <Step S101> In step S101, the control unit 11 determines whether the drug subject to the modification process is the oral medication (the oral anticancer drug). If the cell C2 selected by the user operation represents the date of use of the oral anticancer drug, the control unit 11 determines that the subject of the modification process is the oral medication (S101: Yes), and proceeds to step S3. On the other hand, if the cell C2 selected by the user operation represents the date of use of a drug other than the oral anticancer drug, the control unit 11 determines that the subject of the modification process is not the oral medication (S101: No), and proceeds to step S102.

[0173] <Step S102> In step S102, the control unit 11 determines whether the drug subject to the modification process is the injectable drug (the injectable anticancer drug). If the cell C2 selected by the user operation represents the date of use of the injectable anticancer drug, the control unit 11 determines that the subject of the modification process is the injectable drug (S102: Yes), and proceeds to step S15. On the other hand, if the cell C2 selected by the user operation represents the date of use of a drug other than the injectable anticancer drug, the control unit 11 determines that the subject of the modification process is not the injectable drug (S102: No), and terminates the series of processes related to the modification process.

[0174] Based on the above, if the target of the change processing is the oral medication (S101:Yes), the type-specific restriction processing unit 114 of the control unit 11 allows all processing related to the change of the change information. On the other hand, if the target of the change processing is the injectable drug (S101:No, S102:Yes), the type-specific restriction processing unit 114 of the control unit 11 prohibits all processing related to the change of the medication history information except for the discontinuation processing, and allows the discontinuation processing. If the target of the change processing is neither the oral medication nor the injectable drug (S101:No, S102:No), all processing related to the change of the change information is prohibited.

[0175] Furthermore, the type-specific restriction processing unit 114 only needs to prohibit some of the processing related to the change of the medication history information when the type of drug is the injectable drug, and the processing permitted for the injectable drug is not limited to the discontinuation processing. For example, the type-specific restriction processing unit 114 may prohibit the discontinuation processing when the type of drug is the injectable drug, and permit at least one of the other processing, namely the change of the start date, the combination, the division, the addition of the usage date, and the pattern change.

[0176] [Other features] The modification processing performed by the modification processing unit 113 is not limited to the functions of "change start date," "combine," "split," "add usage date," "change pattern," and "cancel" described above, but may include further functions. The functions of "combine" and "change prescription quantity" will be explained individually below with specific examples. However, the functions of "combine" and "change prescription quantity" can be adopted individually; for example, the modification processing performed by the modification processing unit 113 may include only the "combine" function or only the "change prescription quantity" function. Figures 18 to 20, referenced below, are diagrams showing only the area R10 corresponding to the "July 2020" calendar from the medication history display area R1 of the display screen D1, with other areas of the display screen D1 omitted as appropriate.

[0177] [Merger] First, the merger process will be explained with reference to Figures 18 and 19.

[0178] "Combining" is an extended process of the "combining" process described above, and includes two types: "Combining: Continuous Administration" and "Combining: Intermittent Administration." In other words, "Combining: Continuous Administration" and "Combining: Intermittent Administration" are types of "combining" that combine two or more of the aforementioned groups. For example, there are cases where the aforementioned drugs for the same cycle or course are prescribed in multiple installments. In such cases, the days on which the oral anticancer drugs belonging to the same cycle are actually used may be separated into two or more cycles in the medication history information. Therefore, the aforementioned combining (combining) process is necessary to consolidate these days of use into the same cycle.

[0179] As an example, let's assume that, as shown in the display screen D129 in Figure 18, the previous medication history information indicated that "July 9, 2020" was the date of use of the oral anticancer drug belonging to the first cycle, "July 16, 2020" was the date of use of the oral anticancer drug belonging to the second cycle, and "July 23, 2020" was the date of use of the oral anticancer drug belonging to the third cycle. In this case, in order to combine the medication history information for "July 16, 2020" belonging to the second cycle with the medication history information for the first cycle, the user performs the following operations.

[0180] In other words, the user places the cursor M1 over cell C2, which contains "July 16, 2020," the start and end date of the second cycle, on display screen D129 and right-clicks. As a result, "July 16, 2020" is designated as the target date, and the context menu A2 is displayed, as shown in display screen D130 in Figure 18. Here, when the start and end date of use is designated as the target date, the processing related to "split" and "cancel: specified date only" among the change processing is restricted. Therefore, in the context menu A2 on display screen D130, the items "split" and "cancel: specified date only" are deactivated, for example by being grayed out, and only the items "change start date," "combine: continuous administration," "combine: interval administration," "add usage date," "change pattern," "cancel: after specified date," and "change prescription amount" are displayed as selectable and active. For "Combine: Continuous Dosage" and "Combine: Intermittent Dosage," the conditions for switching between inactive and active display in the context menu A2 are the same as for the normal "Combine" option.

[0181] The user moves the cursor M1 over the "Combine: Continuous Administration" item in the context menu A2 on the display screen D130. This highlights the "Combine: Continuous Administration" item in the context menu A2 with the mark M3. In this state, the user selects the "Combine: Continuous Administration" item by left-clicking. Here, "Combine: Continuous Administration" has the same function as the regular "Combine" item.

[0182] In other words, when "Combine: Continuous Administration" is selected, a combination menu A3 for specifying the content of the combination is displayed, as shown in the display screen D131 of Figure 18. Here, the combination menu A3 includes an input field A31 for specifying the start date after combining the medication history information to be combined (in this case, the medication history information of the second cycle). When "Combine: Continuous Administration" is selected, the day after the last use date of the combined data is displayed by default in the input field A31. In the example in Figure 18, the start date of use of the second cycle (July 16, 2020) is specified as the target date, so the most recent past group (cycle) is the first cycle, and the combination menu A3 shows the first cycle (July 9, 2020 - July 9, 2020) as the data to be combined. Therefore, the start date after combining the medication history information to be combined is displayed by default in the input field A31 as "July 10, 2020," which is the day after "July 9, 2020."

[0183] Therefore, without changing the date in the input field A31 from the state of the display screen D131, the user selects the registration button K4, and the merging process is executed as shown in the display screen D132 of Figure 18. In short, for the medication history information for at least the target date (July 16, 2020), the start date of use is changed to "July 10, 2020". If there are multiple use dates belonging to the same cycle (group) as the target date (July 16, 2020), the start date of use for these medication history information entries is also changed to "July 10, 2020". Furthermore, the medication history information with the changed start date of use is merged with the medication history information of the first cycle by changing all of the cycle information to the first cycle. As a result, as shown in the display screen D132 in Figure 18, the modified medication history information indicates that the two days from "July 9, 2020" to "July 10, 2020" are the days when the oral anticancer drug was used, belonging to the same cycle (the first cycle). In this case, cell C2 corresponding to the date cell C1 for the two days from "July 9, 2020" to "July 10, 2020" displays a "●" representing the days the oral anticancer drug was used (taken), and is colored the same.

[0184] As described above, when "Combine: Continuous Administration" is selected, the start date of use for the combined medication history information (in this case, the medication history information for the second cycle) is changed by default to be continuous with the medication history information to be combined (in this case, the medication history information for the first cycle). Of course, if the user changes the date specified in input field A31 of the combination menu A3, it is possible to maintain the start date of use of the combined medication history information without changing it. In other words, by changing the date specified in input field A31 of the combination menu A3 to "July 16, 2020", it is possible to maintain the start date of use of the combined medication history information as "July 16, 2020". However, if the user selects the registration button K4 in the combination menu A3 without paying particular attention to the start date of use, the start date of use of the combined medication history information will be changed automatically. Therefore, within the aforementioned combining process, a function called "Combine: Interval Dosage" is provided to maintain the start date of use of the medication history information to be combined.

[0185] In other words, as shown in Figure 19, when the "Combine: Intermittent Dosage" item is selected in the context menu A2, the merging process is executed while maintaining the start date of use of the medication history information to be merged. Specifically, as shown in the display screen D133 of Figure 19, the user places the cursor M1 over cell C2, which is "July 16, 2020," the start date of use for the second cycle, and right-clicks, thereby specifying "July 16, 2020" as the target date, and the context menu A2 is displayed as shown in the display screen D134 of Figure 19. On the display screen D134, the user moves the cursor M1 over the "Combine: Intermittent Dosage" item in the context menu A2, and with the "Combine: Intermittent Dosage" item in the context menu A2 highlighted by the mark M3, the user left-clicks to select the "Combine: Intermittent Dosage" item.

[0186] When "Combine: Interval Dosage" is selected, the combination menu A3 is displayed as shown in the display screen D135 of Figure 19. Here, the target date is displayed by default in the input field A31 of the combination menu A3. In the example in Figure 19, the start date of the second cycle (July 16, 2020) is specified as the target date, so the target date, "July 16, 2020," is displayed by default in the input field A31 as the start date after combining the medication history information.

[0187] Therefore, without changing the date in the input field A31 from the state of the display screen D135, the user selects the registration button K4, and the merging process is executed as shown in the display screen D136 of Figure 19. In short, for the medication history information for at least the target date (July 16, 2020), the start date of use remains "July 16, 2020," while all the cycle information is changed to the first cycle, thereby merging it with the medication history information of the first cycle. As a result, as shown in the display screen D136 of Figure 19, the modified medication history information indicates that the two days with an interval between them, "July 9, 2020" and "July 16, 2020," are the days on which the oral anticancer drug was used, belonging to the same cycle (the first cycle). In this case, cell C2 corresponding to the date cell C1 for the two days "July 9, 2020" and "July 16, 2020" displays a "●" representing the date the oral anticancer drug was used (taken), and is colored the same color.

[0188] [Prescription dosage change] Next, the process for changing the prescription amount will be explained with reference to Figure 20.

[0189] The modification of the medication history information by the modification processing unit 113 includes changing the prescribed amount of the medication. For example, there are cases where multiple days' worth of the medication is prescribed at once. In such cases, the modification (same cycle) process is necessary to divide the usage days in the medication history information into two or more cycles (or courses). However, the modification process alone does not change the amount of the medication used (prescribed amount) related to the medication history information, which may result in the amount of the medication used (prescribed amount) on each usage day after modification remaining the same as the amount used (prescribed amount) for multiple days. To resolve this problem, the prescription amount change process makes it possible to change the prescribed amount of the medication for each usage day in the medication information to a prescription amount per usage day (1 day).

[0190] In the following example, we assume that 10 tablets of "oral anticancer drug ABC 4mg" for 4 days, totaling 40 tablets (160mg), were prescribed all at once on "July 17, 2020". In this case, when the prescription date of the drug in the prescription data is reflected in the medication history information as the start date of use based on the prescription data, the medication history information before the change will show that "July 17, 2020" was the date of use of the oral anticancer drug, as shown in Figure 20. Originally, this medication history information pertains to prescriptions for four days: "July 17, 2020", "July 20, 2020", "July 24, 2020", and "July 27, 2020", but the information specifying each use date is only entered as a comment in the prescription data. In this case, to divide (distribute) the aforementioned medication history information into four days, "July 17, 2020", "July 20, 2020", "July 24, 2020", and "July 27, 2020", the user performs the following operations.

[0191] In other words, the user places the cursor M1 over cell C2, which contains "July 17, 2020," the start and end date of use, on the display screen D137, and right-clicks. As a result, "July 17, 2020" is designated as the target date, and the context menu A2 is displayed, as shown as display screen D138 in Figure 20. Here, when the start and end date of use is designated as the target date, the "split" and "cancel: specified date only" processes among the change processes are restricted. The "change prescription amount" item is always displayed as active regardless of the target date.

[0192] The user moves the cursor M1 over the "Change Prescription Dosage" item in the context menu A2 on the display screen D138. This highlights the "Change Prescription Dosage" item in the context menu A2 with the mark M3. In this state, the user selects the "Change Prescription Dosage" item by left-clicking.

[0193] As a result, as shown in the display screen D139 of Figure 20, a prescription amount menu A6 for specifying the content of the prescription amount change is displayed. The prescription amount menu A6 is displayed as a pop-up, for example, overlaid on the area R10. The prescription amount menu A6 includes the registration button K4, the close button K5, the display field A61, and the input field A62. The display field A61 displays the current (before change) prescription amount of the drug in the medication history information. The user changes the prescription amount displayed in the input field A62 to an arbitrary value. Here, it is assumed that the drug is prescribed in a batch of "160 mg" for four days, so "160 mg" is divided into four (four equal parts), and "40" is entered in the input field A62 so that the prescription amount per day of use is "40 mg". Note that in the example of Figure 20, the unit (mg) is not displayed in the display field A61, but is displayed in association with the input field A62 only.

[0194] In this way, after specifying the prescription amount in input field A62, the user selects the registration button K4, and the prescription amount change process is executed. If the prescription amount specified in input field A62 is "40", the prescription amount (usage) of the drug will be changed to "40 mg" for at least the target date (July 17, 2020) in the medication history information. Furthermore, the user adds "3 days" to the target date through the usage day addition process, setting 4 days of usage (July 17, 2020 to July 20, 2020) belonging to the same cycle (group). Furthermore, the user divides these 4 days of medication history information into "July 17, 2020" to "July 27, 2020" with a drug-free period in between, through the split (same cycle) process.

[0195] As a result, as shown in the display screen D140 in Figure 20, the aforementioned medication history information for "July 17, 2020," "July 20, 2020," "July 24, 2020," and "July 27, 2020," all belonging to the same cycle, is set. In the modified medication history information, the prescribed amount (usage) of the drug for "July 17, 2020," "July 20, 2020," "July 24, 2020," and "July 27, 2020" has already been changed to "40 mg" due to the prescription amount change process. Therefore, the problem of the drug usage amount (prescription amount) on each usage day after the split remaining the same as the drug usage amount (prescription amount) for multiple days is resolved.

[0196] [Differentiation] The multiple components included in the medication history management system 10 may be distributed across multiple housings. Conversely, the multiple components that are distributed across multiple housings in the above embodiment (such as the control unit 11 and the display unit 24) may be consolidated and provided in a single housing.

[0197] Furthermore, the drugs whose medication history is managed in the medication history management system 10 are not limited to anticancer drugs, but may also include, for example, dialysis fluid used in dialysis patients, or various other oral or injectable drugs.

[0198] Furthermore, when performing the splitting or cancellation process, a confirmation screen (a screen corresponding to the merging menu A3) may be displayed, similar to the merging process. In this case, the confirmation screen preferably includes guide information that represents the content of the various modification processes, similar to the merging menu A3 in the merging process. For example, if the confirmation screen displayed when "after the specified date" is selected in the cancellation process, it may include guide information indicating that the medication history after the specified date will be deleted, such as the string "Delete from 2020 / 07 / 13 (Mon) onwards."

[0199] Furthermore, the user operation to change the medication history information is not limited to an operation that specifies at least one or more of the usage dates as "target dates". For example, if the usage pattern of the medication history information is "used every other day", the change process may be initiated by an operation that specifies a drug-free day as the target date instead of a usage day.

[0200] Furthermore, the display format of the medication history information in D1 on the display screen is not limited to a calendar format, as in the above embodiment, in which the information is divided horizontally (left and right) by the days of the week from Sunday to Saturday, and vertically (up and down) by the weeks from the 1st to the 5th week (or the 6th week). For example, the medication history information may be displayed in a weekly calendar format, or in a calendar format in which the dates for one month are arranged in a single column (without being divided by week). Moreover, the medication history information may be displayed in a format other than the calendar format.

[0201] Furthermore, the operation to initiate the modification process is not limited to selecting items such as "Change Start Date" or "Merge" on the context menu A2. For example, items such as "Change Start Date" and "Merge" included in the context menu A2 may be displayed on the display screen D1 permanently (i.e., always displayed) by being shown on a menu bar or the like. In this case, the user may perform the modification process by selecting the desired item on the display screen D1 with a left-click or the like, and then selecting the date cell C1 of the target date on the calendar with a left-click or the like. Alternatively, the user may, while the date cell C1 of the target date is selected, move the cursor M1 to the date cell C1 to be merged or split, and specify the merged or split, etc.

[0202] In the above embodiment, the case in which the medication history management system 10 is the therapy management system was described as an example, but the medication history management system 10 can be applied to other systems as well. Specifically, an electronic medical record system that manages patient medical record information may be an example of the medication history management system 10. In this case, in the medication history management system 10 which is the electronic medical record system, the control unit 11 performs the process of changing the medication history information according to the operation of a user such as a doctor.

Claims

1. An output processing unit that outputs medication history information regarding the date of drug use, A modification processing unit that modifies the medical history information for usage dates other than the target dates that correspond to the same group as the target dates, in accordance with a user operation to modify the medical history information, which includes an operation to specify one or more usage dates corresponding to a group as target dates, The system includes a type-specific restriction processing unit that restricts the changes to the medication history information by the change processing unit according to the type of drug, The aforementioned group corresponds to one course as defined in the therapy used as the aforementioned drug, The aforementioned type-specific restriction processing unit allows the change of the medication history information if the type of drug is an oral medication. Medication history management system.

2. The type-specific restriction processing unit prohibits at least some of the processing related to the change of the medication history information if the type of drug is an injectable drug. A medication history management system according to claim 1.

3. The output processing unit outputs the medication history information for oral medications and the medication history information for injectable medications in a manner that allows them to be displayed simultaneously. The medication history management system according to claim 2.

4. The system further includes a daily restriction processing unit that restricts the changes to the medication history information by the change processing unit according to the target date. A medication history management system according to any one of claims 1 to 3.

5. The restrictions imposed by the daily restriction processing unit include restrictions based on the type of change in the patient's medical history information. The medication history management system according to claim 4.

6. The system further includes an acquisition processing unit for acquiring prescription data related to the aforementioned drug, The output processing unit outputs the medication history information based on the prescription data. The user operation that modifies the aforementioned medication history information does not involve modifying the aforementioned prescription data. A medication history management system according to any one of claims 1 to 5.

7. The modification processing unit modifies the medication history information after the usage date specified by the user operation. A medication history management system according to any one of claims 1 to 6.

8. The changes to the medication history information by the aforementioned change processing unit include changes to the start date of use. A medication history management system according to any one of claims 1 to 7.

9. The modification of the medical history information by the modification processing unit includes the merging of two or more of the aforementioned groups. A medication history management system according to any one of claims 1 to 8.

10. The aforementioned combination is permitted only for the same group of chemicals. A medication history management system according to claim 9.

11. The modification of the medical history information by the modification processing unit includes the division of the group. A medication history management system according to any one of claims 1 to 10.

12. The modification of the medication history information by the modification processing unit includes the addition of the date of use. A medication history management system according to any one of claims 1 to 11.

13. The modification of the medication history information by the modification processing unit includes, A medication history management system according to any one of claims 1 to 12.

14. The modification of the medication history information by the modification processing unit includes discontinuing the use of the medication. A medication history management system according to any one of claims 1 to 13.

15. An output step that outputs medication history information regarding the date of drug use, A modification step which includes an operation to specify one or more of the aforementioned usage dates corresponding to a group as target dates, and which modifies the aforementioned medical history information for usage dates other than the aforementioned target dates that correspond to the same group as the aforementioned target dates, in accordance with a user operation to modify the aforementioned medical history information. A type-specific restriction step that restricts the changes to the medication history information made by the change step according to the type of drug, A medication history management program that causes a computer to execute, The aforementioned group corresponds to one course as defined in the therapy used as the aforementioned drug, In the aforementioned type-based restriction step, at least if the type of drug is an oral medication, the change in the medication history information is permitted. A medication history management program.

Images