Operation supporting system and operation supporting program

Abstract

To provide an operation supporting system and an operation supporting program which allow work burden on a pharmacist to be reduced.SOLUTION: An operation supporting system includes an output processing unit. The output processing unit outputs first medicine information D11 and second medicine information D12 in a distinguishable manner. The first medicine information D11 is information on medicines to be taken by a patient at a first timing which is related to an event of the patient. The second medicine information D12 is information on medicines to be taken by the patient at a second timing which is related to the event and subsequent to the first timing.SELECTED DRAWING: Figure 7

Description

[Technical field]

[0001] The present invention relates to a task support system and a task support program that support the tasks of pharmacists at times related to patient events. [Background technology]

[0002] A system that can improve the efficiency of the work of pharmacists is known (for example, see Patent Document 1). This type of system displays a check result of a prescription check that determines whether one or more first confirmation items are appropriate for prescription data. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2016-45926 A Summary of the Invention [Problem to be solved by the invention]

[0004] Incidentally, as a measure against polypharmacy, prescriptions may be reviewed, including reducing the dosage, following an event such as a patient's hospitalization. However, understanding how prescriptions were actually reviewed for each patient may lead to an increased workload for pharmacists.

[0005] An object of the present invention is to provide a work support system and a work support program that can reduce the work burden on pharmacists. [Means for solving the problem]

[0006] A business support system according to one aspect of the present invention includes an output processor. The output processor outputs first drug information and second drug information in a distinguishable manner. The first drug information is information about a drug to be taken by a patient at a first timing related to an event of the patient. The second drug information is information about a drug to be taken by the patient at a second timing related to the event, the second timing being later than the first timing.

[0007] According to another aspect of the present invention, a business support system includes a first acquisition processing unit and a status display processing unit. The first acquisition processing unit acquires first drug information related to a drug to be taken by a patient at a first timing related to an event of the patient. The status display processing unit displays at least a doctor's intervention status in an effort to change the prescription content related to the first drug information for the patient.

[0008] A task support system according to another aspect of the present invention includes a continuation determination processing unit. The continuation determination processing unit determines that the drug of interest is to be continued if the drug of interest is a drug of interest that is taken by the patient in all of a plurality of unit periods included in a specific period that is set based on a first timing related to a patient's event. The continuation determination processing unit also determines that the drug of interest is to be continued if, among the plurality of unit periods, there is one or more unit periods in which the drug of interest is not a drug of interest that is taken by the patient and the taking history of the drug of interest satisfies a determination condition.

[0009] A business support program according to another aspect of the present invention is a program for causing one or more processors to execute an output step. In the output step, first drug information and second drug information are output in a distinguishable manner. The first drug information is information about a drug to be taken by the patient at a first timing related to an event of the patient. The second drug information is information about a drug to be taken by the patient at a second timing related to the event, which is later than the first timing. Effect of the Invention

[0010] According to the present invention, a work support system and a work support program are provided that can reduce the work burden on pharmacists. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a block diagram showing the configuration of a task support system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram showing an example of an approach to measures against polypharmacy in which the business support system according to the embodiment of the present invention is used. [Diagram 3] FIG. 3 is a diagram showing an example of a patient list screen displayed in the business support system according to the embodiment of the present invention. [Figure 4] FIG. 4 is a diagram showing an example of a patient search screen displayed in the business support system according to the embodiment of the present invention. [Diagram 5] FIG. 5 is a flowchart showing an example of a procedure of a patient extraction process executed in the business support system according to the embodiment of the present invention. [Figure 6] FIG. 6 is a flowchart showing an example of a procedure for managing an intervention situation executed in the task support system according to the embodiment of the present invention. [Figure 7] FIG. 7 is a diagram showing an example of a provision creation screen displayed in the business support system according to the embodiment of the present invention. [Figure 8] FIG. 8 is a diagram showing an example of a provision creation screen displayed in the business support system according to the embodiment of the present invention. [Figure 9] FIG. 9 is a diagram showing an example of a comparison screen displayed in the business support system according to the embodiment of the present invention. [Figure 10] FIG. 10 is a diagram showing an example of a drug information document created using the business support system according to the embodiment of the present invention. [Figure 11] FIG. 11 is a diagram showing an example of a drug information document created using the business support system according to the embodiment of the present invention. [Figure 12]FIG. 12 is a flowchart showing an example of a procedure for creating a medicine information document, which is executed in the business support system according to the embodiment of the present invention. [Figure 13] FIG. 13 is a flowchart showing an example of a procedure for a reason / progress management process executed in the business support system according to the embodiment of the present invention. [Figure 14] FIG. 14 is a flowchart showing an example of a procedure of a restriction process executed in the task support system according to the embodiment of the present invention. [Figure 15] FIG. 15 is a diagram showing an example of a medication history of a patient for which the business support system according to the embodiment of the present invention is used. [Figure 16] FIG. 16 is a flowchart showing an example of a procedure of a continuation determination process executed in the task support system according to the embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings to facilitate understanding of the present invention. Note that the following embodiment is an example of the present invention and is not intended to limit the technical scope of the present invention. In addition, the configurations and processing functions described in the following embodiment can be selected and combined as desired.

[0013] [Business Support System 10] As shown in FIG. 1, a task support system 10 according to an embodiment of the present invention includes a server 1, a client terminal 2, and a printer 3. The server 1, the client terminal 2, and the printer 3 are connected to each other via a communication network NT1 so as to be able to communicate wirelessly or wired. The communication network NT1 includes a LAN (Local Area Network), a WAN (Wide Area Network), the Internet, an intranet, and the like. A discrimination support system 4 and a host system 5 are connected to the server 1 via the communication network NT1. The task support system 10 may include a plurality of at least one of the server 1, the client terminal 2, and the printer 3. In FIG. 1, as an example, a plurality of (two) client terminals 2 are provided. A plurality of the discrimination support system 4 and / or the host system 5 may be provided, and the plurality of discrimination support systems 4 may include different types of systems, and the plurality of host systems 5 may include different types of systems.

[0014] The users of the business support system 10 are, for example, pharmacists, doctors, nurses, medical staff, facility managers, etc. in medical institutions such as hospitals, nursing homes for the elderly, or pharmacies. In this embodiment, as an example, the business support system 10 is used in a hospital, and the users of the business support system 10 are pharmacists (hospital pharmacists) in the hospital.

[0015] In addition, in this embodiment, unless otherwise specified, when simply referring to a "drug" the "drug" refers to an oral drug. In other words, in this embodiment, the "drug" does not include an injection drug or an external medicine, but means only an oral drug.

[0016] In the task support system 10, the server 1 can display various information such as a medical history and adverse events for each patient on the client terminal 2 in response to an operation of the client terminal 2 by a user. The client terminal 2 controls a 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 to the client terminal 2 by a user.

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

[0018] The host system 5 is, for example, an electronic medical record system, an ordering system, or a medical receipt computer processing system. The host system 5 is a system separate from the business support system 10, and it is sufficient that the host system 5 can communicate with the business support system 10, and it is not essential that the host system 5 is in a "host" relationship with the business support system 10. The host system 5 inputs prescription data related to the prescription or administration of medicines to patients, test data related to the test results of various tests performed on patients, and patient data related to patients to the server 1. The server 1 may be configured to actively read out the prescription data, the test data, and the patient data from the host system 5.

[0019] The discrimination support system 4 supports a drug discrimination task of confirming and identifying drugs. The discrimination support system 4 may be a system separate from the task support system 10, and may be linked to the task support system 10 through communication. Input of at least one of the prescription data, the test data, and the patient data to the server 1 may be performed by the discrimination support system 4 in addition to or instead of the higher-level system 5. Alternatively, at least one of the prescription data, the test data, and the patient data may be directly input to the task support system 10 by a user's operation on the client terminal 2 or the server 1.

[0020] Here, the patient data includes at least patient identification information for identifying each patient, such as a patient ID and a patient name (first name). The patient data further includes various information related to the patient, such as the patient's age, sex, medical history, prescription drug history, whether the patient consumes alcohol, whether the patient smokes, and family information. The patient data further includes information related to the patient's medical treatment at the hospital, such as whether the patient is inpatient / outpatient, the date of admission (including the planned date of admission) and the date of discharge (including the planned date of admission), the medical department, the ward, the room, and the doctor in charge. The patient data further includes physical information such as the height, weight, and body surface area of ​​each patient, and measurement date information indicating the date of measurement of each of the physical information. The patient data may be included in the prescription data or the test data.

[0021] The prescription data includes patient identification information (patient ID, patient name), prescription date, preparation date, drug information (drug code, drug name, etc.), usage, and dosage. The prescription data may include pharmacist information for identifying an individual pharmacist, such as a pharmacist ID and a pharmacist name (name). The prescription data may also include doctor information, type of drug container (ampule containing drug solution, vial containing drug solution, vial containing powdered drug, or infusion bag, etc.), preparation content information (type and number of drug containers, syringes, and needles used in the mixed injection work, etc.), preparation procedure information (work content, dissolved drug, solvent, amount of dissolved drug, amount of solvent, amount extracted), administration date, prescription category, medical department, ward, etc.

[0022] Meanwhile, the business support system 10 is used to support the business of pharmacists at a timing related to a patient event. In this embodiment, the business support system 10 is used in a hospital, and the event is some event of a patient in the hospital. In this embodiment, as an example, the event is described as the hospitalization of a patient. In other words, the business support system 10 supports the business of pharmacists at a timing related to the event, that is, the "admission" of a patient to the hospital in which the business support system 10 is installed.

[0023] In this embodiment, the business support system 10 is used for the purpose of supporting measures against polypharmacy. In the present disclosure, "polypharmacy" means taking many kinds of medicines, which causes adverse events such as side effects. In other words, for example, in the case of elderly people, the possibility of unpredictable adverse events occurring due to various factors such as multiple prescriptions from different medical departments or decreased medication adherence increases due to "polypharmacy" in which many kinds of medicines are taken. The "adverse events" referred to here mean any undesirable or unintended signs, symptoms, or illnesses that occur in patients who take medicines, including events with an unclear causal relationship with the medicine.

[0024] As a measure against polypharmacy, for example, prescription contents, including reduction of medication, may be reviewed following an event such as a patient's hospitalization. However, understanding how prescription contents were actually reviewed for each patient may lead to an increase in the workload of pharmacists. In response to this, by using the work support system 10, it becomes possible to reduce the workload of pharmacists, mainly related to measures against polypharmacy.

[0025] Specifically, measures against polypharmacy are implemented by changing the prescriptions of hospitalized patients who are prescribed multiple drugs and who are at risk of adverse drug events, medication errors, or reduced medication adherence. More specifically, measures against polypharmacy are implemented by comprehensively evaluating the prescriptions of the patient, changing the prescriptions, and providing the patient with necessary medical guidance. Changes to the prescriptions include reducing, changing, reducing the dosage, discontinuing, switching to generic drugs, and switching to alternative drugs.

[0026] The above-mentioned approach roughly includes multiple steps such as identifying patients with polypharmacy, determining whether to intervene in the approach, issuing instructions to change prescription contents, creating drug information sheets, and follow-up. Furthermore, since the results of the approach are reflected in changes to prescription contents made during the patient's hospitalization period (the period from admission to discharge), when evaluating the approach, it is necessary to organize the drugs that the patient is taking at the time of admission and at the time of discharge. Therefore, for example, at the time of discharge, information about the drugs that the patient is taking at the time of admission and at the time of discharge must be entered into the drug information sheet, which increases the burden of work such as creating the drug information sheet.

[0027] The business support system 10 according to the present embodiment comprehensively supports the business of pharmacists in the efforts. For this reason, the business support system 10 has a function of extracting patients with polypharmacy, a function of managing the intervention status in the efforts, a function of managing the cause / progress, and a function of creating a drug information document Sh1 (see FIG. 10). The functions of the business support system 10 are not limited to the four functions listed here, and include, for example, a function of outputting caution information regarding caution drugs contained in the drugs to be taken by the patient, and a function of determining whether the patient should continue taking the drug. The business support system 10 is involved in measures against polypharmacy of the patient from the time of admission to the time of discharge from the hospital, and further during the period after discharge related to the follow-up of the patient. Details of each function of the business support system 10 will be described in “Business Support Method” and subsequent sections.

[0028] [Client terminal 2] The client terminal 2 is a personal computer including a control unit 21, a storage unit 22, a communication I / F 23, a display unit 24, an operation unit 25, and a drive device 26. Each of the client terminals 2 is an operation terminal that is placed in a medical institution (a hospital in this embodiment) where the business support system 10 is used, and is operated by a user. For example, the client terminal 2 is used by a pharmacist who prepares medicines to be administered to patients at the medical institution. The client terminal 2 may be a smartphone, a tablet terminal, a wearable terminal, or a portable information processing device such as a laptop computer.

