Medication history management apparatus, medication history management system, medication history management method, and medication history management program

Abstract

To provide a medication history management apparatus with which a highly accurate medication history is registered and utilized.SOLUTION: A server includes a communication unit, a storage unit, and a control unit. The communication unit receives, from a patient terminal, which is a terminal of a patient, a drug image which is an image of drugs captured when the patient takes them. The storge unit stores the drug image received by the communication unit in association with patient identification information identifying the patient, the date of medication, and the time of medication. The control unit reads, from the storage unit, in accordance with a request from a health worker terminal which is a terminal of a dispensing pharmacy or a hospital, medication history data in which the drug image, the date of medication and the time of medication are associated with each other, corresponding to the patient identification information received from the health worker terminal, transmits the data to the health worker terminal, and displays a medication history screen in which the drug image, the date of medication and the time of medication are associated, on the health worker terminal.SELECTED DRAWING: Figure 5

Description

Technical Field

[0001] The present invention mainly relates to a medication history management device for registering a medication history.

Background Art

[0002] Patent Document 1 discloses a method for continuously storing a patient's medication status. This method is realized using an application installed on a mobile terminal. When the time set as the medication time of the drug arrives, the mobile terminal displays a screen for registering the medication history on the display. Buttons for selecting whether or not the drug has been taken are displayed on this screen. By the patient operating this button, the medication history is transmitted to the server.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the method of Patent Document 1, registration errors in the medication history are likely to occur. For example, even if the patient thinks they have taken all the drugs, they may actually have forgotten to take one drug. In this case, a medication history different from the actual one will be registered. Also, when the screen for registering the medication history is displayed on the mobile terminal, the patient may operate the button indicating that they have taken the drug without checking the display content. Even in this case, there is a possibility that a medication history different from the actual one will be registered. Therefore, the method of Patent Document 1 has room for improvement from the perspective of the accuracy of the medication history.

[0005] The present invention has been made in view of the above circumstances, and its main object is to provide a medication history management device in which a highly accurate medication history is registered and utilized. Means for solving problems and effects

[0006] The problems to be solved by the present invention are as described above. Next, the means for solving these problems and their effects will be described.

[0007] According to a first aspect of the present invention, there is provided a medication history management device having the following configuration. That is, the medication history management device includes a communication unit, a storage unit, and a control unit. The communication unit receives a medication image, which is an image of a drug taken by a patient at the time of taking the drug, from a patient terminal, which is a terminal of the patient. The storage unit stores the medication image received by the communication unit in association with patient identification information for identifying the patient, the date of administration, and the time of administration. The control unit, in response to a request from a medical staff terminal, which is a terminal of a dispensing pharmacy or a hospital, reads out from the storage unit the medication history data associating the medication image, the date of administration, and the time of administration corresponding to the patient identification information received from the medical staff terminal, and transmits the data to the medical staff terminal, and performs a process of displaying on the medical staff terminal a medication history screen associating the medication image, the date of administration, and the time of administration.

[0008] Thereby, by managing the medication history using the medication image, it is less likely that a registration error in the medication history occurs due to a patient's misrecognition or carelessness. As a result, a highly accurate medication history can be registered. In addition, by providing the information received from the patient terminal to the medical staff terminal, the medical staff can provide medication guidance using the highly accurate medication history.

[0009] In the above-described medication history management device, it is preferable to have the following configuration. That is, the medication history screen is a tabular screen in which areas are divided using the date of administration and the time of administration. In each area of the medication history screen, the medication image corresponding to the date of administration and the time of administration is displayed.

[0010] This enables medical staff to quickly grasp the patient's medication history at a glance.

[0011] In the above-mentioned medication history management device, the following configuration is preferably adopted. That is, the control unit analyzes the administered drug image to identify the type and quantity of the drug contained in the administered drug image. The control unit identifies the type and quantity of the drug for each administration date and time based on the patient's prescription data. The control unit collates whether the type and quantity of the drug contained in the administered drug image match the type and quantity of the drug identified based on the prescription data, and stores the collation result.

[0012] This enables the system to verify whether the medication is correct. Therefore, the labor required for medical staff to verify can be reduced.

