JP2017033107A - Dispensing support system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a dispensing support system which appropriately reflects a change in schedules of medication to be taken in a host system, so as to manage medication administration data.SOLUTION: A dispensing support system 10 includes: an acquisition processing section 110 for acquiring prescription data which indicate prescription contents of medications and correction data which indicate correction contents of schedules of the medications to be taken from a host system; a storage processing section 111 for storing medication administration data including the schedules of taking respective medications in a storage section 12 on the basis of the prescription data acquired by the acquisition processing section 110; and an update processing section 112 for updating the schedules of taking respective medications in the medication administration data stored in the storage section 12 on the basis of the correction data acquired by the acquisition processing section 110.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a dispensing support system capable of managing patient medication data.

  In hospitals, prescription data is issued by inputting prescription contents of medicines into an electronic medical record system and the like, and medicines are dispensed based on the prescription data. Conventionally, there has been known a dispensing support system that supports a medicine dispensing operation (see, for example, Patent Document 1). In this type of dispensing support system, medication data such as a medication schedule or medication history of each patient may be managed based on prescription data received from a host system such as an electronic medical record system.

JP 2015-14865 A

  By the way, in a hospital, a patient's medication schedule may be changed by a doctor's judgment after issuing prescription data, and the contents of the change may be input to an electronic medical record system. For example, the change of the dosing schedule includes stopping or interrupting taking. However, in the past, changes in taking schedules in the electronic medical record system have not been transmitted to the dispensing support system. For this reason, in the conventional dispensing support system, the administration of the administration data that appropriately reflects the change of the administration schedule in the electronic medical record system has not been performed.

  An object of the present invention is to provide a dispensing support system capable of managing dosing data by appropriately reflecting changes in dosing schedules in a host system.

  The dispensing support system according to the present invention includes a storage processing unit that stores, in a storage unit, dosing data including a schedule of each medicine based on prescription data that is input, and the dosing data stored in the storage unit. And an update processing unit that updates the medication schedule of each medicine in response to input of correction data relating to the correction of the medication data.

  According to the present invention, since the dose data is updated in synchronization with a higher-level system such as an electronic medical record system that outputs the prescription data and the correction data, the user of the dispensing support system has to manage the dose data Is reduced.

  For example, it is conceivable that the correction content includes at least one of cancellation, interruption, and extension of taking the medicine in the unit of taking time.

  In addition, the dispensing support system may further include a display processing unit capable of displaying the presence / absence of medication at each medication time based on the medication data stored in the storage unit.

  In addition, the display processing unit includes a first display mode for displaying the presence / absence of each dose in each dose date for each drug and a second display mode for displaying the dose in each dose date for each drug. It may be possible to switch and execute.

  The storage processing unit may integrate each of the drug data when the drug data included in the prescription data includes at least drug data having the same patient name and drug name in the medication data. Conceivable.

  In addition, the update processing unit, for the drug data included in the correction data, if at least the drug data with the same patient name and drug name exists in the dose data, the content of the correction data in the dose data It is conceivable to update the dose data by reflecting it.

  Moreover, it is possible that the said memory | storage process part or the said update process part can convert the dosing time expressed by one of time or time in the said prescription data or the said correction data into the dosing time expressed by the other.

  The dispensing support system may further include a prescription check processing unit that determines whether or not the prescription data acquired by the acquisition processing unit is appropriate based on the dosing data stored in the storage processing unit. .

  Specifically, the dispensing support system includes one or a plurality of dispensing devices capable of executing a medicine dispensing process, and the dispensing device performs the dispensing process based on the prescription data determined to be appropriate by the prescription check processing unit. And a dispensing processing unit that executes

  Further, it is considered that the correction data is data that can specify only the target portion of the correction to be taken performed in the host system and the correction contents of the target portion. And it is possible that the said update process part updates only the data of the said target location among the said taking data memorize | stored in the said memory | storage part.

  ADVANTAGE OF THE INVENTION According to this invention, it is possible to manage dosing data reflecting the change of the dosing schedule in a high-order system suitably.

FIG. 1 is a block diagram showing a configuration of a dispensing support system according to an embodiment of the present invention. FIG. 2 is a diagram showing an example of prescription check data D1 used in the dispensing support system according to the embodiment of the present invention. FIG. 3 is a diagram showing an example of dose data D2 used in the dispensing support system according to the embodiment of the present invention. FIG. 4 is a flowchart showing an example of a dose data management process executed by the dispensing support system according to the embodiment of the present invention. FIG. 5 is a diagram showing an example of a dose management screen displayed by the dispensing support system according to the embodiment of the present invention. FIG. 6 is a diagram illustrating an example of a dose management screen displayed by the dispensing support system according to the embodiment of the present invention. FIG. 7 is a diagram showing an example of prescription data used in the dispensing support system according to the embodiment of the present invention. FIG. 8 is a diagram showing an example of prescription data used in the dispensing support system according to the embodiment of the present invention. FIG. 9 is a flowchart showing an example of a taking data update process executed by the dispensing support system according to the embodiment of the present invention. FIG. 10A is a diagram showing an example of correction data used in the dispensing support system according to the embodiment of the present invention. FIG. 10B is a diagram showing an example of the correction result of the dose data in the dispensing support system according to the embodiment of the present invention. FIG. 11A is a diagram showing an example of correction data used in the dispensing support system according to the embodiment of the present invention. FIG. 11B is a diagram illustrating an example of a correction result of the medication data in the dispensing support system according to the embodiment of the present invention. FIG. 12A is a diagram showing an example of correction data used in the dispensing support system according to the embodiment of the present invention. FIG. 12B is a diagram illustrating an example of a result of correcting the dosage data in the dispensing support system according to the embodiment of the present invention. FIG. 13A is a diagram showing an example of correction data used in the dispensing support system according to the embodiment of the present invention. FIG. 13B is a diagram illustrating an example of a result of correcting the dosage data in the dispensing support system according to the embodiment of the present invention. FIG. 14A is a diagram showing an example of correction data used in the dispensing support system according to the embodiment of the present invention. FIG. 14B is a diagram illustrating an example of a result of correcting the dosage data in the dispensing support system according to the embodiment of the present invention. FIG. 15A is a diagram showing an example of correction data used in the dispensing support system according to the embodiment of the present invention. FIG. 15B is a diagram illustrating an example of a result of correcting the dosage data in the dispensing support system according to the embodiment of the present invention. FIG. 16A is a diagram showing an example of correction data used in the dispensing support system according to the embodiment of the present invention. FIG. 16B is a diagram illustrating an example of a correction result of the dosage data in the dispensing support system according to the embodiment of the present invention. FIG. 17A is a diagram illustrating an example of a result of updating taking data in the dispensing support system according to the embodiment of the present invention. FIG. 17B is a diagram showing an example of the update result of the medication data in the dispensing support system according to the embodiment of the present invention. FIG. 18A is a diagram illustrating an example of the update result of the medication data in the dispensing support system according to the embodiment of the present invention. FIG. 18B is a diagram showing an example of the update result of the medication data in the dispensing support system according to the embodiment of the present invention.

  Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings for understanding of the present invention. In addition, the following embodiment is an example which actualized this invention, Comprising: The thing of the character which limits the technical scope of this invention is not.