[0029] The control unit 21 has control devices such as a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), and an EEPROM (registered trademark). The CPU is a processor that executes various arithmetic operations. The ROM is a non-volatile storage unit in which information such as a control program for causing the CPU to execute various processes is stored in advance. The RAM is a volatile storage unit, and the EEPROM (registered trademark) is a non-volatile storage unit. The RAM and the EEPROM (registered trademark) are used as temporary storage memories (work areas) for various processes executed by the CPU. The control unit 21 uses the CPU to execute various processes in accordance with various control programs stored in advance in the ROM, the EEPROM (registered trademark), or the storage unit 22.

[0030] The storage unit 22 is a non-volatile storage unit such as a hard disk or SSD (Solid State Drive) in which various control programs and various data executed by the control unit 21 are stored. Specifically, the storage unit 22 includes a program storage unit in which an operating system (OS) and application programs such as browser software are stored. The browser software is application software for displaying various operation screens and the like on the display unit 24 by accessing the server 1 via the communication network NT1, and for transmitting input operations on the operation screen 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 input at a predetermined position on the operation screen displayed by the browser software, the control unit 21 accesses the server 1 based on the address information.

[0031] The communication I / F 23 is a communication interface having a network card or the like that performs wireless or wired data communication between the server 1 and external devices such as the printer 3 via the communication network NT1 in accordance with a predetermined communication protocol.

[0032] 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. The operation unit 25 is a device operated by a user to input various information to the client terminal 2. Specifically, the operation unit 25 includes a keyboard and a pointing device (mouse, etc.) that accepts 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 and inputs the contents of the user operations to the server 1.

[0033] The drive device 26 is a device that reads the OS or the browser software from a computer-readable recording medium 261 on which the OS or the browser software is non-temporarily recorded. The drive device 26 may be integrated with the client terminal 2, or may be externally attached to the client terminal 2 by being removably connected to the client terminal 2. The recording medium 261 is a CD, DVD, BD, USB memory, or the like, and the drive device 26 is a CD drive, DVD drive, BD drive, USB port, or the like. In the client terminal 2, the control unit 21 installs the OS or the browser software read from the recording medium 261 using the drive device 26 into the program storage unit of the storage unit 22. Note that various software (programs) may be stored in advance in the storage unit 22, or the client terminal 2 may receive them from an external device via the communication network NT1.

[0034] Specifically, the server 1 transmits data described in a Web page description language such as HTML (Hyper Text Markup Language) to the client terminal 2, thereby displaying various screens on the display unit 24 of the client terminal 2. In addition, the control unit 21 of the client terminal 2 transmits an operation signal to the server 1 in response to an operation input to the operation unit 25.

[0035] [Printer 3] The printer 3 is an image forming device such as a color printer or a monochrome printer capable of executing a print process for recording information contained in print data input from the server 1 or the client terminal 2 via the communication network NT1 onto a sheet of paper or the like. For example, in a medical institution such as a hospital or a pharmacy, a prescription based on the prescription data may be printed by the printer 3. The printer 3 is also used in the business support system 10 to print a drug information sheet Sh1, which will be described later.

[0036] [Identification Support System 4] The discrimination support system 4 executes a discrimination support process for checking and identifying at least the medicines brought by the patient (medicines brought by the patient). In other words, in general, when a patient is admitted to a medical institution such as a hospital, a pharmacist performs a discrimination task in advance to check and identify the medicines brought by the patient that the patient has been taking since before the admission. The discrimination support system 4 executes the discrimination support process, so that the discrimination task for such medicines brought by the patient can be automated or simplified.

[0037] In this embodiment, the "brought-in medication" will be described as including only medications prescribed at a hospital other than the hospital where the patient is admitted before hospitalization. Therefore, medications prescribed at the hospital where the patient is admitted, i.e., the hospital where the business support system 10 is used, are not included in the "brought-in medication" even if they were intended for the patient to take before hospitalization. Therefore, in this embodiment, medications taken by a patient at the time of admission include both medications brought by the patient and medications prescribed at the hospital where the patient is admitted and intended for the patient to take before hospitalization. The discrimination support system 4 performs the discrimination support process only for the brought-in medications among the medications taken by the patient at the time of admission.

[0038] 1, as an example, the discrimination support system 4 includes a photographing device 41 and a computer 42. In the discrimination support system 4, the photographing device 41 photographs medicines, and the computer 42 automatically discriminates the medicines based on image data of the photographed medicines.

[0039] The computer 42 includes a control unit, a storage unit, a communication I / F, a display unit, an operation unit (all of which are not shown), etc. The storage unit stores in advance a control program for causing the control unit to execute the discrimination support process.

[0040] When identifying medicines (medicines brought with the user in this embodiment), first, a user of the identification support system 4 sets the medicine to be identified in the photographing device 41. Next, based on the user's operation of the computer 42, the photographing device 41 photographs the medicine. Image data of the photographed image of the medicine is transmitted to the computer 42. The control unit of the computer 42 refers to a database based on the image data and searches for the medicine. The control unit may search for the medicine by referring to a database built into the computer 42, or may search for the medicine by accessing an external database via the communication I / F.

[0041] In the column "[Discrimination support system 4]", unless otherwise specified, "user" refers to a user of the discrimination support system 4, and as an example, a pharmacist (hospital pharmacist) of the hospital where the business support system 10 is introduced. In other words, the user of the discrimination support system 4 may be the same as the user of the business support system 10.

[0042] As a specific example, the user places the medicine brought by the patient in a petri dish of the photographing device 41. When the user performs an instruction operation for photographing processing in the photographing device 41 on the computer 42, the photographing device 41 photographs the medicine placed on the petri dish from above and below. When the control unit obtains image data from the photographing device 41, it causes the display unit to display a discrimination screen including the image.

[0043] When the discrimination of the brought-in medicine is completed, the control unit displays a list of candidate medicines obtained as a result of discrimination on the discrimination screen. The control unit narrows down the candidate medicines to be listed based on at least one of the following: type of medicine (whether it is a tablet or other medicine), shape of the medicine (whether it is round or non-round, and if it is non-round, the ratio of the length of the major axis to the minor axis), size of the medicine (diameter of the medicine if it is round, and the length of the major axis and the length of the minor axis if it is non-round), presence or absence of engraving, presence or absence of printing, presence or absence of a dividing line, and representative color of the medicine (representative color of the region with the engraving, representative color of the region with the printing, and representative color of the other region). For example, the control unit displays medicines that are more likely to be correct probabilistically in higher rows of the list.

[0044] The user selects, from the list, a candidate drug that is considered to be correct as a result of the identification of the brought-in drug, as the brought-in drug. As a result, information about the selected candidate drug becomes brought-in drug information about the brought-in drug. The brought-in drug information includes at least a drug code or drug name for identifying the drug. The user also manually inputs information about the brought-in drug, such as the usage, dosage (amount taken per day or per session), and start date of taking the brought-in drug, for example, by referring to a medicine notebook. The user also counts the quantity of the brought-in drug (amount brought in) and manually inputs it into the computer 42. The control unit registers (records) the brought-in drug information, including this manually input information.

[0045] When the registration of the brought-home drug information for one drug is completed, the user performs the discrimination process for the other brought-home drugs for which discrimination has not yet been completed in the same manner as described above. When the discrimination process for all brought-home drugs is completed in this manner, the control unit registers (records) discrimination result data. The discrimination result data includes the brought-home drug information registered in the discrimination support process for each brought-home drug.

[0046] After checking the discrimination result data, the user (pharmacist) affixes a confirmation seal (e.g., an electronic seal). Furthermore, a doctor verifies the discrimination result data that has already been stamped by the user, and affixes a confirmation seal (e.g., an electronic seal). When the doctor has completed the confirmation of the discrimination result data, the discrimination result data is registered (recorded) in the computer 42 in a state that can be output as appropriate.

[0047] The discrimination support system 4 can output the registered discrimination result data in various forms, such as display and printing. In particular, in this embodiment, the discrimination support system 4 can cooperate with the business support system 10, and can output at least a part of the discrimination result data to the server 1 of the business support system 10. In addition, the discrimination support system 4 also outputs at least a part of the discrimination result data to the client terminal 2 as necessary. Here, the format of the discrimination result data, etc. can be appropriately changed depending on the output form and output destination.

[0048] The discrimination support system 4 does not have to include the photographing device 41. In other words, the discrimination support system 4 does not have to automate the discrimination work, and may be a system that simplifies the discrimination work. For example, a user (pharmacist, etc.) inputs an identification code marked on a medicine into an input screen of the computer 42. In this case, the computer 42 performs "Web discrimination" in which the computer 42 accesses an external database via the communication I / F based on the manually inputted identification code to discriminate the medicine.

[0049] [Server 1] 1, the server 1 is a computer including a control unit 11, a storage unit 12, a communication I / F 13, a display unit 14, an operation unit 15, and a drive device 16. The server 1 may be provided outside a medical institution such as a hospital or a pharmacy where the business support system 10 is used. The server 1 may also be an information processing device such as a smartphone, a tablet terminal, or a laptop computer.

[0050] The control unit 11 has control devices such as a CPU, a ROM, a RAM, and an EEPROM (registered trademark). The CPU is a processor that executes various arithmetic operations. The ROM is a non-volatile storage unit in which information such as a control program for causing the CPU to execute various processes is stored in advance. The RAM is a volatile storage unit, and the EEPROM is a non-volatile storage unit. The RAM and the EEPROM are used as temporary storage memories (work areas) for the various processes executed by the CPU. The control unit 11 then uses the CPU to execute various processes in accordance with the various control programs stored in advance in the ROM, the EEPROM, or the storage unit 12.

[0051] 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.

[0052] The program storage unit 121 is a storage area in which a business support program for causing the control unit 11 to execute various processes related to a business support method described below is stored. The program storage unit 121 also stores programs such as an operating system (OS).

[0053] The master storage unit 122 is a storage area in which various types of master information, such as a medicine master, a patient master, a medical department master, a user master, and a caution medicine master, are stored.

[0054] For example, the drug master includes information about various drugs, such as drug codes (including YJ codes, etc.), drug names, JAN codes, RSS codes, medicine bottle codes, dosage forms, units, specific gravity, drug varieties, compounding variations, excipients, precautions, allergy information, and package insert information. The patient master includes information about each patient, such as patient ID, patient name, age, sex, medical history, prescription drug history, alcohol use, smoking, family information, medical department, ward, room, and doctor in charge. The medical department master includes information about various medical departments of the medical institution in which the business support system 10 is used. The user master includes information about users, such as pharmacist IDs, pharmacist names, passwords, user groups, and processing permissions.

[0055] The caution drug master includes, for each predetermined caution drug, information such as drug code, drug name, JAN code, RSS code, medicine bottle code, dosage form, unit, specific gravity, drug type, compounding variations, excipient drug, allergy information, package insert information, etc. Furthermore, the caution drug master associates caution drugs with attributes (age, etc.) of patients who need to be careful when taking the caution drug, and information such as adverse events that may occur with the caution drug.

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

[0057] The information storage unit 123 is a storage area in which various information such as the prescription data, the test data, the patient data, the discrimination result data, and the medication history data is stored. The control unit 11 acquires the prescription data, the test data, the patient data, the discrimination result data, and the like from the upper system 5 or the discrimination support system 4, and accumulates and stores them in the information storage unit 123.

[0058] The control unit 11 updates various data in the information storage unit 123 based on data acquired from the higher-level system 5 (or the discrimination support system 4) or data read from the recording media 161, 261 by the server 1 (or the client terminal 2). Alternatively, the control unit 11 may update various data in the information storage unit 123 based on data directly input to the task support system 10 by a user's operation on the client terminal 2 or the server 1.

[0059] The test data is information including test results such as test values ​​for each test item performed on each patient. For example, the test data includes information such as a patient ID (patient identification information), a patient name (patient identification information), a test date, a test ID (test identification information), a test item (test identification information), and test results.

[0060] The medical history data is information indicating the drug taking history of each patient. The medical history data includes information such as a patient ID (patient identification information), a patient name (patient identification information), a start date of taking the drug, a date of taking the drug, a prescription date, drug information (drug code, drug name, etc.), usage, and dosage. The medical history data may further include information such as the pharmacist information, the doctor in charge, the medical department, and the ward. According to the medical history data, it is possible to know at least "when" and "which drug" the patient took in chronological order.

[0061] The control unit 11 updates the medical history data in the information storage unit 123 based on at least one of the prescription data and the discrimination result data. The control unit 11 can also edit the medical history data in response to a user operation using the server 1 or the client terminal 2. That is, the control unit 11 can record the medical history of each patient by editing the medical history data in response to a user operation. Therefore, the medical history data may include information on future medication schedules and past medical history. Specifically, the control unit 11 can edit the medical history data in response to a user operation on a prescription creation screen P3 (see FIG. 7) described later.

[0062] The control unit 11 updates various data in the information storage unit 123, for example, when new data occurs 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.

[0063] The communication I / F 13 is a communication interface having a network card or the like that executes wireless or wired data communication in accordance with a predetermined communication protocol between the client terminal 2 and external devices such as the printer 3 via the communication network NT1. The communication I / F 13 also performs data communication between the discrimination support system 4 and the higher-level system 5.