[0013] In the above-mentioned medication history management device, the following configuration is preferably adopted. That is, the medication history screen is a tabular screen divided into areas by the administration date and time. The collation result corresponding to the administration date and time is displayed in each area of the medication history screen.

[0014] This enables medical staff to quickly grasp whether the medication is correct at a glance.

[0015] In the above-mentioned medication history management device, it is preferable that the collation result and the administered drug image corresponding to the administration date and time are displayed in each area of the medication history screen.

[0016] This enables medical staff to easily check whether the medication verification result is correct.

[0017] In the above-mentioned medication history management device, it is preferable that the control unit determines whether single-packaging is recommended based on the collation result and stores the determination result.

[0018] This enables medical staff to obtain reference information on whether to recommend single packaging by accessing the determination result.

[0019] In the above medication history management device, it is preferable that the control unit analyzes the tendency of medication errors based on the collation result and stores the analysis result.

[0020] This enables medical staff to speculate on the reasons why medication errors are likely to occur or give advice to make it less likely for medication errors to occur by accessing the analysis result.

[0021] According to a second aspect of the present invention, the following medication history management system is provided. That is, the above medication history management system includes a medication history management device, a patient terminal, and a medical staff terminal.

[0022] According to a third aspect of the present invention, the following medication history management method is provided. That is, the medication history management method includes a reception step, a storage step, and a display step. In the reception step, a medication image taken by a patient at the time of taking the medicine, which is a medication image, is received from a patient terminal, which is the terminal of the patient. In the storage step, the medication image received in the reception step is stored in a storage unit in association with patient identification information for identifying the patient, the medication date, and the time of taking the medicine. In the display step, in response to a request from a medical staff terminal, which is a terminal of a dispensing pharmacy or a hospital, the medication history data associating the medication image, the medication date, and the time of taking the medicine corresponding to the patient identification information received from the medical staff terminal is read out from the storage unit and transmitted to the medical staff terminal, and a medication history screen associating the medication image, the medication date, and the time of taking the medicine is displayed on the medical staff terminal.

[0023] According to a fourth aspect of the present invention, there is provided a medication history management program for causing a computer to execute the following processes. That is, the medication history management program includes a reception step, a storage step, and a display step. In the reception step, a medication image taken by a patient at the time of taking the medicine, which is a medication image, is received from a patient terminal, which is the terminal of the patient. In the storage step, the medication image received in the reception step is stored in a storage unit in association with patient identification information for identifying the patient, the date of taking the medicine, and the time of taking the medicine. In the display step, in response to a request from a medical staff terminal, which is a terminal of a dispensing pharmacy or a hospital, the medication history data associating the medication image, the date of taking the medicine, and the time of taking the medicine corresponding to the patient identification information received from the medical staff terminal is read out from the storage unit and transmitted to the medical staff terminal, and a medication history screen associating the medication image, the date of taking the medicine, and the time of taking the medicine is displayed on the medical staff terminal.

Brief Description of the Drawings

[0024]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Modes for Carrying Out the Invention

[0025] Next, embodiments of the present invention will be described with reference to the drawings.

[0026] The medication history management system 1 shown in Fig. 1 is a system for registering a patient's medication history. The registered medication history is shared between the patient and medical staff. Medical staff can provide medication guidance according to the medication history by referring to the medication history registered in the system.

[0027] In this specification, "medical staff" refers to those engaged in medical practice, and more specifically, those who provide medication guidance. Specifically, medical staff refers to doctors or pharmacists. The "medications" targeted by the medication history management system 1 are prescription drugs prescribed at a dispensing pharmacy or hospital based on a prescription, and dosage forms include tablets, capsules, powders, etc. "Medication history" refers to the type and quantity of medications taken on the date of administration and at the time of administration. "Time of administration" refers to the timing of taking medications within a day, such as morning, noon, evening, before meals, after meals, etc.

[0028] As shown in Fig. 1, the medication history management system 1 includes a patient terminal 10, a medical staff terminal 20, and a server (medication history management device) 30.