[Dispensing support system 10]
The dispensing support system 10 according to the embodiment of the present invention is used in a medical institution such as a hospital or a dispensing pharmacy, for example. The user who operates the dispensing support system 10 is a medical worker such as a doctor, a nurse, or a pharmacist.

  As shown in FIG. 1, the dispensing support system 10 includes a server 1, a client terminal 2, a dispensing device 3, and a printer 4. The server 1 alone may be regarded as a dispensing support system according to the present invention. The server 1, the client terminal 2, the dispensing device 3, and the printer 4 are connected via a communication network 5 so that they can communicate wirelessly or by wire. The client terminal 2, the dispensing device 3, and the printer 4 included in the dispensing support system 10 may be plural. The communication network 5 is a LAN, a WAN, the Internet, an intranet, or the like.

  The server 1 is connected to a host system 6 such as an electronic medical record system or an ordering system via the communication network 5. In the host system 6, prescription data indicating prescription contents for each patient is issued in response to a user operation such as a doctor. Further, in the host system 6, when correction is made for each medication schedule corresponding to the prescription data in response to a user operation such as a doctor, correction data indicating the correction content is issued. The contents of correction include at least one of stopping, discontinuing, and extending the taking of the medicine in units of the taking time.

  Then, when the prescription data or the correction data is issued, the host system 6 inputs the prescription data and the correction data into the dispensing support system 10. Specifically, the host system 6 transmits the prescription data and the correction data to the server 1 via the communication network 5. The host system 6 includes a storage unit 61 that stores the prescription data or the correction data, and the server 1 accesses the storage unit 61 to actively acquire the prescription data or the correction data. May be.

  The prescription data includes, for example, information such as a prescription category, a patient name, a department, a medicine name, a dose, a dosage, a medication start date, and a medication end date. Further, the correction data includes information such as prescription classification, patient name, department, medicine name, dose, usage, and correction contents. For example, the contents of each item in the prescription data and the correction data are indicated by a preset code, and the server 1 can recognize the contents of each item of the prescription data and the correction data based on the code. It is.

  Further, in the host system 6, in addition to taking each medicine corresponding to the prescription data, an operation for correcting the prescription data may be performed. For example, the correction of the prescription data may include a change in medicine, a change in dose, or a change in usage. In this case, the host system 6 issues corrected prescription data corresponding to the corrected content of the prescription data, stores it in the storage unit 61 and inputs it to the dispensing support system 10. Thereby, in the said dispensing assistance system 10, it is possible that the said server 1 performs the dispensing process etc. which used the said dispensing apparatus 3 based on the said correction prescription data. That is, the correction data described in the present embodiment is data that is issued when the prescription data based on the prescription data is not interrupted or cancelled, but the content of the prescription data itself is not changed. Yes, different from the modified prescription data. Then, as will be described later, in the dispensing support system 10, when the prescription data is acquired, dose data is generated based on the prescription data, and when the correction data is acquired thereafter, the dose data is stored. Will be corrected.

[Dispensing equipment 3]
Each of the dispensing devices 3 is a device capable of executing a medicine dispensing process such as automatic medicine dispensing or support of a medicine dispensing operation by a pharmacist. For example, each of the dispensing devices 3 is a tablet dispenser, a powder dispenser, a liquid dispenser, a PTP sheet dispensing device, a mixed injection device, or a picking auxiliary device. For example, the tablet packaging machine has a plurality of medicine cassettes containing a plurality of types of tablets, dispenses tablets from the medicine cassette according to dispensing data input from the server 1, and dispenses them for each dose. A wrapping operation for wrapping with wrapping paper is executed. In accordance with the dispensing data input from the server 1, the powder medicine packaging machine performs a packaging operation for packaging the powdered powder in a dosed paper for each dose. The picking assisting device collates the prescription data with the medicine information of the picked medicine, and supports a medicine dispensing operation by a pharmacist.

[Printer 4]
The printer 4 prints information included in print data input from the server 1 or the client terminal 2 on a sheet such as paper. For example, the printer 4 is used in the dispensing support system 10 for printing a prescription, a medicine information, a notebook, or a medicine bag. In the dispensing support system 10, the prescription data, the correction data, or later-described medication data can be printed using the printer 4.

[Client terminal 2]
The client terminal 2 is a computer including a control unit 21, a storage unit 22, a communication I / F 23, a display device 24, an operation device 25, a drive device 26, and the like. The client terminal 2 is an operation terminal provided in a dispensing room where a pharmacist performs dispensing based on the prescription data, or a ward where a pharmacist provides guidance or confirmation regarding drug administration. Specifically, in the dispensing support system 10, a server client system is configured by the server 1 and the client terminal 2, and the server 1 executes various processes according to user operations of the client terminal 2. . The client terminal 2 may be a mobile terminal such as a smartphone or a tablet terminal.

  The control unit 21 includes control devices such as a CPU, a ROM, a RAM, and an EEPROM (registered trademark). The CPU is a processor that executes various arithmetic processes. 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 a temporary storage memory (working area) for various processes executed by the CPU. And the said control part 21 performs various processes according to the various control programs previously stored in the said ROM, the said EEPROM, or the said memory | storage part 22 using the said CPU.

  The storage unit 22 is a non-volatile storage unit such as a hard disk or an SSD in which various application programs executed by the control unit 21 and various data are stored. Specifically, the storage unit 22 includes a program storage unit 221 in which application programs such as an operating system (OS) and browser software are stored. The browser software displays the various operation screens on the display device 24 by accessing the server 1 via the communication network 5 and performs an input operation on the operation screen using the operation device 25. Application software for transmission to the server 1. Specifically, 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 receives the address information. The server 1 is accessed based on the above.

  The communication I / F 23 performs data communication between the server 1, the dispensing device 3, and the external device such as the printer 4 via the communication network 5 in a wireless or wired manner according to a predetermined communication protocol. A communication interface to be executed.

  The display device 24 is a display unit such as a liquid crystal display or an organic EL display that displays various types of information in accordance with control instructions from the control unit 21. The operation device 25 is an operation unit operated by a user in order to input various information to the client terminal 2. Specifically, the operation device 25 includes a keyboard and a mouse (pointing device) that accept input operations on various operation screens displayed on the display device 24. The operation device 25 may include a touch panel that accepts touch operations on various operation screens displayed on the display device 24, or a voice input device that accepts input of various information by voice recognition.

  The drive device 26 can read the OS or the browser software from a computer-readable recording medium 261 in which an application program such as the OS or the browser software is recorded. 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.