[0064] 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 is a device operated by a user to input various information to the server 1. Specifically, the operation unit 15 includes a keyboard and a pointing device (such as a mouse) that accepts input operations on various operation screens displayed on the display unit 14. The operation unit 15 may also include a touch panel that accepts touch operations on various operation screens displayed on the display unit 14, or a voice input device that accepts input of various information by voice recognition. The control unit 11 then accepts user operations on the operation unit 15 and executes processing according to the content of the user operation.

[0065] The drive device 16 is a device that reads the business support program from a computer-readable recording medium 161 on which the business support program is non-temporarily recorded. The recording medium 161 is a CD, a DVD, a BD, a USB memory, or the like, and the drive device 16 is a CD drive, a DVD drive, a BD drive, a USB port, or the like. In the server 1, the control unit 11 installs the business support program read from the recording medium 161 using the drive device 16 into the program storage unit 121 of the storage unit 12. The business support 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.

[0066] Incidentally, the control unit 11 of the server 1 includes a first acquisition processing unit 111, a second acquisition processing unit 112, a third acquisition processing unit 113, an output processing unit 114, a display change processing unit 115, a progress determination processing unit 116, an extraction processing unit 117, a status display processing unit 118, a restriction processing unit 119, and a continuation determination processing unit 110, as shown in FIG. 1. Specifically, the control unit 11 executes various processes related to a business support method described later according to the business support program, thereby functioning as various processing units such as the first acquisition processing unit 111, the second acquisition processing unit 112, the third acquisition processing unit 113, and the output processing unit 114. That is, in this embodiment, the server 1 embodies the main functions of the business support system 10. In other words, the business support system 10 according to this embodiment only needs to include the server 1, and may not include the client terminal 2 and the printer 3 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. Furthermore, a part or all of the various processing sections may be configured with electronic circuits.

[0067] In another embodiment, some or all of the functions of the server 1 may be provided in the client terminal 2. For example, some or all of the business support program may be installed in the client terminal 2, and the control unit 21 of the client terminal 2 may acquire necessary information from the server 1 as appropriate and execute various processes related to the business support method described below. In this case, the client terminal 2 embodies the main functions of the business support system 10. Furthermore, in the business support system 10, the server 1 and the client terminal 2 may cooperate to execute various processes related to the business support method described below.

[0068] The first acquisition processing unit 111 executes a first acquisition process to acquire first drug information D11 (see FIG. 7). The first drug information D11 is information on a drug to be taken by the patient at a first timing. The first timing is a timing related to the event of the patient. Specifically, the first acquisition processing unit 111 can acquire the first drug information D11 from various information such as the prescription data, the test data, the patient data, the discrimination result data, and the medication history data stored in the information storage unit 123. The first drug information D11 includes information for identifying individual drugs such as at least a drug code and a drug name. Here, the first timing is a timing related to the "start" of the event, and is, for example, the start time (starting period) of the event. In particular, in this embodiment, the first timing is a timing related to the start of hospitalization as the event. That is, since the event is the "hospitalization" of the patient, the timing when the patient starts "hospitalization", for example, "at the time of hospitalization" corresponds to the first timing. In this embodiment, the first timing is defined on a daily basis, and therefore the first timing is the "admission date" (including the planned date of admission). Therefore, the first timing is determined based on the admission date included in the patient data, etc.

[0069] In addition, as described below ([Other configuration examples of the identification work]), when a user (pharmacist, etc.) identifies the brought-in medicine by visual inspection, etc., the first acquisition processing unit 111 acquires the identification result data including the brought-in medicine information, for example, from the client terminal 2.

[0070] The second acquisition processing unit 112 executes a second acquisition process to acquire second drug information D12 (see FIG. 8). The second drug information D12 is information on the drug to be taken by the patient at a second timing. The second timing is related to the event and is a timing later than the first timing. Specifically, the second acquisition processing unit 112 can acquire the second drug information D12 from various information such as the prescription data, the test data, the patient data, the discrimination result data, and the medication history data stored in the information storage unit 123. The second drug information D12 includes information for identifying individual drugs such as at least a drug code and a drug name. Here, the second timing is a timing related to the "end" of the event, and is, for example, the end point (end) of the event. In particular, in this embodiment, the second timing is a timing related to discharge from hospital. That is, since the event is the "hospitalization" of the patient, the timing at which the patient ends the "hospitalization", for example, "at the time of discharge from hospital", corresponds to the second timing. In this embodiment, the second timing is defined on a daily basis, and therefore the second timing is the "discharge date" (including the planned discharge date). Therefore, the second timing is determined based on the discharge date included in the patient data, etc.

[0071] The third acquisition processing unit 113 executes a third acquisition process for acquiring additional information D13 (see FIG. 8) other than the first drug information D11 and the second drug information D12. The additional information D13 may include various information such as information on prescription or administration of drugs to a patient, information on test results of various tests performed on the patient, and information on the patient. Specifically, the third acquisition processing unit 113 can acquire the additional information D13 from various information such as the prescription data, the test data, the patient data, the discrimination result data, and the medication history data stored in the information storage unit 123. Note that the "acquisition" of information by the first acquisition processing unit 111, the second acquisition processing unit 112, and the third acquisition processing unit 113 may include both acquisition from inside the server 1 (for example, the storage unit 12) and acquisition from outside the server 1 (for example, the client terminal 2, the discrimination support system 4, and the upper system 5).

[0072] Furthermore, the additional information D13 may include information on the patient's condition after discharge. The information on the patient's condition after discharge is input, for example, by the hospital where the patient is admitted, or a hospital other than the hospital where the patient is admitted, a pharmacy, or the patient himself / herself after the patient is discharged. As an example, after the patient is discharged, a tracing report (medication information document) describing the patient's medication status (good progress, request to change to generic medicine, request to change dosage form, difficulty in taking medication, etc.) may be submitted from the pharmacy to the prescribing doctor. The tracing report describes matters that are generally not necessary for a referral, but if the tracing report describes, for example, the patient's request or changes, the prescribing doctor can refer to it when prescribing next time. The contents of the tracing report, etc. may be included in the additional information D13 as information on the patient's condition after discharge. Among the additional information D13 acquired by the third acquisition processing unit 113, the information on the patient's condition after discharge is input, for example, to a follow-up comment field C330 (see FIG. 8) described later. By managing the information regarding the patient's condition after discharge, the hospital can publicly demonstrate that it is following up with patients after discharge, and for pharmacies, this can lead to medical fee increases such as a medication information fee or a local support system surcharge.

[0073] The output processing unit 114 outputs the first medicine information D11 and the second medicine information D12 in a distinguishable manner. That is, the output processing unit 114 executes an output process (output step) for outputting the first medicine information D11 and the second medicine information D12, and in the output process, the first medicine information D11 and the second medicine information D12 are output in a distinguishable manner. Specifically, the output processing unit 114 outputs the first medicine information D11 and the second medicine information D12 by displaying a prescription creation screen P3 (see FIG. 7) including at least the first medicine information D11 and the second medicine information D12 on, for example, the display unit 24 of the client terminal 2. That is, in this embodiment, the manner of "output" related to the output process is "presentation" to the user, and more specifically, "display".

[0074] However, the form of "output" related to the output process is not limited to display, and may include, for example, printing, voice output, data output, transmission to another system (another device), writing to a database, and writing to a memory. For example, the output processing unit 114 may output the first drug information D11 and the second drug information D12 to a device (including the discrimination support system 4 and the upper system 5) other than the business support system 10 in a form in which the first drug information D11 and the second drug information D12 can be distinguished from each other. Specifically, the output processing unit 114 may output, for example, the updated (including edited) medication history data to a device other than the business support system 10 in a format in which the first drug information D11 and the second drug information D12 can be distinguished from each other. In this embodiment, the output processing unit 114 can also output the first drug information D11 and the second drug information D12 by, for example, printing the drug information booklet Sh1 in addition to displaying. In this case, the output processing unit 114 outputs (transmits) to the printer 3 print data including the first medicine information D11 and the second medicine information D12.

[0075] Furthermore, the output processing unit 114 outputs the first medicine information D11 and the second medicine information D12 by displaying a comparison screen P4 (see FIG. 9) including at least the first medicine information D11 and the second medicine information D12, for example, on the display unit 24 of the client terminal 2. In this embodiment, the comparison screen P4 includes at least a part of a first display area R41 (see FIG. 9) and at least a part of a second display area R42 (see FIG. 9). The first display area R41 is an area where the first medicine information D11 is displayed, and the second display area R42 is an area where the second medicine information D12 is displayed. That is, the output processing unit 114 simultaneously displays at least a part of the first display area R41 that displays the first medicine information D11 and at least a part of the second display area R42 that displays the second medicine information D12 on one screen. The output processing unit 114 can also output the additional information D13 and the like by displaying the additional information D13 and the like on the offer document creation screen P3, for example.

[0076] The display change processing unit 115 executes a display change process for changing the display contents of the provision document creation screen P3 or the comparison screen P4 in response to a display change operation by a user. The display change operation is a predetermined operation by a user on the operation unit 25 of the client terminal 2 in a state in which the provision document creation screen P3 or the comparison screen P4 is displayed on the display unit 24 of the client terminal 2. The manner of changing the display contents related to the display change process includes, for example, scrolling the screen, switching pages, zooming in / out, and switching display items. Here, the display change processing unit 115 changes the display contents of the first display area R41 and the display contents of the second display area R42 on the comparison screen P4 individually in response to the display change operation.

[0077] The progress determination processing unit 116 performs a progress determination process for determining change information based on an operation related to a change in the medicine taken by the patient from the first timing to the second timing. The change information is information related to the change content of the second medicine information D12 to the first medicine information D11. Then, the progress determination processing unit 116 outputs the change information to the output processing unit 114. That is, during the event (hospitalization) period from the first timing to the second timing, changes in the medicine taken by the patient may be made, such as a reduction in dosage, a change, a reduction in dosage, (abolition of) (taking) (a change to a generic drug), and a change to an alternative drug. In this case, when a user performs an operation related to the change, the progress determination processing unit 116 automatically determines the change content of how the second medicine information D12 is changed to the first medicine information D11, and outputs the change information to the output processing unit 114. Specifically, the progress determination processing unit 116 automatically determines the change content by comparing the first medicine information D11 with the second medicine information D12. In this embodiment, the output processing unit 114 displays (outputs) the change information together with the first medicine information D11 and the like by including the change information in, for example, the provision sheet creation screen P3.

[0078] Here, in the present disclosure, each of the first drug information D11 and the second drug information D12 may include not only information on one type of drug, but also information on zero or multiple types of drugs. That is, the first drug information D11 may be information on the drug to be taken by the patient at the first timing. As an example, when the patient is taking multiple types of drugs at the first timing, the first drug information D11 includes information on the multiple types of drugs. As another example, when there is no drug to be taken by the patient at the first timing, that is, when there are zero types of drugs to be taken, the first drug information D11 includes information on "no drug to be taken". Therefore, as a specific example, if the patient is taking only drug A at the first timing and the patient is taking only drug B as a generic version of drug A at the second timing, the change information includes information on "change to generic drug" as information on the change from the first drug information D11 (information on drug A) to the second drug information D12 (information on drug B). As another specific example, if the patient is only taking drug A at the first timing and has stopped taking drug A at the second timing, the change information includes the information "reduction in medication" as information regarding the change from the first drug information D11 (information about drug A) to the second drug information D12 (no drug to be taken).

[0079] The extraction processing unit 117 executes an extraction process to extract the patient candidates according to extraction conditions. The extraction conditions include at least a condition related to the number of types of drugs to be taken. According to the extraction process, it is possible to automatically extract patients who satisfy a specific condition (the extraction condition) related to the number of types of drugs to be taken from among a large number of patients, and for example, it is possible to realize the extraction of patients with polypharmacy who are included in efforts related to measures against polypharmacy. This reduces the burden of work on pharmacists related to the extraction of patients with polypharmacy. Specifically, the extraction processing unit 117 automatically extracts the patient candidates by checking various information such as the prescription data, the test data, the patient data, the discrimination result data, and the medication history data stored in the information storage unit 123 against the extraction conditions.

[0080] The status display processing unit 118 executes a status display process to display at least a doctor's intervention status in an effort to change the contents of the prescription related to the first drug information D11 for the patient. Specifically, the status display processing unit 118 displays the intervention status by displaying a patient list screen P1 (see FIG. 3) including at least the intervention status for each of the patients on, for example, the display unit 24 of the client terminal 2. According to the status display process, the doctor's intervention status in the effort related to measures against polypharmacy can be visualized, and, for example, management of the intervention status in the effort included in the effort related to measures against polypharmacy can be realized. This reduces the workload of pharmacists involved in extracting patients with polypharmacy.