[0029] The patient terminal 10 is a mobile terminal owned by the patient, such as a smartphone or a tablet terminal. The patient terminal 10 includes a control unit 11, a storage unit 12, a communication unit 13, an operation unit 14, a display unit 15, and an imaging unit 16.

[0030] The medical staff terminal 20 is a terminal provided at a dispensing pharmacy or hospital and operated by medical staff. The medical staff terminal 20 is, for example, a notebook computer or a desktop computer. Note that the medical staff terminal 20 may be a mobile terminal. The medical staff terminal 20 includes a control unit 21, a storage unit 22, a communication unit 23, an operation unit 24, and a display unit 25.

[0031] Server 30 is a device provided in the cloud. The cloud can be accessed via the Internet from a terminal on the user side (patient terminal 10 or medical staff terminal 20). In this embodiment, server 30 is provided at a location separate from the dispensing pharmacy or hospital, and provides services to a plurality of dispensing pharmacies or hospitals. Note that this is just an example, and server 30 may be provided in a dispensing pharmacy or hospital. Also, at least a part of the processing performed by server 30 (details will be described later) may be performed by patient terminal 10 or medical staff terminal 20. Server 30 includes a control unit 31, a storage unit 32, a communication unit 33, an operation unit 34, and a display unit 35. Note that operation unit 34 and display unit 35 are not essential components of server 30 and can be omitted.

[0032] Since patient terminal 10, medical staff terminal 20, and server 30 each include a control unit 11, 21, 31, a storage unit 12, 22, 32, a communication unit 13, 23, 33, an operation unit 14, 24, 34, and a display unit 15, 25, 35, they will be described together below. Control units 11, 21, 31 are arithmetic devices such as a CPU. Storage units 12, 22, 32 are SSDs, HDDs, flash memories, or the like. The storage units 12, 22, 32 store data used for control, registered or input data, programs, and the like. Communication units 13, 23, 33 are, for example, wired communication modules or wireless communication modules. Communication units 13, 23, 33 can communicate with other devices via the Internet. Operation units 14, 24, 34 are, for example, touch panels or hardware keys. Operation units 14, 24, 34 receive operations from patients or medical staff, etc., and output signals corresponding to the operations performed by patients or medical staff, etc. to control units 11, 21, 31. Display units 15, 25, 35 are, for example, liquid crystal displays or organic EL displays. Display units 15, 25, 35 can display screens created by the control units 11, 21, 31 of the own device or other devices. Imaging unit 16 is, for example, a camera module. Imaging unit 16 captures an object and creates an image of the object. Note that patient terminal 10, medical staff terminal 20, and server 30 are all a type of computer.

[0033] Next, with reference to FIGS. 2 and 3, the processes performed by the patient terminal 10 and the server 30 in the registration stage of the medication history will be described. In the medication history management system 1 of the present embodiment, the medication history is registered using an image of the administered drug. The "image of the administered drug" is an image of the drug taken by the patient at the time of taking the drug.

[0034] An application for using the medication history management system 1 is installed in the patient terminal 10. Note that instead of the application, a similar function may be realized based on a browser. Prescription data is registered in the application. The prescription data may be obtained from another application (for example, a medicine management application), may be manually input by the patient, or may be received from a hospital or the like as electronic data.

[0035] When the control unit 11 of the patient terminal 10 determines that the medication timing has arrived based on the prescription data, it causes the display unit 15 to display the medication guidance screen 40 shown in FIG. 3 (sequence number S1). Note that the process of determining the medication timing based on the prescription data is an example, and it may be determined that the medication timing has arrived based on the time set in advance by the patient or based on a notification from the server 30. Alternatively, when the patient starts the application and performs a predetermined operation, the control unit 11 of the patient terminal 10 may cause the display unit 15 to display the medication guidance screen 40.

[0036] On the medication guidance screen 40 shown in FIG. 3, a date and time display area 41, a message display area 42, a drug display area 43, and a camera activation button 44 are displayed. In the date and time display area 41, the administration date and time are displayed. In the message display area 42, a message prompting the patient to take an image of the drug is displayed. In the drug display area 43, the type, quantity, and photo of the drug to be taken are displayed. The information displayed in the drug display area 43 is created based on the prescription data. The camera activation button 44 is a button for activating the imaging unit 16 of the patient terminal 10. Note that the medication guidance screen 40 shown in FIG. 3 is an example and can be changed as appropriate. For example, the photo of the drug may be omitted from the drug display area 43.