[Server 1]
The server 1 is a computer including a control unit 11, a storage unit 12, a communication I / F 13, a display device 14, an operation device 15, a drive device 16, and the like. The server 1 is provided inside or outside the medical institution where the dispensing support system 10 is used.

  The communication I / F 13 is wirelessly or wired between the client terminal 2, the dispensing device 3, the printer 4, and the external system such as the host system 6 via the communication network 5 according to a predetermined communication protocol. It is an interface for executing data communication.

  The display device 14 is a display unit such as a liquid crystal display or an organic EL display that displays various types of information in accordance with control instructions from the control unit 11. The operation device 15 is an operation unit operated by a user in order to input various kinds of information to the server 1. Specifically, the operation device 15 includes a keyboard and a mouse (pointing device) that accept input operations on various operation screens displayed on the display device 14.

  The operation device 15 may include a touch panel that accepts touch operations on various operation screens displayed on the display device 14 or a voice input device that accepts input of various information by voice recognition.

  The drive device 16 can read various control programs or various information from a computer-readable recording medium 161. The recording medium 161 is a CD, DVD, BD, or USB memory, and the drive device 16 is a CD drive, DVD drive, BD drive, USB port, or the like. In the server 1, the control unit 11 stores the control program read from the recording medium 161 using the drive device 16 in the storage unit 12.

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

  The program storage unit 121 stores the control program for causing the control unit 11 to execute various processes such as a later-described dose data management process (see FIG. 4) and a dose data update process (see FIG. 9). It is a storage area. The program storage unit 121 also stores application programs such as an operating system (OS) and browser software.

  The master storage unit 122 is a storage area for storing various master information such as a medicine master and a patient master. In the medicine master, for each medicine, medicine code, medicine name, medicine classification (classification code), medicine ingredient (component code), JAN code, RSS code, medicine bottle code, dosage form, unit, specific gravity, kind of medicine, compounding Changes, excipients, precautions, etc. are registered in association with each other. The patient master stores a patient code, a patient name, age, sex, pregnancy status, alcohol consumption status, smoking status, disease name, allergy information, and the like for each patient.

  The data storage unit 123 is a storage area for storing prescription check data D1, the prescription data, the correction data, and later-described medication data. FIG. 2 is a diagram showing an example of the prescription check data D1. As shown in FIG. 2, the prescription check data D1 stores one or more check items to be confirmed before dispensing for the prescription data. For example, the prescription check data D1 shown in FIG. 2 includes 20 types of check items including “interaction check” and “dose check”. Further, the prescription check data D1 includes determination conditions predetermined for each check item in order to determine whether or not the content of each check item is appropriate for each medicine included in the prescription data. It is. For example, in the prescription check data D1, information for determining the presence / absence of a problem related to the combination of medicines taken by the patient is defined for the “interaction check”. In addition, in the prescription check data D1, regarding “dose check”, information for determining whether or not the amount of a medicine that a patient takes once or in a day is less than the upper limit amount for each medicine in advance. A predetermined once upper limit amount or a daily upper limit amount is stored.

  The prescription data, the correction data, and the dose data are stored in the data storage unit 123 in association with each patient. The dosing data includes a schedule of each medicine taken by the patient. Specifically, in the dose data, the dose at each dose time on each dose date for each medicine is stored as the dose schedule. The dosing data is generated based on the prescription data input from the host system 6 and is updated based on the correction data input from the host system 6. The medication data is also used as a medication history for each patient.

  FIG. 3 is a diagram showing the dose data D2 which is an example of the dose data. In the dose data D2 shown in FIG. 3, for the drug name "Artist Tablets 20mg", each dose period from "noon on July 23" to "morning on July 27" (after breakfast, after lunch, It is remembered that the dose is 1 tablet after dinner. In addition, for the drug name “ITOLOL Tablet 20 mg”, there is a dose for each dosing period (designation 1, designation 2, designation 3) from “designation 1 on July 23” to “designation 3 on July 26”. The fact that it is one tablet is stored. The designations 1 to 3 are arbitrary timings designated in advance by a doctor. Furthermore, for the drug name “Actos Tablets 30”, Wednesday (7/23), Friday (7/25), Monday (7/23) from “Noon on July 23” to “Morning on July 28” It is stored that the dose is 1 tablet for each dose period of 28) (after breakfast, after lunch, after dinner).

  The control unit 11 includes control devices such as a CPU, a ROM, a RAM, and an EEPROM (registered trademark). The CPU is a processor that executes various arithmetic processes. 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 a temporary storage memory (working area) for various processes executed by the CPU. The control unit 11 includes a system clock for measuring time, and can acquire the current date and time from the system clock.

  The control unit 11 functions as a plurality of processing units by executing various processes according to the control program stored in the ROM, the EEPROM, or the storage unit 12 using the CPU. Specifically, the control unit 11 includes an acquisition processing unit 110, a storage processing unit 111, an update processing unit 112, a display processing unit 113, a prescription check processing unit 114, a dispensing processing unit 115, and the like. Any one or more of the processing units embodied by the control unit 11 may be provided in the control unit 11 as an electronic circuit.

  The acquisition processing unit 110 acquires the prescription data and the correction data from the host system 6 and executes a process for storing the prescription data and the correction data in the data storage unit 123 in association with a patient. . Specifically, the acquisition processing unit 110 acquires the prescription data by receiving the prescription data transmitted from the host system 6 to the server 1 when the prescription data is issued by the host system 6. To do. Further, the acquisition processing unit 110 acquires the correction data by receiving the correction data transmitted from the host system 6 to the server 1 when the correction data is issued by the host system 6. The acquisition processing unit 110 may read the prescription data and the correction data from the storage unit 61 of the host system 6 at a preset timing. Further, the storage processing unit 111 monitors whether or not the prescription data or the correction data is newly stored in the storage unit 61, and the prescription data or the correction data is newly stored in the storage unit 61. In such a case, the prescription data or the correction data may be acquired.

  When the prescription data is acquired by the acquisition processing unit 110, the storage processing unit 111 generates the dosing data including a dosing schedule for each medicine based on the prescription data, and the dosing data is converted into the data. Store in the storage unit 123. In the data storage unit 123, the dose data is stored in association with the patient in the same manner as the prescription data.

  The update processing unit 112, when the correction data is acquired by the acquisition processing unit 110, based on the correction data the dose schedule for each medicine in the dose data stored in the data storage unit 123. Update. In addition, the update processing unit 112 is configured to store the dose stored in the data storage unit 123 in response to a correction operation performed by the user using the operation device 15 of the server 1 or the operation device 25 of the client terminal 2. It is also possible to update the dosage schedule for each medicine in the data. For example, the correction operation includes an operation of recording an arbitrary comment in addition to stopping, interrupting, or extending the dosing schedule for each medicine in the dosing data. As described above, the dispensing support system 10 can arbitrarily modify the dose data separately from the operation for correcting the scheduled dose in the host system 6, and the flexibility of operation in the dispensing support system 10 Will increase.

  If the correction data corresponds to the entire prescription data after correction in the host system 6, all the dose data stored in the data storage unit 123 when the correction data is acquired are all stored. It may be updated. On the other hand, the correction data in the present embodiment is data that can specify only the correction target portion and the correction content of the target portion that are to be corrected in the higher system 6. For example, in the correction data, in addition to the correction contents of the target location, information such as prescription classification, patient name, department, drug name, dose, or usage specifies the target location corresponding to the correction data. Included as data for. Then, the update processing unit 112 executes a partial update process for updating only the data of the target portion of the dose data stored in the data storage unit 123. Therefore, even if the correction data is acquired from the host system 6 after the dosing data has been corrected according to the correction operation by the user, the correction content according to the correction operation by the user is deleted. Will remain. That is, in the dispensing support system 1, the correction data in the dispensing system 1 is reflected in the dose data while synchronizing the dose data stored in the data storage unit 123 with the correction operation in the host system 6. It is possible. In addition, when the correction content according to the said correction operation and the correction content in the correction data are the content regarding the same location, it is possible that either one of the preset data is given priority.

  The display processing unit 113 executes a process for displaying the presence / absence of medication at each medication time based on the medication data stored in the data storage unit 123. In particular, the display processing unit 113 displays a first display mode (see FIG. 5) for displaying the presence / absence of each dose in each dose date for each drug and the dose in each dose date for each drug. It can be executed by switching to the second display mode (see FIG. 6). The display processing unit 113 may be capable of executing only the first display mode.

  The prescription check processing unit 114 performs a prescription check (prescription inspection) for determining the suitability of the prescription data acquired by the acquisition processing unit. Specifically, the prescription check processing unit 114 can determine the suitability of the prescription data based on the prescription data, the dose data, and the prescription check data D1. Therefore, when the dosing data is updated by the update processing unit 112, the suitability of the prescription data is determined based on the updated dosing data. The prescription check is executed, for example, when the server 1 acquires the prescription data from the host system 6, when dispensing is started for the prescription data, or when a prescription check is requested by a user operation. Then, the prescription check processing unit 114 records the check result of the prescription check in the storage unit 12 in association with the prescription data. Thereby, in the said dispensing assistance system 10, it is possible to refer the check result of the said prescription check corresponding to the said prescription data later.

  The dispensing processing unit 115 executes a process for causing the dispensing device 3 to execute the dispensing process based on the prescription data determined to be appropriate by the prescription check processing unit 114. Specifically, the dispensing processing unit 115 generates dispensing data for causing each of the dispensing devices 3 to execute a medicine dispensing process based on the prescription data, and inputs the generated dispensing data to each of the dispensing devices 3. Thus, each of the dispensing devices 3 executes a medicine dispensing process based on the dispensing data. Each of the dispensing devices 3 may actively read out the dispensing data generated by the server 1 and stored in the storage unit 12 to execute the dispensing process.

  By the way, in the hospital, the medicine taking schedule by the patient may be changed according to the judgment of the doctor after the prescription data is issued, and the contents of the change may be input to the host system 6. However, conventionally, the change of the dosing schedule in the host system 6 has not been transmitted to the dispensing support system. For this reason, in the conventional dispensing support system, the administration data that appropriately reflects the change in the administration schedule in the host system 6 has not been managed. On the other hand, in the dispensing support system 10 according to the present embodiment, the medication data can be managed by appropriately reflecting the change of the medication schedule in the host system 6.