[0081] More specifically, the status display processing unit 118 displays the intervention status in a manner that allows distinction between an unconfirmed state, an intervention state, and a non-intervention state. The unconfirmed state refers to a state in which confirmation by the doctor has not yet been made. The intervention state refers to a state in which the doctor has determined that there is intervention in the effort. The non-intervention state refers to a state in which the doctor has determined that there is no intervention in the effort. That is, in the status display processing, the intervention status is represented as one of three states: the unconfirmed state, the intervention state, and the non-intervention state. In the unconfirmed state, confirmation by the doctor has not yet been made, whereas in the intervention state and the non-intervention state, confirmation by the doctor has been completed. That is, the state in which confirmation by the doctor has been made is classified into either the intervention state or the non-intervention state according to the doctor's judgment.

[0082] The restriction processing unit 119 executes a restriction process for restricting an operation for changing the second medicine information D12 on the first medicine information D11 for the patient in at least one of the unconfirmed state and the non-intervention state. That is, there are three states of the intervention state, the unconfirmed state, the intervention state, and the non-intervention state, and basically, the effort to change the contents of the prescription related to the first medicine information D11 is not performed in states other than the intervention state. Therefore, when the intervention state is other than the intervention state (the unconfirmed state and the non-intervention state), the operation is restricted by the restriction process so that the operation for changing the second medicine information D12 on the first medicine information D11 is not performed by mistake. This can reduce erroneous operations by the user. The restriction of the operation here is embodied, for example, by a process for invalidating the operation, a process for prohibiting transition to a screen for operation, or a process for displaying a notice such as "Are you sure you want to change the medicine information" during the operation.

[0083] The continuation determination processing unit 110 executes a continuation determination process for determining whether or not the drug of interest, which is the subject of administration of the patient, is a drug of interest. In the continuation determination process, the continuation determination processing unit 110 determines that the drug of interest is a drug of interest that is continued to be taken if the drug of interest is taken by the patient in all of a plurality of unit periods included in a specific period set based on the first timing. In addition, in the continuation determination process, the continuation determination processing unit 110 also determines that the drug of interest is a drug of interest that is continued to be taken if, among the plurality of unit periods, there is one or more unit periods in which the drug of interest is not taken by the patient and the history of taking the drug of interest satisfies a determination condition. In the present disclosure, "continuous administration" refers to a state in which the continuation determination processing unit 110 considers the drug to be taken continuously during the specific period. Therefore, not only when the drug is taken strictly during the specific period, but also when there is a period (one or more unit periods) during the specific period in which the drug is not taken, the continuation determination processing unit 110 may consider the drug to be "continuously taken."

[0084] Specifically, the continuation determination processing unit 110 automatically determines whether or not the medication is to be continued by checking various information such as the prescription data, the test data, the patient data, the discrimination result data, and the medication history data stored in the information storage unit 123 against the determination conditions. In this way, the continuation determination processing unit 110 automatically determines whether or not the medication is to be continued, thereby reducing the workload of pharmacists involved in extracting patients with polypharmacy.

[0085] [Business support method] An example of the business support 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 business support method when a preset specific start operation for executing the business support program is performed on the client terminal 2. When the specific start operation is performed on a plurality of the client terminals 2, the control unit 11 can execute the business support method substantially in parallel for each of the client terminals 2. The business support method may be terminated in response to a specific end operation on the client terminal 2 even during execution of the business support method. The present invention may be understood as an invention of a method (business support method) for executing part or all of the processes of the business support method by a computer such as the server 1.

[0086] Here, the start operation includes connection of the client terminal 2 to the server 1 (launch of application software) and login involving input of a user ID and password, while the end operation includes logout and disconnection between the server 1 and the client terminal 2.

[0087] The business support method is involved in the polypharmacy countermeasures of the patient continuously or intermittently from the time of admission to the time of discharge, and further from the time of discharge to the time of follow-up of the patient. As shown in FIG. 2, the business support method includes a plurality of processes executed at each stage when the efforts for the polypharmacy countermeasures to be carried out from the time of admission to the time of discharge are classified into a plurality of stages. That is, the efforts are classified into five stages: extraction of patients with polypharmacy (ST1), narrowing down of the patients (ST2), preparation of an information sheet of the medicines to be taken at the time of admission of the patient (ST3), preparation of an information sheet of the medicines to be taken at the time of discharge of the patient (ST4), and follow-up after discharge (ST5). In addition, in the extraction of patients with polypharmacy (ST1) and narrowing down of the patients (ST2), "patient extraction process", "intervention status management process", "continuous medication determination process", etc. are executed. In the creation of information sheets at the time of admission and discharge (ST3 and ST4) and follow-up (ST5), "medication information sheet creation process," "reason / progress management process," and "warning information output process" are executed. Specific examples of these various processes are explained individually below.

[0088] Furthermore, the control unit 11 of the server 1 basically executes the business support method using a screen displayed on the display unit 24 of the client terminal 2. In the present disclosure, "screen" refers to an image (picture) displayed on the display unit 24 (or the display unit 14) or the like, and includes icons, figures, photographs, text, and videos. Major screens displayed on the display unit 24 include the patient list screen P1, the patient search screen P2, the provision form creation screen P3, and the comparison screen P4. As an example in this embodiment, the control unit 11 of the server 1 is configured to set the patient list screen P1 as a home screen, and to transition to the patient search screen P2, the provision form creation screen P3, and the comparison screen P4 in response to a user operation.

[0089] That is, by the start operation, first, the patient list screen P1, which is a home screen, is displayed on the display unit 24 of the client terminal 2. Then, when a patient import button B11 in the patient list screen P1 is operated, the patient list screen P1 transitions to the patient search screen P2. Furthermore, when a patient is selected and the provision form creation button B12 in the patient list screen P1 is operated, the patient list screen P1 transitions to the provision form creation screen P3. Furthermore, when a comparison button B33 in the provision form creation screen P3 is operated, the provision form creation screen P3 transitions to the comparison screen P4.

[0090] Note that buttons on a screen, such as the patient import button B11, are objects included in a screen displayed on the display unit 24, and an operation of the button is an operation of the operation unit 25 to select the button. For example, a user can operate the patient import button B11 by performing an operation on the operation unit 25, such as placing a cursor on the patient import button B11 on the patient list screen P1 and clicking it, or touching the patient import button B11 on the patient list screen P1. Also, in the drawings showing the screens displayed on the display unit 24, such as FIG. 3, the dashed lines, leader lines, and reference symbols representing areas are added only for the purpose of explanation, and are not actually displayed on the display unit 24.

[0091] [Patient extraction process] In relation to the extraction process of patients with polypharmacy, for example, the patient list screen P1 shown in FIG. 3 and the patient search screen P2 shown in FIG. 4 are displayed.

[0092] The patient list screen P1 includes a list display area R11, a button group area R12, and a search area R13. The list display area R11 displays information on one or more patients. In the example of FIG. 3, the list display area R11 displays a list of various information on a plurality of patients, including patient identification information such as a patient ID and a patient name. The button group area R12 displays a plurality of buttons to be operated by the user. Specifically, the button group area R12 displays the patient import button B11, the provision form creation button B12, the provision form print button B13, the patient list button B14, the CSV output button B15, the row delete button B16, the patient restore button B17, and the redisplay button B18. The search area R13 displays an input field for narrowing down the patients displayed in the list display area R11 by various conditions. Specifically, the search area R13 displays an input field for directly searching for a patient by specifying a patient ID, an input field for specifying various narrowing down items such as age, gender, or ward to search for patients who fit those items, and an input field for specifying the order in which patients are sorted in the list display area R11.

[0093] More specifically, in the present embodiment, as an example, the list display area R11 displays a plurality of patients arranged vertically (up and down) so that each row corresponds to an individual patient. A slide bar Sb11 is provided at the right end of the list display area R11, and the display contents of the list display area R11 can be scrolled vertically in response to the operation of the slide bar Sb11. The list display area R11 is divided horizontally (left and right) into a plurality of columns C101 to C116, and information about each patient is displayed separately in the plurality of columns C101 to C116. A check box for selecting a patient is displayed in the column C101, a patient ID is displayed in the column C102, a patient name is displayed in the column C103, the patient's age is displayed in the column C104, the patient's gender is displayed in the column C105, the medical department is displayed in the column C106, the hospitalization / outpatient department is displayed in the column C107, the admission date is displayed in the column C108, the discharge date is displayed in the column C109, and the ward is displayed in the column C110. Furthermore, column C111 displays the doctor's intervention status, column C112 displays whether the patient has given consent, column C113 displays the evaluation adjustment status, column C114 displays the number of medications brought in, column C115 displays the number of medications requiring caution, and column C116 displays the follow-up status.

[0094] Regarding the presence or absence of the patient's consent in the column C112, if the patient agrees to the above-mentioned efforts related to the polypharmacy countermeasures, "○" is entered. The status of the evaluation adjustment in the column C113 is used as a memo of the application status for the "drug comprehensive evaluation adjustment surcharge", and as an example, it is filled in blank if not implemented (default), "○" if the evaluation adjustment has been completed, and "◎" if the adjustment surcharge is applied. The number of drugs brought in the column C114 displays the total number of types of drugs, including drugs brought in by the patient and drugs prescribed at the hospital where the patient is admitted and that the patient has been taking since before admission. The number of drugs with caution in the column C115 displays the number of types of drugs that fall under the "caution drugs" among the drugs counted in the number of drugs brought in the column C114. The status of follow-up in the column C116 is filled in "○" if there is an input in the follow-up comment column C330 (see FIG. 8) on the provision creation screen P3. In this embodiment, the input into columns C111, C112, and C113 is performed manually by the user, but the input into at least one of columns C111, C112, and C113 may be automated, for example, by linking with the higher-level system 5.

[0095] The patient import button B11 in the button group area R12 is a button for shifting to the patient search screen P2, and the provision statement creation button B12 is a button for shifting to the provision statement creation screen P3. The provision statement print button B13 is a button for printing the drug information provision statement Sh1, and the patient list button B14 is a button for printing the information of all patients in the patient list screen P1. The CSV output button B15 is a button for outputting the information of all patients in the patient list screen P1 in CSV (Comma Separated Value). The row delete button B16 is a button for deleting information from the list display area R11 on a row basis, that is, on a patient basis, and the patient restore button B17 is a button for restoring (restoring) the deleted information. The redisplay button B18 is a button for updating and redisplaying the display contents of the list display area R11.

[0096] In the search area R13, for example, when "000085407" is input as the patient ID and "Taro Yuyama" as the patient name, and the search button is operated, only the information of "Taro Yuyama" located in the first row is displayed in the list display area R11. In addition, in the search area R13, when, for example, "doctor collaboration" and "with intervention" are input as the narrowing down conditions, and the narrowing down button is operated, only the information of "Patient C" and "Patient D" with "with intervention" is displayed in the list display area R11. This makes it possible to easily extract only the patients who will take the initiative in the patient list screen P1. Similarly, in the search area R13, when, for example, "doctor collaboration" and "unconfirmed" are input as the narrowing down conditions, and the narrowing down button is operated, only the information of "Taro Yuyama", "Patient A", and "Patient B" with "unconfirmed" is displayed in the list display area R11. This makes it possible to easily extract only the patients who need to be confirmed in the in-hospital conference in the patient list screen P1. In addition, when, for example, "ward ascending order" is entered in the search area R13, the patients displayed in the list display area R11 are displayed in ascending order of wards. Furthermore, by setting follow-up as a narrowing-down condition, it is also possible to extract patients who are being followed up or who have not yet been followed up based on the entry status in the column C116.

[0097] On the other hand, the patient search screen P2 includes a search result area R21, a button group area R22, and a search area R23, as shown in Fig. 4. The patient search screen P2 is a screen for searching for a patient who meets the extraction conditions from among patients included in various information such as the prescription data, the test data, the patient data, the identification result data, and the medication history data. In the example of Fig. 4, the patient search screen P2 is displayed as a pop-up window superimposed on the patient list screen P1. However, this is not limited to this example, and the patient list screen P1 may be switched to the patient search screen P2.

[0098] The search result area R21 displays information on one or more patients searched for using the extraction conditions. In the example of FIG. 4, the search result area R21 displays a list of various information on a plurality of patients, including patient identification information such as patient ID and patient name. The button group area R22 displays a plurality of buttons to be operated by the user. Specifically, the button group area R22 displays a search button B21, a registration button B22, a Do button B23, a brought-in medication button B24, and a close button B25. The search area R23 displays an input field for setting the extraction conditions. Specifically, the search area R23 displays an input field for specifying a search destination, an input field for specifying a range of a patient's age and a lower limit of the number of oral medications, and an input field for searching for a patient by specifying a prescription date, a patient ID, and a drug with caution. The search destination can be selected from, for example, two options, "Previous prescription" and "Differentiation." When "Previous prescription" is selected, the patient is searched for from the prescription data and the medical history data, etc., and when "Differentiation" is selected, the patient is searched for from the differentiation result data and the medical history data, etc. When the caution drug is selected, patients who take the caution drug can be searched for. Furthermore, the prescription category C210 is displayed in the search area R23, and patients in the prescription category selected in the prescription category C210 can be searched for.