[0037] The patient operates the camera activation button 44 to activate the imaging unit 16, places the drug within the imaging range, and presses the shutter button. As a result, the imaging unit 16 of the patient terminal 10 images the drug to create an image of the administered drug, and the control unit 11 stores the image of the administered drug in the storage unit 12 (sequence number S2).

[0038] Next, the communication unit 13 of the patient terminal 10 transmits the patient ID, the image of the administered drug, the administration date, and the administration time to the server 30 (sequence number S3). The patient ID is unique identification information (patient identification information) for identifying the patient. The patient ID is a unique character string or number sequence created for each user during user registration in the medication history management system 1. Information regarding the patient (for example, name, age, prescription data, etc.) is registered in the server 30 in association with the patient ID.

[0039] In this embodiment, the image of the administered drug and the like are transmitted from the patient terminal 10 to the server 30 at the timing when the image of the administered drug is captured. Alternatively, the patient terminal 10 may transmit the image of the administered drug and the like to the server 30 at another cycle (for example, every day, every week). Also, when the patient visits a pharmacy or a hospital, the patient may operate the patient terminal 10 to transmit the image of the administered drug and the like to the server 30.

[0040] A program for operating the medication history management system 1 is stored in the storage unit 32 of the server 30. The control unit 31 of the server 30 reads and executes the program stored in the storage unit 32 to perform the processes of the following sequence numbers S4 to S6.

[0041] The communication unit 33 of the server 30 receives the patient ID, the image of the administered drug, the administration date, and the administration time from the patient terminal 10, and the control unit 31 of the server 30 associates these data and stores them in the storage unit 32 (sequence number S4). Also, since the prescription data is registered in the server 30 as described above, the server 30 can also specify the type and quantity of the drug to be administered. Hereinafter, the patient ID, the type and quantity of the drug to be administered, the image of the administered drug, the administration date, and the administration time are collectively referred to as medication history data. The medication history data is managed as a database. Therefore, for example, by specifying the patient ID, the data associated with the patient ID can be extracted.

[0042] Note that the medication history data may be registered not only in the server 30 but also in the patient terminal 10. Thereby, the patient can check the medication history data only by starting the application of the patient terminal 10 without acquiring data from the server 30.

[0043] Next, the control unit 31 of the server 30 analyzes the image of the administered drug to specify the type and quantity of the drug (sequence number S5). Specifically, a drug database is registered in the storage unit 32 of the server 30. The drug database is a database that associates the type (name) of the drug, the image of the drug, and the description of the drug, etc. The control unit 31 of the server 30 performs a matching process between the image of the drug included in the image of the administered drug and the image of the drug in the drug database to specify the type of the drug included in the image of the administered drug. Further, the control unit 31 specifies the quantity for each type of the specified drug.

[0044] Note that the drug database may be stored not in the server 30 but in another server. Also, the matching process may be performed not by the server 30 but by another server.

[0045] Here, there is a concern that the processing load of the control unit 31 will increase if matching processing is performed for all the drug images registered in the drug database. Therefore, the control unit 31 of the server 30 may identify the type (name) of the drug prescribed based on the prescription data, and read only the images corresponding to the identified type (name) of the drug from the drug database to perform the matching processing. This is because the possibility of accidentally taking a drug that has not been prescribed is extremely low. Another reason is that the matching processing performed at sequence number S5 is sufficient if it can determine whether the taking is correct, and there is little need to identify which drug was taken instead when the taking is incorrect. Note that the matching processing may be performed for all the drug images.

[0046] The process of identifying the type and quantity of the drug from the taken drug image is not limited to the matching process. For example, the same function can be realized using AI. In this case, learning data associating the image of the drug taken, the type and quantity of the drug, is created in advance. It is preferable that there are a plurality of images of the drug taken, but a single image may also be used. A determination model is created by performing supervised learning using this learning data. Then, during operation, by inputting the taken drug image into the determination model, the type and quantity of the drug are output from the determination model. By using the determination model, it may be possible to identify the correct drug type even if the taken drug image is unclear or the angle is different from normal. Note that a determination model for identifying the type of the drug and a determination model for determining the quantity of the drug may be provided separately.