[Dosage data management process]
Next, taking data management processing executed by the control unit 11 will be described with reference to FIG. The user operations described below are performed using the operation device 15 of the server 1 or the operation device 25 of the client device 2. Various screens described below are displayed by the display device 24 of the server 1 or the display device 24 of the client device 2.

<Step S11>
In step S11, the control unit 11 determines whether or not a predetermined user operation for displaying the dose data has been performed. For example, the user operation is an operation for displaying a medicine history screen for referring to a medicine history of a patient. The predetermined user operation is performed using the operation device 14 of the server 1 or the operation device 24 of the client device 2. If the predetermined user operation has been performed (S11: Yes), the process proceeds to step S12. If the predetermined user operation has not been performed (S11: No), the process proceeds to step S13. To migrate.

<Step S12>
In step S12, the control unit 11 displays a dose management screen D11 on which the dose data is displayed. Specifically, the control unit 11 reads the dose data of the patient selected by the user operation from the data storage unit 123, and the read dose data of the dose management screen D11 set in advance. Display according to the layout. The dose management screen D11 is displayed on the display device 15 of the server 1 or the display device 25 of the client device 2.

  Here, FIGS. 5 and 6 are diagrams illustrating an example of the dose management screen D11. More specifically, the dose management screen D11 shown in FIG. 5 is a screen corresponding to the first display mode, and the dose management screen D11 shown in FIG. 6 is a screen corresponding to the second display mode. In the server 1 of the dispensing support system 10, the first display mode or the second display mode is selected as the initial management screen in advance by initial setting or the like. And the said control part 11 displays the said medication management screen D11 in the said 1st display mode or the said 2nd display mode selected as the said initial management screen in the said step S12.

  As shown in FIGS. 5 and 6, each of the dose management screens D <b> 11 displays patient information such as a patient ID and a patient name for identifying a patient and the dose data corresponding to the patient. The first display area A11 or the second display area A12 is displayed. Specifically, on the dose management screen D11 corresponding to the first display mode, the presence or absence of each dose time on each dose date for each medicine is displayed in the first display area A11 based on the dose data. The In the dose management screen D12 corresponding to the second display mode, the dose for each medication day is displayed on the second display area A12 based on the dose data.

  The medication management screen D11 displays a display switching key K11 for switching between the first display mode and the second display mode during the display of the medication management screen D11. And the said control part 11 can switch and perform the said 1st display mode and the said 2nd display mode according to operation of the said display switching key K11, and the said 1st display mode in the said administration management screen D11 The display area A11 and the second display area A12 are switched and displayed.

  Here, FIG. 7 shows prescription data D21 as an example of the prescription data, and FIGS. 5 and 6 show taking data D2 generated based on the prescription data D21. In the prescription data D21, the prescription classification is “regular prescription”, and the drug names “Artist tablet 20 mg”, “Itrol roll 20 mg”, and “Actos tablet 30” are included as prescription drugs. The prescription data D21 indicates the usage and dose corresponding to each prescription drug.

  Specifically, for the drug name “Artist Tablets 20 mg”, 3 tablets, one each three times a day after breakfast, after lunch, and after dinner, are prescribed for 4 days from July 23, 2014 (Wednesday) Has been. In addition, for the drug name “ITOLOL Tablets 20 mg”, a total of 3 tablets, 1 tablet each 3 times a day, is prescribed for 4 days from July 23, 2014 (Wednesday) as instructed by the doctor. Furthermore, for the drug name “Actos Tablets 30”, three tablets, one each three times a day after breakfast, lunch and dinner, will be taken on Monday, Wednesday and Friday from July 23, 2014 (Wednesday) Is prescribed for 2 days. Although omitted in FIG. 7, the prescription data D21 includes a code indicating the content of each item, and the control unit 11 recognizes the content of each item of the prescription data based on the code. To do.

  In this way, by displaying the first display area A11 (see FIG. 5) on the dose management screen D11, the user refers to the first display area A11, for example, after lunch on July 23, 7 It is possible to easily confirm whether or not each drug is scheduled to be taken for each dose period until after the breakfast on the 27th of May. In addition, by displaying the second display area A12 (see FIG. 6) on the dose management screen D11, the user refers to the second display area A12, for example, from July 23 to July 27. It is possible to easily confirm the dose of each medicine for each dose day. That is, the user refers to the first display area A11 when confirming the presence / absence of taking medicine at each time of taking, and the second display area A12 when confirming the dose of medicine on each taking day. It is possible to refer to it.