[0099] More specifically, in the present embodiment, as an example, the search result region R21 displays a plurality of patients arranged vertically (up and down) such that each row corresponds to an individual patient. A slide bar Sb21 is provided at the right end of the search result region R21, and the display contents of the search result region R21 can be scrolled vertically in response to an operation of the slide bar Sb21. The search result region R21 is divided horizontally (left and right) into a plurality of columns C201 to C207, and information on each patient is displayed separately in the plurality of columns C201 to C207. A check box for selecting a patient is displayed in the column C201, a patient ID is displayed in the column C202, a patient name is displayed in the column C203, the patient's age is displayed in the column C204, the patient's sex is displayed in the column C205, the number of medications brought with the patient is displayed in the column C206, and the number of medications requiring caution is displayed in the column C207.

[0100] The search button B21 in the button group area R22 is a button for searching for a patient using the extraction conditions. When the search button B21 is operated with the extraction conditions set in the search area R23, a search is performed with the extraction conditions, and the results are displayed in the search result area R21. The registration button B22 is a button for registering the searched patient as a polypharmacy patient. When the registration button B22 is operated with one or more patients selected in the search result area R21, the patient is added to the patient list screen P1. The Do button B23 is a button for checking the prescription history of a patient. When the Do button B23 is operated with a patient selected in the search result area R21, the prescription history (the prescription data) of the patient is displayed. The brought-in medicine button B24 is a button for checking the brought-in medicine of a patient. When the brought-in medicine button B24 is operated with a patient selected in the search result area R21, the identification result data of the patient is displayed. The close button B25 is a button for closing the patient search screen P2 and returning to the patient list screen P1.

[0101] In the search area R23, for example, when "65" or older is entered for the age and "6" or more is entered for the range of the number of oral medications, and the search button B21 is operated, patients who are 65 years old or older and take six or more types of medication are searched for. Here, the number of types of medications to be taken is searched for based on the number of types of medication counted in the number of medications brought with the patient in the column C114 of the patient list screen P1. At this time, the extraction processing unit 117 extracts candidate patients from among patients included in various information such as the prescription data, the test data, the patient data, the discrimination result data, and the medication history data, in accordance with the extraction conditions.

[0102] An example of a procedure of the process of the control unit 11 related to the patient extraction process will be described with reference to FIG.

[0103] <Step S11> In step S11, the control unit 11 displays the patient search screen P2. Specifically, when the patient import button B11 is operated on the patient list screen P1, the screen displayed on the display unit 24 of the client terminal 2 transitions from the patient list screen P1 to the patient search screen P2.

[0104] <Step S12> In step S12, the first acquisition processing unit 111 of the control unit 11 acquires the first medicine information D11. Furthermore, the third acquisition processing unit 113 of the control unit 11 acquires the additional information D13. Thereby, information from which patients are extracted, that is, information that becomes a population, is acquired.

[0105] <Step S13> In step S13, the extraction processing unit 117 of the control unit 11 executes the extraction process to extract the patient candidates according to the extraction conditions. Specifically, when the search button B21 is operated in a state in which the extraction conditions are set on the patient search screen P2, the extraction process is executed based on the first drug information D11 and the additional information D13. In the extraction process, data to be referenced is set at the search destination. As a result, for example, patients aged 65 or older who are taking six or more types of drugs are automatically extracted from a large number of patients.

[0106] <Step S14> In step S14, a candidate selected by the user from among the patient candidates extracted in step S13 is registered as a "patient" in the business support system 10. Specifically, when one or more patients are selected on the patient search screen P2, the registration button B22 is operated, and the patient is added to the patient list screen P1. This makes it possible to ultimately register only the patient selected by the user from among the automatically extracted patient candidates. However, this is not limiting, and the extracted patient candidates may be automatically registered without the user's selection operation.

[0107] The patient extraction process is not essential to the business support method and can be omitted as appropriate.

[0108] [Intervention status management process] In relation to the management process of the intervention status in the initiative regarding measures against polypharmacy, for example, the patient list screen P1 is displayed.

[0109] Specifically, the intervention status of the doctor is displayed in a field C111 of the list display area R11 on the patient list screen P1. That is, on the patient list screen P1, the intervention status of the doctor in the effort to change the contents of the prescription related to the first medicine information D11 is displayed for each patient displayed in the list display area R11. In this embodiment, for patients who are only registered on the patient list screen P1, the intervention status is set to the unconfirmed state by default. Therefore, the intervention status becomes the intervention status or the non-intervention status only when the user manually changes the intervention status in the field C111, which is set to the unconfirmed state by default, to the intervention status or the non-intervention status.

[0110] Generally, the doctor's intervention in the initiative is often decided at a conference including doctors and pharmacists, such as an in-hospital conference. Therefore, the pharmacist, who is the user, inputs data into the column C111 of the patient list screen P1 so as to reflect the result of the doctor's decision at the conference. That is, in the example of FIG. 3, the patients (Yuyama Taro, Patient A, Patient B) in the unconfirmed state (indicated as "unconfirmed") are presumed to be patients for whom the conference has not yet been held. On the other hand, in the example of FIG. 3, the patients (Patient C, Patient D) in the intervention state (indicated as "Doctor confirmed, with intervention") are presumed to be patients for whom the conference has been held and the doctor has determined that the doctor will intervene in the initiative. In the example of FIG. 3, the patients (Patient E, Patient F) in the non-intervention state (indicated as "Doctor confirmed, no intervention") are presumed to be patients for whom the conference has been held and the doctor has determined that the doctor will not intervene in the initiative.

[0111] Furthermore, in order to intervene in the initiative, in addition to the doctor's decision to intervene, the patient's consent is also required. In the column C112 of the list display area R11 in the patient list screen P1, the presence or absence of the patient's consent is displayed. That is, in the patient list screen P1, for each patient displayed in the list display area R11, the presence or absence of the patient's consent to the initiative is displayed together with the doctor's decision (the intervention status). Therefore, the user can check both the column C111 and the column C112 of the patient list screen P1 and determine that intervention in the initiative is possible only for patients who have given their consent and are in the intervention state. Note that, usually, the presence or absence of the patient's consent is confirmed prior to the doctor's decision.

[0112] An example of a procedure of the process of the control unit 11 related to the intervention status management process will be described with reference to FIG.

[0113] <Step S21> In step S21, the first acquisition processing unit 111 of the control unit 11 acquires the first medicine information D11 (the first acquisition process), and the second acquisition processing unit 112 of the control unit 11 acquires the second medicine information D12 (the second acquisition process). Furthermore, the third acquisition processing unit 113 of the control unit 11 acquires the additional information D13.

[0114] <Step S22> In step S22, the control unit 11 displays the patient list screen P1. Specifically, for example, during an in-hospital conference, the user performs the start operation to cause the display unit 24 of the client terminal 2 to display the patient list screen P1.

[0115] <Step S23> In step S23, the control unit 11 accepts an operation on the operation unit 25 of the client terminal 2. At this time, the user selects the intervention state or the non-intervention state from the unconfirmed state, the intervention state, and the non-intervention state displayed in a pull-down format, for example, in a column C111 of the patient list screen P1. Thereby, information on the intervention state or the non-intervention state selected by the user is accepted by the control unit 11.

[0116] <Step S24> In step S24, the status display processing unit 118 of the control unit 11 registers the intervention status. Specifically, the information on the unconfirmed state, the intervention status, or the non-intervention status input in step S22 for any patient is registered in the task support system 10 as the intervention status of the patient. At this time, the intervention status already registered for the patient is updated to the new intervention status.

[0117] <Step S25> In step S25, the status display processing unit 118 of the control unit 11 executes a status display process for displaying the intervention status registered in step S24 on the patient list screen P1. Specifically, the unconfirmed state, the intervention status, or the non-intervention status is displayed in a field C111 of the patient list screen P1. At this time, it is preferable that the unconfirmed state, the intervention status, or the non-intervention status is displayed in an easily distinguishable manner by highlighting, for example, by coloring, the field C111.

[0118] In this embodiment, the intervention status in the field C111 is manually input by a user, but the invention is not limited to this and may be automated, for example, by linking with the host system 5 such as an electronic medical record system. As an example, when a doctor records a judgment result that an intervention is required for a certain patient in the host system 5, the intervention status in the field C111 may automatically become the intervention state in conjunction with the record. The management process of the intervention status is not essential to the business support method and may be omitted as appropriate.

[0119] [Creating Drug Information Sheet Sh1] In relation to the process of creating the drug information statement Sh1, for example, the statement creation screen P3 shown in FIG. 7 and FIG. 8 and the comparison screen P4 shown in FIG. 9 are displayed.

[0120] The provision document creation screen P3 includes an information display area R31, a button group area R32, and a patient information area R33. The first drug information D11, the second drug information D12, and the additional information D13 for one patient are displayed in the information display area R31. The additional information D13 is displayed, for example, in a comment field C320 or the follow-up comment field C330 in the information display area R31. In the example of FIG. 7, the first drug information D11 is displayed in the information display area R31. In the example of FIG. 8, the second drug information D12 and the additional information D13 are displayed in the information display area R31. The button group area R32 displays a plurality of buttons to be operated by the user. Specifically, the button group area R32 displays a registration button B31, a print button B32, the comparison button B33, a patient memo button B34, a back button B35, and the like. The patient information area R33 displays information about the patient for whom the first drug information D11, etc. are displayed in the information display area R31. Specifically, the patient information area R33 displays a patient ID, a patient name, a ward, a medical department, hospitalization / outpatient status, admission date, discharge date, pharmacist information, doctor information, etc. Furthermore, the patient information area R33 displays the intervention status that is the same as that in column C111 of the patient list screen P1, the presence or absence of the patient's consent that is the same as that in column C112, and the evaluation adjustment status that is the same as that in column C113.

[0121] More specifically, in this embodiment, as an example, the information display area R31 displays a plurality of medicines arranged vertically (up and down) so that each row corresponds to an individual medicine. A slide bar Sb31 is provided at the right end of the information display area R31, and the display contents of the information display area R31 can be scrolled vertically in response to the operation of the slide bar Sb31. Furthermore, in this embodiment, the information display area R31 has a first display area R311 (see FIG. 7) for displaying the first medicine information D11 and a second display area R312 (see FIG. 8) for displaying the second medicine information D12 arranged vertically. Here, as an example, since the first display area R311 is located above the second display area R312, the information display area R31 is scrolled downward from the state shown in FIG. 7 by operating the slide bar Sb31, and the second display area R312 is displayed as shown in FIG. 8. Further, below the second display area R312 in the information display area R31, the comment field C320 and the follow-up comment field C330 are displayed.

[0122] In the information display area R31, the first display area R311 and the second display area R312 are both divided horizontally (left and right) into a plurality of columns C301 to C312, and information about each drug is displayed in the plurality of columns C301 to C312. The column C301 displays a check box for selection, the column C302 displays whether the drug is brought with the patient, the column C303 displays the drug name, the column C304 displays the daily dosage, the column C305 displays the unit, the column C306 displays the start date of the drug, the column C307 displays the method of use, and the column C308 displays the number of days the drug is to be taken. The number of days the drug is to be taken indicates the number of days the drug is to be taken, that is, how many days the drug is to be taken from the start date of the drug. Furthermore, the column C309 displays the number of cautions, the column C310 displays whether the drug is an antipsychotic drug, the column C311 displays the management category, and the column C312 displays the reason / progress. It should be noted that the column C302 is not set for the second display region R312.

[0123] In the column C302, "Keep" is displayed for the medicine cited from the discrimination result data (i.e., the brought-in medicine) or the medicine cited from the discrimination support system 4 by operating the brought-in medicine button B302, and the other medicines are blank. The column C309 is operated to call up the information of the caution medicine master to which the medicine belongs. In this embodiment, the input of the columns C301 to C312 is basically performed automatically, for example, by linking with the upper system 5. However, the input of at least one of the columns C301 to C312 may be performed manually by the user. For example, the column C312 can be automatically inserted by the reason / progress management process described later, but the user can also manually input information. As an example, for a medicine that has been discontinued, the text "Discontinued" is entered in the column C312, and for a medicine that has been reduced, the text "Reduced" is entered in the column C312.

[0124] The output processing unit 114 may further output information regarding the change of the first medicine information D11 at the first timing. That is, for example, when the patient's brought-in medicines include medicines that have been "changed" in some way, such as being discontinued (from taking), reduced in dosage, changed to a generic drug, or changed to an alternative drug, at the time of hospitalization as the first timing, information regarding the change may be further output for the brought-in medicine. As an example, for the brought-in medicines that have been discontinued at the first timing, text such as "Discontinued at the time of hospitalization" is displayed in a column C312 in the first display area R311 for displaying the first medicine information D11. Alternatively, the display color of the record (row) of the brought-in medicine in the first display area R311 may be changed to, for example, red, to output (display) information regarding the change of the first medicine information D11. This makes it easier to manage the changes at the first timing.