[0047] Next, the control unit 31 of the server 30 collates the identified drug type and quantity with the prescription data and stores the collation result in the storage unit 32 (sequence number S6). Hereinafter, when the drug type and quantity identified by analyzing the taken drug image match the drug type and quantity in the prescription data, the collation result is referred to as "match" or the like. When the two do not match, the collation result is referred to as "mismatch" or the like. As described above, part of the processing performed by the server 30 may be performed by the patient terminal 10 or the medical staff terminal 20. That is, the patient terminal 10 or the medical staff terminal 20 may perform the matching process or the collation process with the prescription data.

[0048] Thus, the processing in the registration stage is completed. Note that the processing of sequence numbers S5 and S6 is not an essential process and can be omitted.

[0049] Next, with reference to FIGS. 4 and 5, the processing performed by the medical staff terminal 20 and the server 30 in the stage of utilizing the medication history will be described.

[0050] Software for operating the medication history management system 1 is installed in the medical staff terminal 20. The medical staff terminal 20 can receive the medication history data from the server 30 or display the medication history screen on the display unit 35 based on the operation of the medical staff. This will be specifically described below.

[0051] The medical staff terminal 20 receives an instruction to display the medication history of a patient designated by the medical staff. Thereafter, the communication unit 33 of the medical staff terminal 20 designates the patient ID of this patient and requests the server 30 for the medication history corresponding to the patient ID (sequence number S11).

[0052] The communication unit 33 of the server 30 receives this request. The control unit 31 of the server 30 reads out the medication history data associated with the designated patient ID (sequence number S12).

[0053] Next, the control unit 31 of the server 30 determines whether unit packaging is recommended and stores the determination result in the storage unit 32 (sequence number S13). Note that the timing for performing this process is arbitrary. For example, it may be when a separate request is received from the medical staff terminal 20, or this process may be performed at a predetermined cycle regardless of the request.

[0054] Specifically, the control unit 31 identifies the frequency of medication errors based on the verification result. When the frequency of medication errors exceeds the reference value, the control unit 31 determines that unit packaging is recommended. When the frequency of medication errors is equal to or less than the reference value, the control unit 31 determines that unit packaging is not recommended. Note that instead of performing a two-stage determination (recommended, not recommended), the control unit 31 may perform a determination with three or more stages (recommendation level: low, medium, high, etc.).

[0055] In addition to the frequency of medication errors, the quantity of the drug to be taken may be considered. That is, when the quantity of the drug to be taken is large, medication errors are likely to occur, and even if they do not occur, the burden on the patient to check all the drugs is significant. Therefore, the control unit 31 may determine that the higher the quantity of the drug to be taken, the higher the recommendation level for unit packaging.

[0056] In addition, the determination of the recommendation for unit packaging is not limited to the process using the reference value. For example, the same function can be realized using AI. In this case, learning data including a medication history (including the determination result of medication errors) and prescription data for which unit packaging is recommended is created in advance. The learning data may be the determination results actually performed in the past or virtual cases. Further, the learning data may include a medication history and prescription data for which unit packaging was not recommended. A determination model is created by performing supervised learning using this learning data. Then, during operation, by inputting the medication history and prescription data into the determination model, the degree of recommendation for unit packaging is output from the determination model. By using the determination model, it is possible to make an appropriate determination considering not only the frequency of medication errors but also other circumstances and the tendency of medication errors (in other words, mimicking the judgment of medical staff).

[0057] Next, the control unit 31 of the server 30 analyzes the tendency of taking medicine mistakes and stores the analysis result in the storage unit 32 (sequence number S14). Note that the timing for performing this process is arbitrary. For example, it may be when there is a separate request from the medical staff terminal 20, or this process may be performed at a predetermined cycle regardless of the request.