<Step S13>
In step S13, the control unit 11 determines whether or not the prescription data has been received. Specifically, the control unit 11 has a prescription category of data acquired by the acquisition processing unit 110 in a category corresponding to a predetermined new prescription such as “regular prescription”, “outpatient”, and “temporary”. When certain data is received, it is determined that the prescription data has been received. In the correction data, the prescription category is a category corresponding to a corrected prescription such as “dosage stop”, “dosage stop”, or “dosage change”. Here, if the said control part 11 judges that the said prescription data was received (S13: Yes), it will transfer a process to step S131, and if it judges that the said prescription data is not received (S13: No), a process will be carried out. To step S14.

<Step S131>
In step S131, the control unit 11 generates the dose data based on the prescription data determined to have been received in step S13, and executes a process for storing the dose data in the data storage unit 123. To do. Such processing is executed by the storage processing unit 111 of the control unit 11.

  Specifically, for the drug data included in the prescription data, the control unit 11 includes the same patient name and drug name data in the medication data already stored in the data storage unit 123. Integrate each data. For example, consider the case where the prescription data D22 shown in FIG. 8 is input after the prescription data D21 is input to the dispensing support system 10. In this case, since the data of the medicine name “Artist Tablet 20 mg” in the prescription data D21 is already stored in the data storage unit 123 as the dose data, the medicine name in the prescription data D22 input later The data of “Artist Tablet 20 mg” is integrated with the dose data. Specifically, in the taking data, the drug name “Artist Tablet 20 mg” is updated to take 2 tablets three times a day in the morning, lunch and dinner.

  On the other hand, when the data of the medicine included in the prescription data does not exist in the medication data already stored in the data storage unit 123, the control unit 11 has the same data as the patient name and the medicine name. Data is newly added to the dose data in the data storage unit 123. In addition, when the control unit 11 determines the presence / absence of the integration, it is determined whether or not to determine the coincidence of one or a plurality of departments, usages, and doses in addition to the patient name and the drug name. It is also conceivable that it can be set in advance according to the user operation.

  In the prescription data D21, the usage of the drug with the drug name “Aitrol Tablet 20 mg” is “as instructed by the doctor”, and the number of doses after noon on Wednesday, July 23, 2014 is unknown. Therefore, when the prescription data D21 is input, the control unit 11 in FIG. 3 shows the medicine name “Itrol roll 20 mg” based on the prescription data D21 in step S131. As shown, the data for four days from instruction 1 on July 23, 2014 (Wednesday) to instruction 3 on July 26, 2014 is registered as the dose data.

  By the way, in the said dispensing assistance system 10, the dosing time which shows the dosing timing which takes a chemical | medical agent is managed at time, such as after breakfast, after lunch, and after dinner. On the other hand, depending on the host system 6, the dosing time may be indicated by time in the prescription data. Therefore, it can be considered that the control unit 11 converts the dosing time represented by the time in the prescription data into the dosing time represented by the time. For example, when the correspondence relationship between time and time is set in advance and the dosing time is displayed as a time such as 8 o'clock, 12 o'clock, or 18 o'clock in the prescription data, it is expressed by those times The dosing time is converted into the dosing time expressed in each time after breakfast, after lunch and after dinner. Further, in the case where the dispensing support system 10 manages the taking time by time, and the taking time is indicated by the time in the prescription data, the control unit 11 is expressed by the time in the prescription data. It is conceivable to convert the taking time to the taking time expressed in time. This point is the same not only for the prescription data but also for the correction data.

<Step S14>
In step S14, the control unit 11 determines whether or not the correction data has been received. Specifically, the control unit 11 is configured such that the prescription classification of the data acquired by the acquisition processing unit 110 corresponds to a predetermined correction prescription such as “dosing cancellation”, “dosing interruption”, and “deletion”. It is determined that the correction data has been received when the data is received. If the control unit 11 determines that the correction data has been received (S14: Yes), the process proceeds to step S15. If the control unit 11 determines that the correction data has not been received (S14: No), the process Is returned to step S11.

<Step S15>
In step S <b> 15, the control unit 11 performs a dose data update process for updating the dose data stored in the data storage unit 123 based on the correction data.

[Dosage data update processing]
Here, an example of the dose data update process executed by the control unit 11 will be described with reference to FIG. Such processing is executed by the update processing unit 112 of the control unit 11. Hereinafter, the case where the dose data D2 (see FIG. 3) is stored in the data storage unit 123 and the dose data D2 is updated based on the correction data will be described as an example.

<Step S21>
In step S <b> 21, the control unit 11 determines whether or not the correction content indicated in the correction data is to stop taking. Here, if the said control part 11 judges that the said correction content is cancellation of taking (S21: Yes), it will transfer a process to step S211 and will judge that the said correction content is not cancellation of taking (S21: No) ), The process proceeds to step S22.

  Specifically, the control unit 11 determines that the correction content is a stop of taking when the prescription classification of the correction data is “dosing stop”. FIG. 10A is a diagram showing correction data D31 that is an example of the correction data. In the correction data D31, the prescription category is “Cancel dose”, the drug name is “Artist tablet 20 mg” as information for specifying the drug to be corrected by the correction data D31, and the usage and dose are It is shown that “3 tablets in total, 3 times a day after morning, lunch and dinner, for 4 days from July 23, 2014 (Wednesday)”. Although omitted in FIG. 10A, the correction data D31 includes information such as a medical department when the medicine is prescribed. The correction data D31 includes information indicating that the medicine name “Artist Tablets 20 mg” is to be stopped from “noon on Friday, July 25, 2014”.