[0125] In addition, at the top of each of the first display area R311 and the second display area R312, a Do button B301, the Brought-in Drugs button B302, a Calculation button B303, a Row Insertion button B304, a Row Delete button B305, and a Rearrange button B306 are displayed. The Do button B301 is a button for displaying the prescription history of the patient, and any medicine can be cited from the prescription history to the first display area R311 or the second display area R312. The Brought-in Drugs button B302 is a button for displaying a discrimination call screen in cooperation with the discrimination support system 4, etc., and any medicine can be cited from the discrimination call screen to the first display area R311 or the second display area R312. The Calculation button B303 is a button for executing a CPZ conversion value. The row insert button B304 is a button for adding a row, i.e., a drug, to the information display area R31, and the row delete button B305 is a button for deleting information by row, i.e., by drug, from the information display area R31. The sort order button B306 is a button for changing the sort order of the selected drugs.

[0126] Furthermore, the number of target drugs and the CPZ conversion value are displayed between the brought-medicine button B302 and the calculation button B303. The number of target drugs is the total number of drugs included in the first display area R311 or the second display area R312, and the CPZ conversion value is the CPZ conversion value of the drugs included in the first display area R311 or the second display area R312.

[0127] In the comment field C320, for example, at the time of discharge, a comment such as a matter to be handed over from a doctor or a pharmacist to an external pharmacy or the like is input. As an example, a comment such as "The number of drugs was reduced by two from the time of admission to the time of discharge" is displayed in the comment field C320 in text form. In the follow-up comment field C330, for example, a follow-up comment from an external pharmacy or the like is input after discharge. As an example, a follow-up comment such as "A local family pharmacy has contacted us to inform us that the progress is good after the reduction in the number of drugs" is displayed in the follow-up comment field C330 in text form. In this embodiment, inputs to the comment field C320 and the follow-up comment field C330 are manually input by a user, but inputs to at least one of the comment field C320 and the follow-up comment field C330 may be automated, for example, by linking with the upper system 5.

[0128] The registration button B31 in the button group region R32 is a button for registering information displayed in the information display region R31 and the patient information region R33. The print button B32 is a button for printing the drug information sheet Sh1, and the comparison button B33 is a button for shifting to the comparison screen P4. The patient memo button B34 is a button for shifting to a patient memo screen for inputting a patient memo, and the back button B35 is a button for shifting to the previous screen (the patient list screen P1).

[0129] The provision record creation screen P3 can be edited as needed. Therefore, for example, when a prescription is changed to discontinue the administration of a certain medicine during hospitalization of a patient, the user edits the provision record creation screen P3 at that time.

[0130] On the other hand, the comparison screen P4 includes the first display region R41 and the second display region R42, as shown in Fig. 9. The comparison screen P4 is a screen for displaying the first medicine information D11 and the second medicine information D12 in an easy-to-compare manner. In the example of Fig. 9, the comparison screen P4 is displayed as a pop-up window superimposed on the provision document creation screen P3. However, this is not limiting, and the provision document creation screen P3 may be switched to the comparison screen P4.

[0131] Unlike the provision form creation screen P3, the comparison screen P4 displays the first display area R41 and the second display area R42 side by side in the horizontal direction (left and right direction). Therefore, unlike the provision form creation screen P3 in which the first display area R311 and the second display area R312 are vertically arranged, the comparison screen P4 can simultaneously display the first display area R41 and the second display area R42 without scrolling the screen. The comparison screen P4 makes it easy to compare the medicines to be taken by the patient at the time of hospitalization (first timing) with the medicines to be taken by the patient at the time of discharge (second timing).

[0132] In both the first display area R41 and the second display area R42, a plurality of medicines are displayed arranged vertically (up and down) such that each row corresponds to an individual medicine. Slide bars Sb41 and Sb42 are provided at the right end of each of the first display area R41 and the second display area R42. The display contents of the first display area R41 can be scrolled vertically in response to an operation of the slide bar Sb41, and the display contents of the second display area R42 can be scrolled vertically in response to an operation of the slide bar Sb42. That is, in this embodiment, the display change processing unit 115 can change the display contents of the first display area R41 and the display contents of the second display area R42 individually in response to the display change operation by the slide bars Sb41 and Sb42.

[0133] This makes it easy to compare all of the multiple types of medicines taken by the patient at the first timing (at the time of hospitalization) with all of the (0 to multiple types) medicines taken by the patient at the second timing (at the time of discharge) on the comparison screen P4, particularly for a patient taking multiple types of medicines at the time of hospitalization. In short, when the patient takes multiple types of medicines at the first timing, the output processing unit 114 displays the first medicine information D11 including information on all of the multiple types of medicines and the second medicine information D12 including information on all of the medicines taken by the patient at the second timing in a comparable manner. Here, the medicines taken at the second timing (at the time of discharge) are not limited to multiple types, and may be 0 (zero) or one type. For example, if, during hospitalization of a patient, all of the multiple types of medicines that the patient was taking at the time of hospitalization are discontinued, resulting in zero types of medicines being taken by the patient at the time of discharge, the second medicine information D12 compared with the first medicine information D11 will be information on all zero types of medicines, that is, information on "no medicines to be taken." In this way, all of the multiple types of medicines that the patient was taking at the first timing and all of the medicines that the patient was taking at the second timing are displayed in a comparable manner, making it easier to understand how the medicines taken by the patient have changed.

[0134] Also, not only on the comparison screen P4 but also on the prescription creation screen P3, the first medicine information D11 including information on all of the medicines to be taken by the patient at the first timing and the second medicine information D12 including information on all of the medicines to be taken by the patient at the second timing are displayed in a comparable manner. That is, on the prescription creation screen P3 as well, the first medicine information D11 related to all of the medicines to be taken by the patient at the first timing (at the time of hospitalization) is displayed in the first display area R311, and the second medicine information D12 related to all of the medicines to be taken by the patient at the second timing (at the time of discharge) is displayed in the second display area R312. Therefore, by comparing the display contents of the first display area R311 and the display contents of the second display area R312, the first medicine information D11 and the second medicine information D12 can be compared.

[0135] The first display area R41 and the second display area R42 are both divided horizontally (left and right) into a plurality of columns C401 to C404, and information about each drug is displayed in the plurality of columns C401 to C404. Column C401 displays a selection check box, column C402 displays the drug name, column C403 displays the daily dosage, and column C404 displays the reason / progress.

[0136] Furthermore, the number of selected drugs and their CPZ equivalents are displayed at the top of each of the first display area R41 and the second display area R42. The number of selected drugs is the total number of drugs selected in the first display area R41 or the second display area R42, and the CPZ equivalents are the CPZ equivalents of the drugs included in the first display area R41 or the second display area R42.

[0137] The comparison screen P4 includes a close button B41, which is a button for closing the comparison screen P4 and returning to the offer document creation screen P3.

[0138] 10 and 11 are examples of the drug information statements Sh1 and Sh2 created on the statement creation screen P3. The drug information statements Sh1 and Sh2 are printed by operating the print button B32 on the statement creation screen P3 or by operating the statement print button B13 on the patient list screen P1. Here, the format (layout) of the drug information statements Sh1 and Sh2 to be printed can be selected by the user. For example, the drug information statement Sh1 shown in FIG. 10 is an A4 size form, and the drug information statement Sh2 shown in FIG. 11 is a label for a notebook (medicine notebook). Furthermore, although both the drug information statements Sh1 and Sh2 are intended for dispensing pharmacies, there may be formats for in-hospital use, etc.

[0139] As shown in FIG. 10, the drug information document Sh1 includes information on drugs to be taken by a certain patient. More specifically, the drug information document Sh1 includes the first drug information D11 on drugs to be taken by a patient at the first timing (at the time of hospitalization) and the second drug information D12 on drugs to be taken by a patient at the second timing (at the time of discharge), similar to the drug information creation screen P3. In the drug information document Sh1, the first drug information D11 and the second drug information D12 are described in a manner that can be distinguished from each other, for example, by separating the description columns. In both the first drug information D11 and the second drug information D12 in the drug information document Sh1, a plurality of drugs are described in a vertical (up and down) arrangement such that each row corresponds to an individual drug. In addition, both the first drug information D11 and the second drug information D12 include drug identification information such as drug name, and information on the drug such as usage, daily dosage, unit, and reason. Furthermore, the number of drugs and the CPZ equivalent value are described at the top of each of the first drug information D11 and the second drug information D12. The number of drugs is the total number of drugs included in the first drug information D11 or the second drug information D12, and the CPZ equivalent value is the CPZ equivalent value of the drugs included in the first drug information D11 or the second drug information D12.

[0140] The drug information statement Sh1 further includes information about the patient and special notes. The special notes cite the additional information D13 as a comment entered in the comment field C320 of the statement creation screen P3. In the example of FIG. 10, a comment such as "Two medications were reduced from the time of admission to the time of discharge" (the additional information D13) is entered in text form as the special notes. Note that the drug information statement Sh2 shown in FIG. 11 has a different size and layout, but basically contains the same content as the drug information statement Sh1. In the example of FIG. 2, the drug information statement Sh2 is divided into two pages.

[0141] An example of a procedure of the process of the control unit 11 related to the process of creating the drug information statement Sh1 will be described with reference to Fig. 12. In the following, the process of creating the drug information statement Sh1 at the time of discharge of a patient will be taken as an example.

[0142] <Step S31> In step S31, the control unit 11 displays the provision form creation screen P3. Specifically, when the provision form creation button B12 is operated on the patient list screen P1, the screen displayed on the display unit 24 of the client terminal 2 transitions from the patient list screen P1 to the provision form creation screen P3.

[0143] <Step S32> In step S32, the first acquisition processing unit 111 of the control unit 11 acquires the first medicine information D11 (the first acquisition process), and the second acquisition processing unit 112 of the control unit 11 acquires the second medicine information D12 (the second acquisition process). Furthermore, the third acquisition processing unit 113 of the control unit 11 acquires the additional information D13. This allows information necessary for creating the medicine information sheet Sh1 to be acquired.

[0144] <Step S33> In step S33, the output processing unit 114 of the control unit 11 updates the offer document creation screen P3. At this time, the output processing unit 114 updates the offer document creation screen P3 according to various information acquired in step S32. In the offer document creation screen P3, the first medicine information D11 and the second medicine information D12 are displayed separately in the first display area R311 and the second display area R312. In other words, the first medicine information D11 is displayed in the first display area R311, and the second medicine information D12 is displayed in the second display area R312.

[0145] As an example, in this embodiment, the first drug information D11 and the second drug information D12 are displayed in a manner that allows them to be distinguished from each other by being displayed separately in the first display region R311 and the second display region R312. Furthermore, in the provision book creation screen P3, the first drug information D11, the second drug information D12, etc. can also be edited.

[0146] <Step S34> In step S34, the control unit 11 judges whether or not the comparison button B33 on the offer document creation screen P3 is operated. If the comparison button B33 is operated (S34: Yes), the control unit 11 shifts the process to step S35. On the other hand, if a predetermined time has elapsed without the comparison button B33 being operated (S34: No), the control unit 11 shifts the process to step S37.

[0147] <Step S35> In step S35, the output processing unit 114 of the control unit 11 displays the comparison screen P4. On the comparison screen P4, the first display area R41 and the second display area R42 are displayed side-by-side. Therefore, the output processing unit 114 simultaneously displays at least a part of the first display area R41 and at least a part of the second display area R42 on one screen.

[0148] <Step S36> In step S36, the display change processing unit 115 of the control unit 11 executes a display change process. Here, in the comparison screen P4, the slide bars Sb41 and Sb42 are provided individually in the first display region R41 and the second display region R42. Therefore, the display change processing unit 115 changes the display contents of the first display region R41 and the second display region R42 individually in the comparison screen P4 in response to the display change operation of individually operating the slide bars Sb41 and Sb42.

[0149] <Step S37> In the step S37, the control unit 11 judges whether or not the print button B32 on the offer document creation screen P3 is operated. If the print button B32 is operated (S37: Yes), the control unit 11 shifts the process to step S38. On the other hand, if a predetermined time has elapsed without the comparison button B32 being operated (S37: No), the control unit 11 shifts the process to step S34.

[0150] <Step S38> In step S38, the control unit 11 prints the drug information statement Sh1. At this time, the user selects a format (layout) of the drug information statement Sh1. Specifically, the control unit 11 outputs (transmits) print data of the drug information statement Sh1 to the printer 3. As a result, the drug information statement Sh1 is printed by the printer 3.

[0151] The process of creating the drug information sheet Sh1 is not essential to the business support method and can be omitted as appropriate.

[0152] [Reason / Progress Management Process] In relation to the reason / progress management process, for example, the offer document creation screen P3 is displayed.

[0153] Specifically, the column C312 of the information display area R31 on the provision book creation screen P3 displays reasons / progresses related to the medicine. That is, on the provision book creation screen P3, for each medicine displayed in the information display area R31, matters related to changes in prescription contents are displayed as reasons / progresses. In this embodiment, the column C312 displays, as reasons / progresses, reduction, change, reduction in dosage, (discontinuation of taking), change to a generic drug, change to an alternative drug, and the like, for the medicine to be taken. According to the "process of managing reasons / progresses", input to the column C312 is automatically performed by the control unit 11.