[0058] The control unit 31 tabulates the situations where taking medicine mistakes occur. For example, it tabulates the number (ratio) of taking medicine mistakes for each day of the week, the number (ratio) of taking medicine mistakes for each taking time point, the number (ratio) of taking medicine mistakes for each type of medicine, the number (ratio) of mistakes in the quantity of medicine, etc. Note that the tabulation methods listed here are just examples and can be changed as appropriate.

[0059] Also, the determination of the tendency of taking medicine mistakes is not limited to the above tabulation process. For example, the same function can be realized using AI. In this case, in advance, learning data including typical patterns of taking medicine mistakes and the medication histories (including the determination results of taking medicine mistakes) determined to correspond to the patterns is created. The learning data may use actual medication histories or may be virtual medication histories created. By performing supervised learning using this learning data, a determination model is created. Then, during operation, by inputting the medication history into the determination model, it is output which pattern it is similar to and the degree of similarity, etc. By using the determination model, it is possible to identify patterns that are not noticed in rule-based analysis.

[0060] Note that the processes related to the determination of single-packaging and the analysis of taking medicine mistakes are not essential processes and can be omitted.

[0061] The communication unit 33 of the server 30 transmits the medication history data, determination result, and analysis result corresponding to the specified patient ID to the medical staff terminal 20 (sequence number S15).

[0062] The communication unit 23 of the medical staff terminal 20 receives these data. The control unit 21 of the medical staff terminal 20 creates a medication history screen 50 using the medication history data (sequence number S16). Then, the control unit 21 of the medical staff terminal 20 displays the medication history screen 50, the determination result, and the analysis result on the display unit 25 (sequence number S17).

[0063] In this embodiment, the medical staff terminal 20 creates the medication history screen 50. Alternatively, the server 30 may create the medication history screen 50 and the server 30 may transmit the medication history screen 50 to the medical staff terminal 20. Even in this case, since the server 30 transmits the medication history data to the medical staff terminal 20, it is included in the scope of the present invention.

[0064] The history display area 51 of the medication history screen 50 shown in FIG. 5 is a tabular screen in which the area is divided using the administration date and time. One area corresponds to one administration. A medication image is displayed in each area. In this way, by displaying a list of medication images, the medical staff can grasp the medication history at a glance.

[0065] In the method of Patent Document 1 described above, even if the patient thinks that all the medications have been taken, if one medication has actually been forgotten to be taken, a medication history different from the actual medication history is registered. On the other hand, in the medication history management system 1 of this embodiment, since the medication history is registered using the medication image, in a similar case, the number of medications included in the medication image is reduced by one, so that the correct medication history can be registered.

[0066] Also, in the method of Patent Document 1 described above, the patient may operate the button indicating that the medication has been taken without checking the displayed content. On the other hand, in the medication history management system 1 of this embodiment, since the medication history is registered using the medication image, there is no concern as in Patent Document 1.

[0067] Therefore, in this embodiment, an accurate medication history can be registered. As a result, medical staff can provide medication guidance based on the accurate medication history.

[0068] The list display of the administered drug images in the history display area 51 is just an example, and a configuration may be adopted in which the administered drug images registered when each area is selected are displayed. Also, the administered drug images displayed in the history display area 51 use the images captured by the patient as they are. However, the control unit 31 may cut out the portion where the drug is displayed from the image captured by the patient and display it on the medication history screen 50.

[0069] In addition, the collation results are further displayed in each area of the history display area 51. Specifically, the display modes are different between the area where the collation result is a match and the area where the collation result is a mismatch. In FIG. 5, the collation result for the morning dose on October 3 is a mismatch and is highlighted. As the highlighting mode, for example, the color or pattern of the background area of the administered drug image can be changed, a specific mark can be added, or the area can be surrounded by a thick frame. Also, in the area where the medication history is not registered, it is indicated to that effect. In FIG. 5, since the medication history for the lunch on October 2 is not registered, a cross mark is shown. By displaying the collation results in a list, it is not necessary for the medical staff to identify each dosing error one by one.

[0070] When the determination result display button 52 displayed on the medication history screen 50 is operated, the control unit 21 of the medical staff terminal 20 causes the display unit 15 to display the above-described determination result. As a result, the medical staff can consider the determination result on the system side and examine whether to propose single-packaging or not.