<Step S211>
In step S <b> 211, the control unit 11 executes a process for changing the dosing at the dosing time specified by the correction data among the medicine taking schedules included in the dosing data to stop.

  Here, for the medicine included in the correction data, the control unit 11 executes a preset error notification process or the like when data having the same patient name and medicine name does not exist in the medication data, The taking data update process is terminated. On the other hand, regarding the drug data included in the correction data, the control unit 11 reflects the content of the correction data in the dosing data when data having the same patient name and drug name exists in the dosing data. To update the dose data. In addition, when the control unit 11 determines the presence or absence of the update, it can be set in advance according to a user operation whether or not to determine the coincidence of any one or a plurality of departments, usages, and doses. It is also possible. In addition, the determination of the presence / absence of the update is performed in the same manner at the time of executing another update process in step S23 or S221 described later.

  FIG. 10B is a diagram showing a display example of the first display area A11 of the dose management screen D11 as an update result of the dose data D2 when the correction data D31 (see FIG. 10A) is input. is there. When the correction data D31 is input, in step S211, the control unit 11 determines, based on the correction data D31, the medicine name “Artist Tablet 20 mg” in the dose data D2 on July 25, 2014. Register information to stop taking the drug from noon on Friday.

  More specifically, the control unit 11 sets the dose from noon on July 25 to the morning on July 27 of the drug name “Artist Tablets 20 mg” in the dose data D2 (see FIG. 3). To "0". In the present embodiment, “1” is indicated as “taken” in the dose data, and “0” and “blank” are indicated as “not taken”. Therefore, in the above-mentioned dose data, it is possible to identify that the dose time that is “0” out of the dose times has become non-dose due to the suspension or interruption of the dose. In addition, all dosing periods without taking may be “0” or “blank”.

  Thus, when the medication data D2 is displayed in the first display area A11 of the medication management screen D11 after the correction data D31 is input, as shown in FIG. 10B, the medicine name “Artist” “Tablet 20 mg” is displayed as “Cancel” at noon on July 25, and the fact that it is not taken is displayed by a blank until the morning of July 27 thereafter.

  Moreover, the said control part 11 can display the update location or the update content in the said medication management screen D11, when the said medication data are updated by the said correction data. Specifically, the display column for the daytime of July 25, which is the stop start time specified by the correction data D31, can be distinguished from other display columns by a specific color such as yellow with a preset background color. Displayed in various ways. When the cursor is positioned in the display column displayed in the specific color, the control unit 11 displays the content of the correction data D31 corresponding to the display column on a pop-up screen or the like. It should be noted that not only the display column for the day of July 25, which is the stop start time specified by the correction data D31, but all display columns updated by the correction data D31 can be identified by the specific color or the like. May be displayed.

  FIG. 11A is a diagram showing correction data D32, which is another example of the correction data different from the correction data D31. FIG. 11B is a diagram showing a display example of the first display area A11 of the dose management screen D11 as an update result of the dose data D2 when the correction data D32 is input. As shown in FIG. 11A, in the corrected data D32, the prescription category is “discontinuation”, and the medication of the medicine name “ITOLOL Tablet 20 mg” is “Friday July 25, 2014”. Information to stop from "noon" is included. However, the usage of the medicine is “as instructed by the doctor” and the number of doses after noon on Friday, July 25, 2014 is unknown. Therefore, when the correction data D32 is input, the control unit 11 determines, in step S211, the medicine name “Itrol roll 20 mg” in the dose data D2 based on the correction data D32. Information indicating that dosing is to be stopped is registered from instruction 1 on July 26, 2014, which is the day after Friday, July 25. More specifically, the control unit 11 takes the dose from the instruction 1 on July 26 to the instruction 3 on July 26 of the drug name “Itrol tablet 20 mg” in the dose data D2 (see FIG. 3). Is changed from “1” to “0”.

  Thus, when the medication data D2 is displayed in the first display area A11 of the medication management screen D11 after the correction data D32 is input, as shown in FIG. “Cancel” is displayed in the instruction 1 on July 26 of “Troll Tablet 20 mg”, and the fact that it is not taken is displayed by a blank until the evening of July 26. Further, as described above, the display column of the instruction 1 on July 26, which is the stop start time specified by the correction data D32, is displayed in a manner distinguishable from the other display columns with the specific color, as described above. The contents of the correction data D32 are displayed by selecting a column.

<Step S22>
In step S <b> 22, the control unit 11 determines whether or not the correction content of the dosing data D <b> 2 indicated in the correction data is a dosing interruption. Here, if the said control part 11 judges that the said correction content is interruption of taking (S22: Yes), it will transfer a process to step S23, and if it judges that the said correction content is not interruption of taking (S22: No) ), The process proceeds to step S221.

  Specifically, the control unit 11 determines that the correction content is a dosing interruption when the prescription classification of the correction data is “dosing interruption”. FIG. 12A is a diagram showing correction data D33 which is an example of the correction data. In the correction data D33, the prescription category is “Suspension”, the drug name is “Artist Tablet 20 mg” as information for specifying the drug to be corrected by the correction data D33, and the usage and dose are It is shown that “3 tablets in total, 3 times a day after morning, lunch and dinner, for 4 days from July 23, 2014 (Wednesday)”. The correction data D33 includes information indicating that the medicine name “Artist Tablets 20 mg” will be stopped in the afternoon and evening of July 25, 2014 (Friday).

<Step S221>
If the correction content indicated by the correction data is not suspension or interruption of taking, in the subsequent step S221, the control unit 11 performs a process for updating the dose data D2 according to the correction content of the correction data. Run. For example, when the correction data is data indicating that the data of a specific medicine in the medication data is to be deleted in units of medicine, the data of the specific medicine is deleted from the medication data. In addition, even when the correction data is data indicating that the data of a specific medicine in the dosage data is deleted in a recipe (usage) unit, the data of the specific medicine is deleted from the dosage data. As described above, also in step S221, the presence / absence of the update is determined in the same manner as in step S211.