[0154] In short, the progress determination processing unit 116 of the control unit 11 determines the change information from the first drug information D11 and the second drug information D12 included in the provision creation screen P3. For example, if one drug included in the first drug information D11 is not included in the second drug information D12, the progress determination processing unit 116 determines the change information for the drug to be discontinuation of taking the drug. Then, the reason / progress of "discontinuation" is automatically inserted in the column C312 for the drug. Alternatively, if it is determined that the number of types of drugs to be taken has decreased from an overall comparison between the first drug information D11 and the second drug information D12, the progress determination processing unit 116 determines the change information for the drug to be a reduction in dosage. Furthermore, if the progress determination processing unit 116 determines that the change is a change to a generic drug or a change to an alternative drug by referring to the drug master or the like, it determines the change information for the drug to be a change to a generic drug or a change to an alternative drug.

[0155] That is, when the drug that the patient was taking at the first timing is no longer the drug that the patient was taking at the second timing, the progress determination processing unit 116 outputs the change information regarding the change content to the output processing unit 114, with the stop of taking the drug as the change content of the second drug information D12 to the first drug information D11. In this embodiment, since the first timing is "at the time of admission" and the second timing is "at the time of discharge", when the patient is not taking one or more drugs that the patient was taking at the time of admission at the time of discharge, the stop of taking the one or more drugs (or reduction in dosage) is included in the change information as the change content. In other words, when the patient is stopped taking any of the drugs due to the efforts during the hospitalization of the patient, the fact (stop or reduction) is automatically inserted as the change information in the reason / progress column C312. The change information regarding the stop of taking such a drug (reduction) is basically inserted in the column C312 of the drug in the first display area R311, not in the second display area R312. Here, discontinuation of medication also includes cases where, for example, all medications that the patient was intended to take at the first timing (time of admission) are discontinued, resulting in the patient being left with zero types of medication at the second timing (time of discharge).

[0156] An example of a procedure of the process of the control unit 11 related to the process of managing the cause / progress will be described with reference to FIG.

[0157] <Step S41> In step S41, the control unit 11 displays the provision form creation screen P3. Specifically, when the provision form creation button B12 is operated on the patient list screen P1, the screen displayed on the display unit 24 of the client terminal 2 transitions from the patient list screen P1 to the provision form creation screen P3.

[0158] <Step S42> In step S42, the progress determination processing unit 116 of the control unit 11 compares the first medicine information D11 and the second medicine information D12 included in the offer document creation screen P3. Then, the progress determination processing unit 116 performs a progress determination process for automatically determining the change information from a comparison result.

[0159] <Step S43> In step S43, the progress determination processing unit 116 of the control unit 11 updates the provision document creation screen P3. At this time, the progress determination processing unit 116 automatically inserts the change information determined in step S42 into column C312 of the provision document creation screen P3. As a result, in the updated provision document creation screen P3, the reason / progress is automatically input into column C312.

[0160] In addition, the column C312 of the provision document creation screen P3 may contain a mixture of automatically inserted reason / progress and reason / progress manually input by the user. When the reason / progress column C312 of any drug is selected on the provision document creation screen P3, details of the reason / progress of the drug are displayed. Note that the reason / progress management process is not essential to the business support method and can be omitted as appropriate.

[0161] [Warning information output processing] In connection with the output process of the warning information, for example, the offer document creation screen P3 is displayed.

[0162] When a specific caution drug is included in the drug to be taken by the patient at least one of the first timing and the second timing, the output processing unit 114 outputs the caution information regarding the caution drug by including it in at least one of the first drug information D11 and the second drug information D12. Specifically, when displaying the provision creation screen P3, the output processing unit 114 refers to the first drug information D11 and the second drug information D12 and automatically determines whether the caution drug is included in the first drug information D11 or the second drug information D12.

[0163] Then, for the drug extracted as the caution drug, the output processing unit 114 searches for the caution information on the caution drug, for example, by referring to the caution drug master. The output processing unit 114 automatically inserts the caution information, for example, into the column C312 of the information display area R31 on the offer document creation screen P3. The caution information is, for example, text data recorded in the caution drug master. Specific examples of the text data as the caution information include abstract sentences such as "This drug requires particularly careful administration" and "This drug should be considered for initiation," sentences showing specific side effects such as "Aggravation of the risk of gastrointestinal bleeding," and sentences showing specific usage methods such as "Do not use for patients with heart failure or those with a history of heart failure. For elderly people, start with a small amount and administer carefully." In addition, text data such as "Drugs that are prone to serious adverse effects," "Efficacy is inferior to safety," "There are safer alternative drugs," and "Adequate explanation to patients and families is required" may be included in the caution information. Various types of master information including the text data can be appropriately registered and edited by a user operation using the server 1 or the client terminal 2. That is, in addition to the information that is automatically inserted in the cause / progress management process, the warning information can also be automatically inserted into column C312.

[0164] In addition, the column C312 of the provision creation screen P3 may contain a mixture of the automatically inserted warning information and warning information manually input by the user. The extracted warning drugs may be reflected in the number of warning drugs displayed in the column C115 of the patient list screen P1, for example. The output process of the warning information is not essential to the business support method, and may be omitted as appropriate.

[0165] [Restriction processing] In association with the restriction process for restricting an operation for changing the second medicine information D12 with respect to the first medicine information D11, for example, the offer document creation screen P3 is displayed.

[0166] In the prescription creation screen P3, the first medicine information D11 and the second medicine information D12 are basically allowed to be edited. Therefore, for example, when the contents of a prescription for a certain patient are changed, the user edits at least one of the first medicine information D11 and the second medicine information D12 in response to the change on the prescription creation screen P3. However, in this embodiment, for example, the doctor's intervention status (field C111) and the presence or absence of the patient's consent (field C112) are managed on the patient list screen P1. And, in addition to the doctor's decision to intervene, the patient's consent is also required for the intervention in the initiative. Therefore, for example, if at least one of the doctor's decision to intervene and the patient's consent is missing, the intervention in the initiative is not performed.

[0167] Therefore, when the intervention status is other than the intervention status or when the patient's consent is not given, the control unit 11 restricts the operation by the restriction process so that the operation for changing the second medicine information D12 to the first medicine information D11 is not performed by mistake. That is, the restriction processing unit 119 of the control unit 11 restricts the operation for changing the second medicine information D12 to the first medicine information D11 at least when the intervention status is the unconfirmed status or the non-intervention status. This makes it possible to reduce erroneous operations by the user.

[0168] An example of a procedure of the process performed by the control unit 11 in relation to the restriction process will be described with reference to FIG.

[0169] <Step S51> In step S51, the control unit 11 displays the provision form creation screen P3. Specifically, when the provision form creation button B12 is operated on the patient list screen P1, the screen displayed on the display unit 24 of the client terminal 2 transitions from the patient list screen P1 to the provision form creation screen P3.

[0170] <Step S52> In step S52, the restriction processing unit 119 of the control unit 11 judges whether or not the restriction condition for executing the restriction processing is satisfied. If the intervention status is other than the intervention state or the patient's consent is not given, the control unit 11 judges that the restriction condition is satisfied (S52: Yes) and moves the process to step S53. On the other hand, if the intervention status is the intervention state and the patient's consent is given, the control unit 11 judges that the restriction condition is not satisfied (S52: No), skips step S53, and ends the process.

[0171] <Step S53> In step S53, the restriction processing unit 119 of the control unit 11 executes the restriction process to restrict an operation for changing the second medicine information D12 on the first medicine information D11. Specifically, the restriction processing unit 119 executes a process to invalidate an operation for editing the first medicine information D11 and the second medicine information D12 on the offer document creation screen P3.

[0172] The restriction process is not essential to the business support method and can be omitted as appropriate.

[0173] [Continuation medication determination process] The process of determining whether or not a medication should be continued is executed, for example, prior to displaying the patient list screen P1.

[0174] That is, in the patient list screen P1, the total number of types of medicines, including the medicines brought by the patient at the time of admission and the medicines prescribed at the hospital to be taken by the patient before admission, is displayed as the number of medicines brought by the patient in the field C114. In addition, for example, the number of oral medicines when searching for a patient on the patient search screen P2 is searched for based on the number of types of medicines counted in the number of medicines brought by the patient in the field C114 of the patient list screen P1. On the other hand, for example, among the medicines taken by the patient before admission, there are medicines that were stopped one week before the admission date, medicines that were started the day before the admission date, and medicines that are taken irregularly, such as only during seizures. And, for medicines that are not taken continuously, such as these medicines, it may be required to exclude them from the medicines taken by the patient at the time of admission (the first timing) (the medicines counted in the number of medicines brought by the patient in the field C114).

[0175] As an example, when taking measures such as reducing medication as a measure against polypharmacy, a case is assumed in which only "oral medications that have been taken for more than four weeks before hospitalization" are included in the medications to be taken at the time of hospitalization. For example, in Japan, the medical fee system specifies cases in which such patients are included in the measures against polypharmacy as a "drug comprehensive evaluation adjustment surcharge." In this case, the condition for including the medications to be taken at the time of hospitalization is that the medication has been taken continuously for more than four weeks before hospitalization, so it is necessary to determine whether or not the medication falls under the category of continued medication. According to the process for determining whether or not the medication falls under the category of continued medication, the determination of whether or not the medication falls under such a category can be automated, thereby reducing the burden on pharmacists' work.

[0176] Specifically, the continuation determination processing unit 110 of the control unit 11 determines whether or not the patient is taking the drug of interest, taking any drug that the patient is taking as the drug of interest (the continuation determination process). In the continuation determination process, in principle, if the patient is taking the drug of interest in all of a plurality of unit periods included in the specific period set based on the first timing, the drug of interest is determined to be taken continuously. In the above case, the first timing is the "date of admission" and the specific period is the "period of four weeks prior to the date of admission". In addition, the unit period is set to "one day" as an example. Therefore, in principle, if the patient is taking the drug of interest every day during the "period of four weeks prior to the date of admission" (the specific period), the drug of interest is determined to be taken continuously. Conversely, if the patient is not taking the drug of interest every day during the "period of four weeks prior to the date of admission" (the specific period), the drug of interest is determined to be not taken continuously.

[0177] However, in this embodiment, as an exception, in the continuation determination process, if there is one or more unit periods in which the target drug is not intended for the patient among the multiple unit periods and the administration history of the target drug satisfies the determination condition, it is determined that the target drug is continuously taken. That is, in the above case, even if there are several days (the unit periods) in which the target drug is not intended for the patient during the "period of four weeks prior to the date of hospitalization" (the specific period), if the administration history of the target drug satisfies the determination condition, it is exceptionally determined that the target drug is continuously taken. The determination condition includes, for example, that there are no consecutive days (the unit periods) in which the target drug is not intended for the patient for "three or more days".

[0178] Fig. 15 shows a specific example of the taking history (medication history) of drugs A to H (the target drugs) for a certain patient. In this case, the continuation determination process produces a determination result such as that shown at the right end of Fig. 15. In Fig. 15, the diagonal line (shaded) portion indicates the day on which the drug was taken (the unit period), and the determination result "◯" indicates that the drug is taken continuously, "△" indicates that the drug is not taken continuously, and "△" indicates that confirmation is required.

[0179] Here, the continuation determination processing unit 110 determines whether or not the determination condition is satisfied based on the history of taking the target drug for both the retroactive period T2, which is set before the start of the specific period T1, and the specific period T1. The "start time of the specific period T1" here is the start time of the specific period T1 in the time series, that is, the start point (starting period) of the specific period T1, and in the above case, it is "4 weeks before" the "date of hospitalization" (the first timing). In the example of FIG. 15, the "date of hospitalization" which is the first timing is "July 1", and the "4 weeks before the date of hospitalization" which is the start time of the specific period T1 is "June 2". Thus, in this embodiment, the retroactive period T2, which is a period further back from the start time (June 2) of the specific period T1, is set, and the drug taking history of the retroactive period T2 is also included in the determination of whether or not the drug is taken continuously. In short, by setting not only the specific period T1, which is the original subject of judgment, but also the retroactive period T2 going back from the specific period T1, the period to be judged for the medication history is expanded, and the accuracy of the judgment of the continuous medication is improved. In FIG. 15, as an example, it is assumed that the combined period of the specific period T1 and the retroactive period T2 (period surrounded by a dashed line) is "45 days". In other words, the retroactive period T2 is a period going back "17 days" from the start of the specific period T1.