[0071] When the analysis result display button 53 displayed on the medication history screen 50 is operated, the control unit 21 of the medical staff terminal 20 causes the display unit 15 to display the above-described analysis result. As a result, the medical staff can consider the analysis result on the system side and propose methods for preventing dosing errors.

[0072] FIG. 6 shows a medication history screen 50 according to a modified example.

[0073] The history display area 51 of the medication history screen 50 of the modified example is further divided for each drug. Therefore, the taken drug images are also displayed for each drug. Specifically, as described in the sequence number S5, the server 30 of the present embodiment can identify the type of drug included in the taken drug image. Therefore, the server 30 can cut out the image of each drug type from the taken drug image. The server 30 registers the cut-out image for each drug as the taken drug image for each drug in the medication history database.

[0074] Also in the medication history screen 50 according to the modified example, the area where a medication error occurred is highlighted. In the medication history screen 50 according to the modified example, since there is an area where drug administration is unnecessary (for example, the trough of drug B), that area is also displayed in a different display mode (one diagonal line in FIG. 6).

[0075] By displaying the medication history screen 50 according to the modified example, medical staff can immediately grasp whether there are medication errors for each drug type.

[0076] As described above, the server 30 of the present embodiment includes a communication unit 33, a storage unit 32, and a control unit 31, and functions as a medication history management device by executing a medication history management method by executing a medication history management program. The communication unit 33 receives a medication image, which is an image of a drug taken by a patient at the time of taking the drug, from the patient terminal 10, which is the patient's terminal (receiving step). The storage unit 32 stores the medication image received by the communication unit 33 in association with a patient ID for identifying the patient, the medication date, and the time of taking the drug (storage step). In response to a request from the medical staff terminal 20, which is a terminal of a dispensing pharmacy or a hospital, the control unit 31 reads out from the storage unit 32 the medication history data in which the medication image, the medication date, and the time of taking the drug corresponding to the patient ID received from the medical staff terminal 20 are associated, and transmits the data to the medical staff terminal 20, and performs a process of causing the medical staff terminal 20 to display a medication history screen 50 in which the medication image, the medication date, and the time of taking the drug are associated (display step).

[0077] By managing the medication history using the medication image, it is less likely that a registration error in the medication history will occur due to a patient's misunderstanding or carelessness. As a result, a highly accurate medication history can be registered. In addition, by providing the information received from the patient terminal to the medical staff terminal, the medical staff can provide medication guidance using the highly accurate medication history.

[0078] In the server 30 of the present embodiment, the medication history screen 50 is a tabular screen in which areas are divided using the medication date and the time of taking the drug. In each area of the medication history screen 50, a medication image corresponding to the medication date and the time of taking the drug is displayed.

[0079] Thereby, the medical staff can grasp the patient's medication history at a glance.

[0080] In the server 30 of the present embodiment, the control unit 31 analyzes the taken medicine image to identify the type and quantity of the medicine included in the taken medicine image. The control unit 31 identifies the type and quantity of the medicine for each taking date and taking time based on the prescription data of the patient. The control unit 31 collates whether the type and quantity of the medicine included in the taken medicine image match the type and quantity of the medicine identified based on the prescription data, and stores the collation result.

[0081] Thereby, it is possible to collate on the system side whether the medicine is taken correctly. Therefore, the labor of the medical staff for collation can be reduced.

[0082] In the server 30 of the present embodiment, the medicine-taking history screen 50 is a tabular screen whose area is divided by taking date and taking time. In each area of the medicine-taking history screen 50, the collation result corresponding to the taking date and taking time is displayed.

[0083] Thereby, the medical staff can grasp at a glance whether the medicine is taken correctly.

[0084] In the server 30 of the present embodiment, in each area of the medicine-taking history screen 50, the collation result and the taken medicine image corresponding to the taking date and taking time are displayed.

[0085] Thereby, the medical staff can easily check whether the collation result of the medicine-taking is correct.

[0086] In the server 30 of the present embodiment, the control unit 31 determines whether single-packaging is recommended based on the collation result, and stores the determination result.