<Step S23>
In step S <b> 23, the control unit 11 executes a process for changing the dosing at the dosing time specified by the correction data out of the medicine taking schedule included in the dosing data. As described above, also in step S23, the presence / absence of the update is determined in the same manner as in step S211.

  FIG. 12A is a diagram showing correction data D33 which is an example of the correction data. FIG. 12B is a diagram illustrating a display example of the first display area A11 of the dose management screen D11 as an update result of the dose data D2 when the correction data D33 is input. As shown in FIG. 12A, in the correction data D33, the prescription category is “medication interruption”, and the drug name is “artist” as information for specifying the drug to be corrected by the correction data D33. 20 mg "and the dosage and usage are" 3 tablets, 3 times a day after morning, noon, and dinner, a total of 3 tablets for 4 days from Wednesday, July 23, 2014 " Has been. The correction data D33 includes information indicating that the taking of the drug name “Artist Tablets 20 mg” in the afternoon and evening of July 25, 2014 (Friday) will be interrupted.

  When the correction data D33 is input, in step S23, the control unit 11 determines the medicine name “Artist Tablet 20 mg” in the dose data D2 in July 2014 based on the correction data D33. Register information to stop taking the afternoon and evening on the 25th (Friday). More specifically, the control unit 11 changes the dose from “1” to “0” on the day and night of July 25 of the drug name “Artist Tablets 20 mg” in the dose data D2 (see FIG. 3). change.

  Thus, when the medication data D2 is displayed in the first display area A11 of the medication management screen D11 after the correction data D33 is input, as shown in FIG. “Tablet 20 mg” is displayed as “interrupted” at noon and evening on July 25. In addition, as described above, the display column for the day and evening of July 25, which is the interruption target specified by the correction data D33, is displayed in a manner distinguishable from the other display columns with the specific color, as described above. The contents of the correction data D33 are displayed by selecting the column.

<Step S24>
In step S <b> 24, the control unit 11 determines whether or not an extension of taking is included in the correction content indicated in the correction data. Specifically, the control unit 11 determines that the amendment includes an extension of taking when the prescription classification of the correction data is “dosing interruption” and an extension comment is included in the correction data. If the control unit 11 determines that the extension of the dose is included in the correction content (S24: Yes), the control unit 11 shifts the process to step S25 and determines that the extension of the correction is not included in the correction content. (S24: No), the dose data update process is terminated.

<Step S25>
In step S <b> 25, the control unit 11 executes a process for extending the dosing at the dosing time specified by the correction data in the medicine dosing schedule included in the dosing data D <b> 2.

  FIG. 13A is a diagram showing correction data D34 that is an example of the correction data. FIG. 13B is a diagram illustrating a display example of the first display area A11 of the dose management screen D11 as an update result of the dose data D2 when the correction data D34 is input. As shown in FIG. 13A, the correction data D34 includes, in addition to the correction data D33, an extended comment indicating that the medicine is to be extended until the evening of Sunday, July 27, 2014. ing. Therefore, when the correction data D34 is input, the control unit 11 determines whether the medicine name “Artist Tablets 20 mg” in the dose data D2 is included in 2014 based on the correction data D34 in the step S25. Register information to extend the dose until the evening of July 27 (Sunday). More specifically, the control unit 11 sets the dose of the medicine name “Artist Tablets 20 mg” in the noon on July 27 and the evening on July 27 in the dosing data D2 (see FIG. 3) to “1”. Set to.

  Thus, when the medication data D2 is displayed in the first display area A11 of the medication management screen D11 after the correction data D34 is input, as shown in FIG. 13B, the medicine name “Artist” “O” indicating that there is a dose is displayed in the display column of July 20th at noon and July 27th evening of “20 mg tablet”. In addition, the display columns for the day of July 27 and the evening of July 27, which are the extension targets specified by the correction data D34, are distinguishable from the other display columns in the specific color as described above. The content of the correction data D34 is displayed by selecting the display field.

  FIG. 14A is a diagram showing correction data D35, which is another example of the correction data different from the correction data D34. FIG. 14B is a diagram illustrating a display example of the first display area A11 of the dose management screen D11 as an update result of the dose data D2 when the previous correction data D35 is input. As shown in FIG. 14A, in the correction data D35, the drug name is “ACTOS tablet 30” as the information for specifying the drug to be corrected by the correction data D35. 3 tablets a day, 3 times a day after morning / noon / dinner, 2 tablets from July 23rd (Wednesday) 2014, “Monday / Wednesday / Friday” Yes. The correction data D35 includes information indicating that the taking of the drug name “Actos Tablets 30” in the morning, noon, and evening on Friday, July 25, 2014 is interrupted. Further, the correction data D35 includes information indicating that the medication name “ACTOS Tablet 30” will be extended until the morning of Wednesday, July 30, 2014.

  When the correction data D35 is input, in step S23, the control unit 11 determines the medicine name “Actos Tablets 30” in the dose data D2 in July 2014 based on the correction data D35. Register the information to stop taking the morning, noon and evening on the 25th (Friday). In step S25, the control unit 11 extends the medication name “Actos Tablets 30” of the medication data D2 based on the correction data D35 until the morning of Wednesday, July 30, 2014. Register the information to do so. More specifically, the control unit 11 determines the dose of the medicine name “ACTOS Tablet 30” in the noon, evening and July 30 morning of the drug name “ACTOS Tablet 30” in the dosage data D2 (see FIG. 3). Set to “1”.

  Accordingly, when the medication data D2 is displayed in the first display area A11 of the medication management screen D11 after the correction data D35 is input, as shown in FIG. 14B, the medicine name “ACTOS” is displayed. After the breakfast on Lunch 30 on July 25, after lunch, and after dinner, “Suspended” is displayed. After lunch on Monday, July 28, after dinner, the morning display column on Wednesday, July 30 “○” indicating that there is a dose is displayed.

  By the way, in the upper system 6, when the correction time taken for correction by the correction data is more than two days, as shown in FIG. 15A, correction data D36 and D37 corresponding to each dose date are issued. Sometimes. For example, in the example shown in FIG. 15A, the correction data D36 includes information indicating that the medication is suspended for the medication time of “Artist Tablets 20 mg” on the day of July 25th (Friday). On the other hand, the correction data D37 includes information indicating that the medication is interrupted for the medication time of July 26 (Saturday) of the drug name “Artist Tablet 20 mg”.

  In this case, the control unit 11 executes a process for correcting the dose data D2 based on the correction data D36 and D37. Specifically, when the correction data D36 and D37 are input, taking the drug name “Artist Tablets 20 mg” on July 25 (Friday) noon based on the correction data D36. The information to the effect is registered, and the information to interrupt the dosing is registered for the noon time of July 26th (Saturday) of the drug name “Artist Tablet 20 mg” based on the correction data D37.

  Furthermore, even when the dose to be corrected by the correction data is over two days and the extension of the dose is performed, as shown in FIG. 16A, the correction data D38 corresponding to each dose date, D39 may be issued. In the example shown in FIG. 16A, in the correction data D38, in addition to the correction data D36, the medicine name “Artist Tablets 20 mg” is to be extended until the evening of July 27 (Sunday). Contains information. In addition to the correction data D37, the correction data D39 also includes information indicating that the medicine name “Artist Tablet 20 mg” is to be extended until the evening of July 27 (Sunday). .

  In this case, the control unit 11 executes a process for correcting the dose data D2 based on the correction data D38 and D39. FIG. 17A and FIG. 17B are diagrams showing an example of a process in which the drug name “Artist Tablet 20 mg” in the dose data D2 is corrected based on the correction data D38 and D39. Here, it is assumed that the control unit 11 stores the last dose time for each medicine specified by the prescription data in the data storage unit 123 in association with the dose data.

  When the correction data D38 and D39 are received in this order, the control unit 11 first, based on the correction data D38, as shown in FIG. 17A, the drug name “Artist Tablet 20 mg”, July 25 (Friday) The dose corresponding to the daytime dose is changed from “1” to “0”, and information indicating that the dose is interrupted is registered. In addition, the control unit 11 specifies a dosing time set to be taken after the morning of July 27 (Sunday), which is the final taking time of the drug name “Artist Tablet 20 mg”. Then, the control unit 11 registers information indicating that the dose corresponding to the specified dose time is changed to “1” and the dose is added. Here, since the daytime for taking the day on July 27 (Sunday) is set to no taking, the dose corresponding to the daytime for taking the day on July 27 (Sunday) is changed to “1”. The

  Subsequently, based on the correction data D39, the control unit 11, as shown in FIG. 17B, takes the dose corresponding to the daytime of taking the medicine name “Artist Tablets 20mg” on Saturday, July 26th. Is changed from “1” to “0”, and information indicating that taking is interrupted is registered. Further, the control unit 11 is set to take no medication after noon on July 27 (Sunday), which is the final take time of the extension indicated by the correction data D38 of the drug name “Artist Tablet 20 mg”. Identify when you are taking. Then, the control unit 11 registers information indicating that the dose corresponding to the specified dose time is changed to “1” and the dose is added. Here, since the evening dose on July 27 (Sunday) is set to no taking, the dose corresponding to the evening dose on July 27 (Sunday) is changed to “1”. The

  As described above, the dosing data D2 is updated based on the correction data D38 and D39, so that when the correction data D39 and D38 are received in this order, or the final dosing time specified by the prescription data is determined. Even if the control unit 11 has been canceled or interrupted before, the control unit 11 can correct the dose data D2 correctly based on the correction data D38 and D39.

  18A and 18B show another example of the process in which the correction data D38 and D39 are corrected based on the correction data D38 and D39. FIG. Here, the said control part 11 does not need to memorize | store the last taking time for every chemical | medical agent in the said data storage part 123 in association with the said taking data.

  First, as shown in FIG. 18A, the control unit 11 sets the dose corresponding to the daytime of taking the drug name “Artist Tablets 20 mg” on July 25 (Friday) based on the correction data D38. Change the information from “1” to “0” and register information to stop taking. In addition, the control unit 11 may take the medicine retrospectively from the evening taking time of Sunday, July 27, which is the final taking time of the extension indicated by the modified data D38 of the drug name “Artist Tablet 20 mg”. Identify when the dose is set to none. Then, the control unit 11 registers information indicating that the dose corresponding to the specified dose time is changed to “1” and the dose is added. Here, since the evening dose on July 27 (Sunday) is set to no taking, the dose corresponding to the evening dose on July 27 (Sunday) is changed to “1”. The

  Subsequently, based on the correction data D39, the control unit 11, as shown in FIG. 18B, takes the dose corresponding to the daytime of taking the medicine name “Artist Tablets 20mg” on Saturday, July 26th. Is changed from “1” to “0”, and information indicating that taking is interrupted is registered. In addition, the control unit 11 may take the medicine retrospectively from the evening taking time of Sunday, July 27, which is the final taking time of the extension indicated by the modified data D38 of the drug name “Artist Tablet 20 mg”. Identify when the dose is set to none. Then, the control unit 11 registers information indicating that the dose corresponding to the specified dose time is changed to “1” and the dose is added. Here, since the daytime for taking the day on July 27 (Sunday) is set to no taking, the dose corresponding to the daytime for taking the day on July 27 (Sunday) is changed to “1”. The

  As described above, the dosing data D2 is updated based on the correction data D38 and D39, so that when the correction data D39 and D38 are received in this order, or the final dosing time specified by the prescription data is determined. Even if the control unit 11 has been canceled or interrupted before, the control unit 11 can correct the dose data D2 correctly based on the correction data D38 and D39.