[0180] Specifically, the determination condition includes that the target drug is not a target for the patient in the first unit period on the timeline among the multiple unit periods, and that the target drug is a target for the patient in the retrospective period T2. The "first unit period on the timeline" here is a unit period that is a first unit period on the timeline in the specific period T1 and includes the start point (starting period) of the specific period T1. Therefore, in the example of FIG. 15, the "first unit period on the timeline" is "four weeks before the hospitalization date" (June 2), which is the start point of the specific period T1. As a result, it is possible to determine that even for drugs C and D in FIG. 15 that are not a target for the patient at the start point (June 2) of the specific period T1, they are continuously taken for four weeks or more based on the history of taking the drug in the retrospective period T2. Note that there is no day in the retrospective period T2 when the drug E is a target for the patient, so it is determined that the drug E is not a target for the patient for the continuous taking. This makes it possible to improve the accuracy of determining whether the drug is continuously taken.

[0181] The specific period may be a period based on the first timing, and is not limited to a period with the first timing as the end point (finish) on the timeline. For example, it may be a three-week period with the first timing as the start point (starting point) on the timeline, a two-week period including one week before and after the first timing, or a four-week period going back from the day before the first timing. The unit period may be appropriately set according to the specific period, and is not limited to "one day", but may be, for example, "1.5 days", "2 days", "3 days", "1 hour", "1.5 hours", "2 hours", "6 hours", or "time periods" such as morning / afternoon / evening.

[0182] Here, the unit period is preferably a period determined according to at least one of the target drug and the patient. That is, what kind of history of taking the drug is considered to be the continuous taking depends on, for example, the efficacy of the drug and the prescription of the patient, so it is preferable that the unit period is dynamically set according to at least one of the target drug and the patient. As an example, for a drug that is recommended to be taken at intervals of 3 days or more when the patient is an elderly person aged 65 or older, the unit period is set to "4 days". This makes it possible to improve the accuracy of determining the continuous taking.

[0183] In FIG. 15, drug G is marked with a "△" because the start date of administration of drug G is unknown in the discrimination result data.

[0184] An example of a procedure of the process of the control unit 11 related to the continuous medication determination process will be described with reference to FIG.

[0185] <Step S61> In step S61, the first acquisition processing unit 111 of the control unit 11 acquires the first medicine information D11 (the first acquisition process), and the second acquisition processing unit 112 of the control unit 11 acquires the second medicine information D12 (the second acquisition process). Furthermore, the third acquisition processing unit 113 of the control unit 11 acquires the additional information D13.

[0186] <Steps S62 and S63> In step S62, the continuation determination processing unit 110 of the control unit 11 sets the specific period T1 and determines whether the target drug is taken by the patient in all of the unit periods included in the specific period T1. In the example of Fig. 15, for drugs A and F that are taken by the patient every day in the specific period T1, the control unit 11 determines that they are taken in all of the unit periods (S62: Yes), and determines that they are taken continuously (S63). On the other hand, for drugs B to E, G, and H, the control unit 11 determines that they are not taken in all of the unit periods (S62: No), and moves the process to step S64.

[0187] <Steps S64 and S65> In step S64, the continuation determination processing unit 110 of the control unit 11 determines whether or not the medication history in the specific period T1 satisfies the determination condition. If the determination condition includes that the patient does not have three or more consecutive days (the unit period) on which medication is not to be taken, in FIG. 15, the control unit 11 determines that the medication B and H do not satisfy the determination condition (S64: No) and do not correspond to the continuous medication (S65). On the other hand, the control unit 11 determines that the medication C, D, and E satisfy the determination condition (S64: Yes) and shifts the process to step S66.

[0188] <Step S66> In step S66, the continuation determination processing unit 110 of the control unit 11 sets the retrospective period T2 and determines whether or not the drug administration history in the retrospective period T2 satisfies the determination condition. In the example of FIG. 15, the drug C, D, and E are not the target drug of the patient in the first unit period in the chronological order among the multiple unit periods. Therefore, the control unit 11 determines the drug administration history in the retrospective period T2 for the drugs C, D, and E. Here, for the drugs C and D, the control unit 11 determines that the drug administration history in the retrospective period T2 satisfies the determination condition (S66: Yes), and determines that the drug corresponds to the continuous administration (S63). On the other hand, for the drug E, the control unit 11 determines that the drug administration history in the retrospective period T2 does not satisfy the determination condition (S66: No), and determines that the drug does not correspond to the continuous administration (S65).

[0189] In addition, in the provision creation screen P3, it is preferable that only the medicines determined to be the continued medication in the continued medication determination process are included in the first medicine information D11. In this case, for example, only the medicines determined to be the continued medication among the brought-in medicines are displayed in the first display area R311 as the first medicine information D11. In other words, among the brought-in medicines, the medicines determined not to be the continued medication are not displayed in the first display area R311. In addition, the continued medication determination process is not essential to the business support method, and can be omitted as appropriate.

[0190] However, the above-mentioned various flowcharts are merely examples, and processes may be added or omitted as appropriate, and the order of processes may be changed as appropriate. As an example, instead of step S32 in the flowchart of FIG. 12, a step (first acquisition process) in which the first acquisition processing unit 111 acquires the first medicine information D11, and a step (second acquisition process) in which the second acquisition processing unit 112 acquires the second medicine information D12 may be included. In this case, the first acquisition process and the second acquisition process may be executed first, or may be executed simultaneously. Furthermore, a step (third acquisition process) in which the third acquisition processing unit 113 acquires the additional information D13 may be further included.

[0191] [Usefulness] First, in Japan, the medical fee system prescribes medical fee points for the above-mentioned efforts to combat polypharmacy. In other words, the medical fee points are set as "basic hospitalization fee surcharge" and "drug comprehensive evaluation adjustment surcharge", and medical fee points are added as "drug comprehensive evaluation adjustment surcharge" for the above-mentioned efforts that meet certain criteria. Specifically, for example, for a patient who was prescribed six or more types of oral medication before hospitalization, if the prescription is comprehensively evaluated, the prescription is changed, and necessary medical guidance is provided, "100 points" will be added once only at the time of discharge. In order to evaluate the patient's condition, side effects, and the presence or absence of problems in medical treatment, a conference is held among doctors, pharmacists, nurses, and other professionals to conduct a comprehensive evaluation of the medication, and prescription changes are made, such as changing to an appropriate dosage and administration, discontinuing the medication suspected of causing side effects, and switching to an alternative medication that is more effective and safer. If the evaluation results and the main points of the changes are recorded in the medical record, etc., and the number of prescribed oral medications is reduced by two or more at the time of discharge, an additional "150 points" will be added as a drug adjustment surcharge. As a result, according to the above-mentioned efforts to combat polypharmacy, a medical fee point of "250 points" can be added.

[0192] Assuming the medical fee system is in place, the introduction of the business support system 10 and the business support program according to this embodiment is expected to provide the following benefits.

[0193] The first usefulness is the reduction in screening time for polypharmacy patients. Mainly because the patient extraction process mentioned above can automate patient extraction, it is possible to reduce the screening time for polypharmacy patients to, for example, about one-fourth of the time required when the user (pharmacist) does the screening manually. As a result, the workload of the user (pharmacist) in relation to screening can be significantly reduced.

[0194] The second usefulness is the reduction in the time required to create the drug information document at the time of discharge. Mainly, the process of creating the drug information document Sh1 simplifies the creation of the drug information document Sh1, so the time required to create the drug information document Sh1 at the time of discharge from the hospital can be reduced to, for example, about two-thirds compared to when the user (pharmacist) does it manually. As a result, the workload of the user (pharmacist) in creating the drug information document Sh1 can be significantly reduced.

[0195] The third usefulness is the improvement of the medical fee point acquisition status by the drug comprehensive evaluation adjustment surcharge and drug adjustment surcharge. Mainly by the management processing of the intervention status, the work related to the acquisition of the medical fee points can be made more efficient, so it is possible to increase the acquisition status of the medical fee points by, for example, about 10 times. As a result, it becomes possible to acquire the appropriate medical fee points more easily and reliably.

[0196] [Other configuration examples for identification work] The method of distinguishing the brought-in medicines is not limited to the above-mentioned method using the distinction support system 4 (automatic distinction). For example, the method may be a method in which a user (such as a pharmacist) visually checks and distinguishes the brought-in medicines (manual distinction) without using the distinction support system 4. In this case, the user manually distinguishes the brought-in medicines and then manually inputs the brought-in medicine information into, for example, the client terminal 2.

[0197] [Variations] A plurality of components included in the task support system 10 may be distributed among a plurality of housings. For example, at least one of the components of the server 1, such as a first acquisition processing unit 111, a second acquisition processing unit 112, a third acquisition processing unit 113, an output processing unit 114, a display change processing unit 115, a progress determination processing unit 116, an extraction processing unit 117, a status display processing unit 118, a restriction processing unit 119, and a continuation determination processing unit 110, may be provided in the client terminal 2 or another device (including the printer 3, the discrimination support system 4, and the upper system 5). In this case, the task support program is distributed and installed in, for example, the server 1 and the client terminal 2, and the task support method is executed by the server 1, the client terminal 2, and the like in cooperation with each other.

[0198] Conversely, in the above embodiment, a plurality of components that are distributed among the server 1, the client terminal 2, the printer 3, etc. may be integrated into one housing. For example, all of the functions of the server 1, the client terminal 2, and the printer 3 may be integrated into one device.

[0199] In the above embodiment, the term "drug" is described as referring to oral medication in principle, but the term "drug" may include at least one of an injection drug and an external medicine in addition to or instead of an oral medication. For example, when the term "drug" includes oral medication, injection drug, and external medicine, each of the first display area R311 and the second display area R312 of the provision creation screen P3 may include information on all of the oral medication, injection drug, and external medicine. However, in this case, for example, it is preferable that the oral medication, injection drug, and external medicine can be distinguished for each drug by the management classification column C311 or the like. Furthermore, it is preferable that the determination of the reduction in the dosage in the change information is performed individually for each of the oral medication, injection drug, and external medicine. As a specific example, when only one type of oral medication is discontinued and only one type of external medicine is discontinued, the progress determination processing unit 116 does not determine that "two types of medication are reduced" but determines that "one type of medication is reduced" for each of the oral medication and the external medicine. As another specific example, judgments regarding reduction, changes, and dosage reductions may be made only for specific medications such as oral medications. In this case, even if one type of oral medication and one type of topical medication are discontinued, the progress judgment processing unit 116 will not count the topical medication as a reduction, but will judge it as "reduction of one type of medication."

[0200] In the above embodiment, the "brought-in medication" is described as including only medications prescribed at a hospital other than the hospital where the patient is admitted before hospitalization, but the "brought-in medication" may also include medications that are prescribed at the hospital where the patient is admitted and that the patient is to take before hospitalization. In other words, the "brought-in medication" may include both medications that are prescribed at a hospital other than the hospital where the patient is admitted before hospitalization and medications that are prescribed at the hospital where the patient is admitted. In this case, medications that the patient is to take before hospitalization can be "brought-in medications" regardless of where they were prescribed. In this way, when the "brought-in medication" includes medications prescribed at the hospital where the patient is admitted, the first medication information D11 on the provision form creation screen P3 basically includes only information regarding the brought-in medications.

[0201] Moreover, the first display area R311 of the provision record creation screen P3 may include information on drugs that have been added to the patient's medication during the patient's hospitalization. In this case, the first display area R311 of the provision record creation screen P3 may list drugs that have been added to the patient's medication before hospitalization and drugs that have been added to the patient's medication after hospitalization and before discharge. However, in this case, it is preferable that the patient's medication before hospitalization and the patient's medication after hospitalization can be distinguished by, for example, the column C302 indicating whether the medication is the patient's own medication or the column C306 indicating the medication start date. Furthermore, for example, it is preferable that the determination of the reduction in medication, etc. in the change information is performed based on information on the drug that has been added to the patient's medication before hospitalization (the first drug information D11), excluding drugs that have been added to the patient's medication after hospitalization. As a specific example, when a drug A is added to the medication after hospitalization and two types of medication, namely drug A and drug B that have been added to the patient's medication before hospitalization, are discontinued by the time of discharge, the progress determination processing unit 116 determines that the reduction in medication is "one type of medication" rather than "two types of medication reduction."

[0202] Furthermore, the "event" is not limited to hospitalization, and may be, for example, surgery, medical examination, or hospital visit (for a certain period of time), etc. For example, if the event is a "hospital visit," the timing related to the start of the hospital visit as the event, i.e., the first day of the hospital visit, is the first timing, and the timing related to the end of the hospital visit as the event, i.e., the last day of the hospital visit, is the second timing.

[0203] In the above embodiment, each of the first timing and the second timing is defined in units of a day (one day) such as the date of admission or the date of discharge, but this is not limited to the example. At least one of the first timing and the second timing may be defined in units of, for example, a time such as date and time, a time period such as morning / afternoon / evening, a week, a month, a season, a course of a treatment plan, or a year. As an example, if the "event" is a surgery, the start time (including the scheduled time) of the surgery may be the first timing, and the end time (including the scheduled time) of the surgery may be the second timing.

Claims

[Claim 1] an output processing unit that outputs, in a distinguishable manner, first drug information on a drug to be taken by the patient at a first timing related to an event of the patient and second drug information on a drug to be taken by the patient at a second timing related to the event that is later than the first timing; Business support system.

Images