[0087] Thereby, the medical staff can obtain reference information on whether to recommend single-packaging by accessing the determination result.

[0088] In the server 30 of the present embodiment, the control unit 31 analyzes the tendency of taking mistakes based on the collation result, and stores the analysis result.

[0089] This enables medical staff to speculate on the reasons why medication errors are likely to occur or to give advice to make it less likely that medication errors will occur by accessing the analysis results.

Explanation of symbols

[0090] 1 Medication history management system 10 Patient terminal 20 Medical staff terminal 30 Server (medication history management device) 40 Medication guidance screen 50 Medication history screen

Claims

1. A communication unit that receives, from a patient terminal which is a terminal of a patient, a taken drug image which is an image of a drug taken by the patient during taking; A storage unit that stores the taken drug image received by the communication unit in association with patient identification information for identifying a patient, a taking date, and a taking time; A control unit that, in response to a request from a medical staff terminal which is a terminal of a dispensing pharmacy or a hospital, reads out from the storage unit the medication history data associating the taken drug image, the taking date, and the taking time corresponding to the patient identification information received from the medical staff terminal, transmits the data to the medical staff terminal, and performs a process of causing the medical staff terminal to display a medication history screen associating the taken drug image, the taking date, and the taking time; A medication history management device, characterized by comprising the above.

2. The medication history management device according to Claim 1, wherein the medication history screen is a tabular screen whose area is divided using the taking date and the taking time, and in each area of the medication history screen, the taken drug image corresponding to the taking date and the taking time is displayed.

3. The medication history management device according to Claim 1, wherein the control unit analyzes the taken drug image to specify the type and quantity of the drug included in the taken drug image, the control unit specifies the type and quantity of the drug for each taking date and taking time based on the prescription data of the patient, and the control unit collates whether the type and quantity of the drug included in the taken drug image match the type and quantity of the drug specified based on the prescription data, and stores the collation result.

4. The medication history management device according to Claim 3, wherein the medication history screen is a tabular screen whose area is divided by the taking date and the taking time, and in each area of the medication history screen, the collation result corresponding to the taking date and the taking time is displayed.

5. The medication history management device according to Claim 4, wherein in each area of the medication history screen, the collation result and the taken drug image corresponding to the taking date and the taking time are displayed.

6. The medication history management device according to Claim 3, wherein the control unit determines whether single-packaging is recommended based on the collation result, and stores the determination result.

7. The medication history management device according to claim 3, wherein the control unit analyzes the tendency of medication errors based on the collation result and stores the analysis result. A medication history management device characterized by this.

8. The medication history management device according to any one of claims 1 to 7, the patient terminal, the medical staff terminal, A medication history management system characterized by comprising.

9. A receiving step of receiving, from a patient terminal which is a patient's terminal, a medication image which is an image of a drug taken by the patient at the time of taking the drug; A storage step of storing, in a storage unit, the medication image received in the receiving step in association with patient identification information for identifying the patient, the medication date, and the time of taking the drug; In response to a request from a medical staff terminal which is a terminal of a dispensing pharmacy or a hospital, reading out from the storage unit the medication history data associating the medication image, the medication date, and the time of taking the drug corresponding to the patient identification information received from the medical staff terminal, and transmitting the data to the medical staff terminal, and causing the medical staff terminal to display a medication history screen associating the medication image, the medication date, and the time of taking the drug; A medication history management method characterized by including.

10. A receiving step of receiving, from a patient terminal which is a patient's terminal, a medication image which is an image of a drug taken by the patient at the time of taking the drug; A storage step of storing, in a storage unit, the medication image received in the receiving step in association with patient identification information for identifying the patient, the medication date, and the time of taking the drug; In response to a request from a medical staff terminal which is a terminal of a dispensing pharmacy or a hospital, reading out from the storage unit the medication history data associating the medication image, the medication date, and the time of taking the drug corresponding to the patient identification information received from the medical staff terminal, and transmitting the data to the medical staff terminal, and causing the medical staff terminal to display a medication history screen associating the medication image, the medication date, and the time of taking the drug; A medication history management program for causing a computer to perform a process including.

Images