1: Server 11: Control unit 12: Storage unit 13: Communication I / F
14: Operation device 15: Display device 16: Drive device 2: Client terminal 21: Control unit 22: Storage unit 23: Communication I / F
24: Operating device 25: Display device 26: Drive device 3: Dispensing device 4: Printer 5: Communication network 6: Host system 10: Dispensing support system

Claims (10)

An acquisition processing unit for acquiring prescription data indicating the prescription content of the drug and correction data indicating the correction content of the drug scheduled to be taken from the host system;
A storage processing unit that stores, in a storage unit, dosing data including a dosing schedule for each medicine based on the prescription data acquired by the acquisition processing unit;
An update processing unit that updates a dosing schedule for each medicine in the dosing data stored in the storage unit based on the correction data acquired by the acquisition processing unit;
Dispensing support system comprising   The dispensing support system according to claim 1, wherein the content of the correction includes at least one of cancellation, interruption, and extension of taking the medicine at the time of taking the medicine.   The dispensing support system according to claim 1 or 2, further comprising a display processing unit capable of displaying the presence / absence of medication at each medication time based on the medication data stored in the storage unit.   The display processing unit switches between a first display mode for displaying the presence / absence of each dose in each dose date for each drug and a second display mode for displaying the dose in each dose date for each drug. The dispensing support system according to claim 3, which is executable.   The storage processing unit integrates each of the drug data when the drug data included in the prescription data includes at least drug data with the same patient name and drug name in the medication data. 4. The dispensing support system according to any one of 4 above.   The update processing unit reflects the content of the correction data in the medication data when the medication data included in the correction data includes at least medication data with the same patient name and medication name in the medication data. The dispensing support system according to any one of claims 1 to 5, wherein the medication data is updated.   The storage processing unit or the update processing unit is capable of converting a dose time expressed by one of time or time in the prescription data or the correction data into a dose time expressed by the other. Dispensing support system described in Crab.   The dispensing according to any one of claims 1 to 7, further comprising a prescription check processing unit that determines whether or not the prescription data acquired by the acquisition processing unit is appropriate based on the dosing data stored in the storage processing unit. Support system. One or a plurality of dispensing devices capable of performing a medicine dispensing process;
A dispensing processing unit that causes the dispensing device to execute the dispensing process based on the prescription data determined to be appropriate by the prescription check processing unit,
The dispensing support system according to any one of claims 1 to 8, further comprising: The correction data is data that can specify only the target portion of the correction to be taken and the correction content of the target portion performed in the host system,
The said update process part is a dispensing assistance system in any one of Claims 1-9 which updates only the data of the said target location among the said medication data memorize | stored in the said memory | storage part.