Medical information processing device

Abstract

To provide a medical information processor that prevents an oversight of an order to update.SOLUTION: A medical information processor 1 has a detection function 112, an extraction function 113, and a control function 114. The detection function 112 acquires information of change of diagnosis information of a patient, and the extraction unit 113 acquires information of an order that has been issued to a patient. The control function 114 displays an update candidate of the content of the issued order to a terminal 10 of a person in charge of diagnosis of the patient on the basis of the information of the change.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The embodiments disclosed in this specification and the drawings relate to a medical information processing apparatus.

Background Art

[0002] In a hospital, for example, a doctor inputs information such as a prescription for a drug and a nursing record based on the medical information of a patient. At this time, in the ordering system within the hospital, the patient information of the patient is acquired, and for the input information, a contraindication check is performed for drugs, allergies, diseases, etc. If there is no problem, an order is issued based on the input information. Here, during drug treatment, treatment of acute diseases, emergency treatment, etc., the patient's condition easily changes, and the medical information of the patient also changes according to the change in the patient's condition. Therefore, it is necessary to update the orders already issued for the patient. On the other hand, only the medical information at the time of input is considered in the content of the issued order. For this reason, a doctor needs to regularly search the medical information of the patient and check the orders that need to be updated. However, checking the orders that need to be updated is time-consuming.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] One of the problems to be solved by the embodiments disclosed in this specification and the drawings is to prevent overlooking orders that need to be updated. However, the problems solved by the embodiments disclosed in this specification and the drawings are not limited to the above problems. It is also possible to position the problems corresponding to the respective effects of each configuration shown in the embodiments described later as other problems.

Means for Solving the Problems

[0005] The medical information processing apparatus according to this embodiment includes a first acquisition unit, a second acquisition unit, and a control unit. The first acquisition unit acquires information on changes in the medical information of a patient. The second acquisition unit acquires information on orders already issued to the patient. The control unit causes an update candidate of the content of the issued order to be displayed on the terminal of a person in charge related to the medical treatment of the patient based on the information on the change.

Brief Description of Drawings

[0006]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7A

Figure 7B

Figure 8

Figure 9

Figure 10

Figure 11A

Figure 11B

Figure 12A

Figure 12B

Figure 13A

Figure 13B

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18A

Figure 18B

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24A

Figure 24B

[0007] Hereinafter, embodiments of the medical information processing apparatus will be described in detail with reference to the accompanying drawings. Note that hereinafter, a medical information processing system 1 including an electronic medical record server in which the functions of the medical information processing apparatus are incorporated will be described as an example. In the medical information processing system 1 shown in FIG. 1, each apparatus is shown as one unit, but actually, a plurality of apparatuses can be further included.

[0008] FIG. 1 is a diagram showing an example of the configuration of a medical information processing system 1 including an electronic medical record server 100 according to the present embodiment. The medical information processing system 1 shown in FIG. 1 is a system including, for example, an electronic medical record system 2, a radiology department information management system (RIS: Radiology Information System), and a medical image management system (PACS: Picture Archiving and Communication System). The electronic medical record system 2 includes, for example, a hospital information system (HIS: Hospital Information System) and an ordering system 3.

[0009] The medical information processing system 1 shown in FIG. 1 includes an electronic medical record server 100, an ordering server 200, terminals 10 and 20, and an HIS server (not shown). The electronic medical record server 100 has the functions of a medical information processing device.

[0010] The terminals 10 and 20 are used by the persons in charge related to the medical treatment of patients. For example, the terminal 10 is used by a doctor, and the terminal 20 is used by medical staff such as a nurse. The terminals 10 and 20 include, for example, a PC (Personal Computer), a tablet PC, a PDA (Personal Digital Assistant), a mobile terminal, and the like.

[0011] As described above, the electronic medical record server 100 is incorporated into the electronic medical record system 2 together with the ordering server 200 and the HIS server. The electronic medical record server 100 is communicably connected to the ordering server 200, the terminals 10 and 20, etc. via a network. The electronic medical record server 100, the ordering server 200, the terminals 10 and 20 are connected to, for example, an in-hospital LAN (Local Area Network) installed in a hospital or the like, transmit information to a predetermined device, and receive information transmitted from a predetermined device. For example, the electronic medical record server 100 and the ordering server 200 are realized by computer devices such as a workstation and a personal computer.

[0012] The electronic medical record server 100 includes a processing circuit 110 and a memory circuit 120. Note that the electronic medical record server 100 is not limited to the above configuration. For example, the memory circuit 120 does not have to be built into the electronic medical record server 100 as long as the electronic medical record server 100 can access it over a network.

[0013] The memory circuit 120 is connected to the processing circuit 110 and stores various types of information. Specifically, the memory circuit 120 stores patient information received from each system. For example, the memory circuit 120 is implemented by a semiconductor memory element such as a RAM (Random Access Memory), a flash memory, or a hard disk, an optical disk, or the like.

[0014] The processing circuit 110 controls the components of the electronic medical record server 100. For example, the processing circuit 110 executes a processing function 111, a detection function 112, an extraction function 113, and a control function 114. Here, for example, each function executed by the processing function 111, the detection function 112, the extraction function 113, and the control function 114, which are components of the processing circuit 110, is recorded in the memory circuit 120 in the form of a program executable by a computer. The processing circuit 110 is a processor that reads each program from the memory circuit 120 and executes it to realize the function corresponding to each program. In other words, the processing circuit 110 in the state of having read each program has each function shown in the processing circuit 110 of FIG. 1.

[0015] The processing function 111 executes the functions of the electronic medical record system. Specifically, the processing function 111 stores an electronic medical record containing patient information such as prescriptions, nursing records, and examinations performed on a patient in the memory circuit 120.

[0016] Patient information includes the patient's basic information, medical information, and examination execution information. The basic information includes patient ID, name, date of birth, gender, blood type, height, weight, etc. Identification information for uniquely identifying the patient is set for the patient ID. The patient's medical information includes information such as numerical values (measurement values) and medical records, and information indicating the recording date and time thereof. For example, as the patient's medical information, there are information such as prescriptions by doctors, nursing records by nurses, examinations by the examination department, and meal arrangements at the time of hospitalization. For example, prescriptions are recorded in the electronic medical record by doctors, and nursing records are recorded in the electronic medical record by nurses. The examination execution information includes information such as past examinations and examination results thereof, and information indicating the execution date of the examination.

[0017] The processing of the detection function 112, extraction function 113, and control function 114 will be described later.

[0018] The memory circuit 120 has a medical information database (hereinafter simply referred to as DB), a medical information DB 121, and an update order DB 122. The medical information DB 121 corresponds to, for example, the memory circuit of the HIS server and stores the patient's medical information or the electronic medical record recording the patient's medical information. The update order DB 122 will be described later.

[0019] The ordering server 200 has a processing circuit 210 and a memory circuit 220. Note that the ordering server 200 is not limited to the above-described configuration. For example, the memory circuit 220 does not have to be built in the ordering server 200 as long as the ordering server 200 can access it on the network.

[0020] The memory circuit 220 is connected to the processing circuit 210 and stores various information. Specifically, the memory circuit 220 has an order DB 221, and the order DB 221 stores the issued orders. For example, the memory circuit 220 is realized by a semiconductor memory element such as a RAM or a flash memory, a hard disk, an optical disk, or the like.

[0021] The processing circuit 210 controls the components of the ordering server 200. For example, the processing circuit 210 executes a processing function 211. Here, for example, the function executed by the processing function 211, which is a component of the processing circuit 210, is recorded in the storage circuit 220 in the form of a program executable by a computer. The processing circuit 210 is a processor that reads the program from the storage circuit 220 and executes it to realize the function corresponding to the program. In other words, the processing circuit 210 in the state of having read the program will have the functions shown in the processing circuit 210 of FIG. 1.

[0022] Based on the medical information of the patient, the processing function 211 issues an order for, for example, a doctor to prescribe medicine, a nurse to record care, an examination for the examination department, and arrangements for meals at the time of hospitalization. For example, the doctor uses the terminal 10 to input information such as a doctor's prescription of medicine, a nurse's care record, an examination for the examination department, and arrangements for meals at the time of hospitalization based on the medical information of the patient. At this time, the processing function 211 acquires the patient information of the patient from the medical information DB 121 of the electronic medical record server 100, performs a contraindication check on the input information for medicine, allergies, diseases, etc., and if there is no problem with the contraindication check, issues an order based on the input information. For example, the processing function 211 performs a contraindication check on whether the medicine prescribed to the patient falls under the combination precautions. If it does, the processing function 211, for example, displays information indicating the correspondence on the doctor's terminal 10 to warn the doctor. On the other hand, if it does not, the processing function 211 issues an order based on the input information, and for example, displays the issued order on the nurse's terminal 20 to notify the nurse. In addition, the processing function 211 registers the issued order in the order DB 221.

[0023] Note that the term "processor" used in the above description means a circuit such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an application specific integrated circuit (ASIC), or a programmable logic device (for example, a simple programmable logic device (SPLD), a complex programmable logic device (CPLD), and a field programmable gate array (FPGA)). When the processor is, for example, a CPU, the processor realizes its function by reading and executing a program stored in the storage circuit 140. On the other hand, when the processor is, for example, an ASIC, instead of storing the program in the storage circuit 140, the program is directly incorporated into the circuit of the processor. Note that each processor of the present embodiment is not limited to being configured as a single circuit for each processor, and a plurality of independent circuits may be combined to form one processor to realize its function. Further, a plurality of components in FIG. 2 may be integrated into one processor to realize its function.

[0024] As described above, the overall configuration of the medical information processing system 1 including the electronic medical record server 100 according to the present embodiment has been described. With such a configuration, the electronic medical record server 100 prevents overlooking an order that needs to be updated.

[0025] For example, during drug treatment, the treatment of acute diseases, emergency treatment, etc., the patient's condition is likely to change. Since the patient's medical information also changes according to the change in the patient's condition, it is necessary to update the issued order for the patient. On the other hand, since only the medical information at the time of input is considered in the content of the issued order, the doctor needs to regularly search the patient's medical information and check the orders that need to be updated. However, it takes time to check the orders that need to be updated. Also, for example, during drug treatment, when a patient develops side effects or an infectious disease, the drug treatment with the drug prescribed in the issued dosing order may be temporarily interrupted, and a new dosing order for prescribing an alternative drug or a drug for treating side effects or infectious diseases may be issued. In that case, if the cancellation of the issued dosing order is forgotten, both the issued dosing order and the new dosing order will exist. If both the issued dosing order and the new dosing order exist, there is a possibility that medical staff such as nurses involved in the patient's medical treatment will be confused. Therefore, it is necessary to detect the change to the drug prescribed in the new dosing order as a change point from the issued dosing order and cancel the issued dosing order.

[0026] Therefore, in the electronic medical record server 100 according to the present embodiment, in order to prevent overlooking orders that need to be updated, the following processing is performed. First, in the electronic medical record server 100 according to the present embodiment, the detection function 112 acquires information on changes in the patient's medical information. The extraction function 113 acquires information on the orders issued to the patient. The control function 114 causes the content update candidates of the issued orders to be displayed on the terminal of the person in charge related to the patient's medical treatment based on the change information.

[0027] Here, the change in medical information is, for example, the addition of an order or a change in the medical information related to the order. For changes not related to medical treatment, the order is not updated. Examples of order updates include cases where the order is changed (for example, a change in quantity (in the case of a drug, a change in the dosage), the addition of a drug, etc.), and cases where the issued order is canceled and a new order is issued. Some examples will be given and described below.

[0028] First, the processing of the electronic medical record server 100 according to the present embodiment will be described with reference to FIGS. 2 to 13. FIG. 2 is a flowchart showing the procedure of processing by the medical information processing system 1 including the electronic medical record server 100 according to the present embodiment.

[0029] In step S101 of FIG. 2, the detection function 112 of the electronic medical record server 100 acquires the medical information of the patient. For example, a nurse uses the terminal 20 to register the nursing record of the patient as the medical information of the patient in the medical information DB 121 of the electronic medical record server 100. For example, the nursing record is recorded in the electronic medical record by the nurse. At this time, the detection function 112 acquires the medical information of the patient registered in the medical information DB 121. In step S102 of FIG. 2, the detection function 112 detects the information on the change of the patient's medical information as a medical information change point. That is, the detection function 112 acquires the medical information change point of the patient. The detection function 112 is an example of the first acquisition unit.

[0030] In step S103 of FIG. 2, the extraction function 113 of the electronic medical record server 100 acquires the information on the orders already issued to the patient as the ordering history from the order DB 221 of the ordering server 200. In step S104 of FIG. 2, the extraction function 113 extracts the update candidates of the contents of the already issued orders as the update order candidates based on the medical information change points of the patient. That is, the extraction function 113 acquires the update order candidates. The extraction function 113 is an example of the second acquisition unit. Here, the extraction function 113 acquires the information on the orders already issued to the patient when the detection function 112 detects the medical information change point of the patient, but may always acquire the information on the orders already issued.

[0031] In step S105 of FIG. 2, the control function 114 of the electronic medical record server 100 causes the update order candidates to be displayed on the terminal of the person in charge related to the patient's medical treatment. Specifically, the control function 114 causes the update order candidates to be displayed on the doctor's terminal 10. The control function 114 is an example of the control unit.

[0032] Here, in step S106 of FIG. 2, for example, it is assumed that a doctor approves the update order candidates displayed on the terminal 10. In this case, in step S107 of FIG. 2, the control function 114 of the electronic medical record server 100 updates the content of the issued order based on the approved update candidates and outputs it to the ordering server 200. Note that if the doctor does not approve the update order candidates displayed on the terminal 10, the issued order is not updated.

[0033] In step S108 of FIG. 2, when the processing function 211 of the ordering server 200 receives the updated order based on the update candidates approved by the doctor, it acquires the patient information of the patient from the medical information DB 121 of the electronic medical record server 100. In step S109 of FIG. 2, the processing function 211 performs a contraindication check on the received order for drugs, allergies, diseases, etc. Here, if there is a problem with the contraindication check, the processing function 211, for example, displays information indicating that there is a problem with the contraindication check on the doctor's terminal 10 to warn the doctor. If there is no problem with the contraindication check, in step S110 of FIG. 2, the processing function 211 issues the order.

[0034] FIG. 3 is a diagram for explaining the processing by the electronic medical record server 100 according to the present embodiment. In the present embodiment, a doctor uses the terminal 10 to associate the patient attributes, the content of the change in the medical information of the patient attributes, and the update content of the order accompanying the change, and registers them in the update order DB 122 of the electronic medical record server 100. The update order DB 122 is an example of a database.

[0035] For example, in FIG. 3, the control function 114 of the electronic medical record server 100 registers the attribute information 300 of the patient group X with similar symptoms, etc. as patient attributes in the update order DB 122. In the example shown in FIG. 3, the attribute information 300 of the patient group X indicates that the department is "Department of Breast Surgery", the treatment phase is "Classical CMF during chemotherapy", the symptom is "Febrile neutropenia", and the execution order that is currently being implemented is "Antibacterial agent A, 2 g once every 8 hours". Here, as an example of the conditions for defining the patient group X, the department, treatment phase, symptom, and execution order are listed, but the patient group X may be defined for each symptom, or the patient group X may be defined only by the disease name. Furthermore, as conditions for defining the patient group X, the patient ID, patient name, gender, date of birth, etc. may be combined.

[0036] Also, for example, in FIG. 3, the control function 114 registers update order information 400 including the content of the change in medical information and the update content of the order accompanying the change, in association with the patient attribute (attribute information 300 of the patient group X) in the update order DB 122. In the example shown in FIG. 3, the update order information 400 indicates that as the content of the change in the medical information of the patient group X, the change point of the medical information is the addition of "<Order addition> Antibacterial agent B, 6 mg / kg every 12 hours", and as the update content of the order accompanying the change, the candidate for the update order is "Antibacterial agent A, 2 g once every 8 hours", and its update content is "Discontinuation". Also, the update order information 400 indicates that as the content of the change in the medical information of the patient group X, the change point of the medical information is the addition of "Antibacterial agent C, 100 - 150 mg once every 24 hours", and as the update content of the order accompanying the change, the candidate for the update order is "Antibacterial agent A, 2 g once every 8 hours", and its update content is "Discontinuation".

[0037] FIG. 4 is a diagram for explaining the processes of steps S101 and S102 as the processes performed by the electronic medical record server 100 according to the present embodiment. In the above-described steps S101 and S102, when the detection function 112 of the electronic medical record server 100 acquires the medical information of a patient whose patient name is "Patient A" from the medical information DB 121, the detection function 112 detects information on changes in the medical information of the patient with the patient name "Patient A" as a medical information change point.

[0038] For example, the detection function 112 detects patient information regarding a patient from the medical information registered in the medical information DB 121 of the electronic medical record server 100. In the example shown in FIG. 4, the detection function 112 detects patient information 310 indicating that the patient name is "Patient A", the medical department is "Department of Breast Surgery", the medical phase is "Classical CMF during chemotherapy", the symptom is "Febrile neutropenia", and the current implementation order is "Antibacterial drug A 2 g once every 8 hours" from the medical information registered in the medical information DB 121.

[0039] In addition, the detection function 112 detects a medical information change point from the medical information of the patient with the patient name "Patient A". For example, the detection function 112 recognizes characters such as "addition", "change", and "order issuance" from the medical information of the patient with the patient name "Patient A" and detects a medical information change point. Specifically, in the example shown in FIG. 4, the detection function 112 detects a medical information change point 410 indicating that the content of the change point of the medical information is "<Order addition> Antibacterial drug B 6 mg / kg every 12 hours" and the type of the change point is "Order issuance" from the medical information of the patient with the patient name "Patient A".

[0040] FIG. 5 is a diagram for explaining the processes of steps S103 and S104 as the processes performed by the electronic medical record server 100 according to the present embodiment. In step S104 described above, the extraction function 113 of the electronic medical record server 100 acquires information on orders already issued to a patient from the order DB 221 of the ordering server 200, and extracts, as candidates for updated orders, candidates for updating the contents of the already issued orders based on the changes in the patient's medical information. Specifically, the extraction function 113 refers to the updated order DB 122 to acquire the updated contents (candidates for updated orders) corresponding to the patient attributes and the contents of changes in the medical information of the patient attributes (points of change in medical information), and sets the acquired updated contents as candidates for updating the contents of the already issued orders (candidates for updated orders).

[0041] For example, the extraction function 113 determines to which group of patients among the groups of patients registered in the updated order DB 122 the patient "Patient A" of the patient information 310 of the medical information detected by the detection function 112 belongs. Here, in FIG. 5, the patient information 310 of the medical information detected by the detection function 112 belongs to the attribute information 300 of the patient group X registered in the updated order DB 122. In this case, the extraction function 113 determines whether the point of change in medical information 410, which is the point of change in medical information detected by the detection function 112, matches the point of change in medical information "<Order addition> Antibacterial agent B 6 mg / kg every 12 hours" of the updated order information 400 of the patient group X registered in the updated order DB 122.

[0042] Here, in FIG. 5, the change point 410 of the medical information of patient "Patient A" matches the change point of the medical information of the order update information 400 of the patient group X registered in the update order DB 122, "<Order addition> Antibacterial drug B 6 mg / kg every 12 hours". In this case, based on the change point 410 of the medical information of patient "Patient A", the extraction function 113 extracts the update candidate of the content of the order already issued to patient "Patient A", "Antibacterial drug A 2 g once every 8 hours", as a candidate for the update order ("Antibacterial drug A 2 g once every 8 hours", "Cancellation"). If the change point 410 of the medical information does not match the change point of the medical information of the order update information 400 of the patient group X registered in the update order DB 122, "<Order addition> Antibacterial drug B 6 mg / kg every 12 hours", the extraction function 113 does not extract a candidate for the update order.

[0043] FIG. 6 is a diagram for explaining the processing of steps S105 to S107 as the processing by the electronic medical record server 100 according to the present embodiment. In the above-described step S105, the control function 114 of the electronic medical record server 100 causes the terminal 10 of the doctor involved in the medical treatment of the patient to display a button for receiving whether to approve the candidate for the update order (candidate for the update order) together with the candidate for the update of the content of the order already issued. For example, the control function 114 notifies the doctor by displaying the candidate for the update order on the terminal 10 by means of an e-mail or the like.

[0044] For example, in the above-described step S105, the control function 114 causes the terminal 10 of the doctor to display a screen 500 as shown in FIG. 6. As shown in FIG. 6, on the screen 500, patient information 310 indicating that the patient ID is "10001", the patient name is "Patient A", the gender is "male", and the date of birth is "April 2, 1970" is displayed. Also, on the screen 500, patient information indicating that the patient ID is "10002", the patient name is "Patient B", the gender is "female", and the date of birth is "February 3, 1973" is displayed. Also, on the screen 500, patient information indicating that the patient ID is "10003", the patient name is "Patient C", the gender is "female", and the date of birth is "March 15, 1980" is displayed.

[0045] For example, on screen 500, for the patient information 310 of patient name "Patient A", a display column 501 "!Order Update Required" is displayed as information for a doctor to confirm whether there is approval for a candidate for an update order. At this time, the control function 114 actively displays, for example, the display column 501 "!Order Update Required" in a display form such as blinking display or highlighting display. For example, when the doctor uses the terminal 10 to place the cursor on the display column "!Order Update Required" on screen 500, as a candidate for an update order, a message "Antibacterial drug B 6 mg / kg has been added. Please confirm the discontinuation of antibacterial drug A 2 g once." is displayed near the display column 501 "!Order Update Required" on screen 500. At this time, a button 502 "Approve" and a button 503 "Reject" for receiving whether to approve the candidate for the update order are displayed in the message. The button 502 "Approve" and the button 503 "Reject" are an example of a first reception unit. Here, in this embodiment, buttons are taken as an example, but it is not limited to buttons as long as an input device such as a mouse cursor of the terminal or a touch panel can receive whether to approve the candidate for the update order.

[0046] In the above step S106, for example, when the doctor approves the candidate for the update order, the doctor operates the button 502 "Approve" on screen 500 using the terminal 10. In this case, in the above step S107, the control function 114 of the electronic medical record server 100 updates the content of the issued order based on the candidate for the update order for which approval has been received, and outputs it to the ordering server 200. On the other hand, when the doctor does not approve the candidate for the update order, the doctor operates the button 503 "Reject" on screen 500 using the terminal 10. In this case, the issued order is not updated.

[0047] FIG. 7A and FIG. 7B are diagrams for explaining the processing after step S110 as the processing by the electronic medical record server 100 according to the present embodiment. The control function 114 of the electronic medical record server 100 causes the nurse's terminal 20 related to the patient's medical treatment to display information indicating whether or not a doctor has confirmed the update candidates (update order candidates) of the contents of the issued order.

[0048] For example, the control function 114 causes the nurse's terminal 20 to display a screen 510 as shown in FIG. 7A. As shown in FIG. 7A, information indicating that the scheduled execution date is "February 3, 2021" and the order name is "Antibacterial drug A 2 g once ···" is displayed on the screen 510. Also, information indicating that the scheduled execution date is "February 3, 2021" and the order name is "Antibacterial drug B 6 mg / kg ···" is displayed on the screen 510.

[0049] For example, when the doctor approves the update order candidate, as shown in FIG. 7A, on the screen 510, further, for the order name "Antibacterial drug B 6 mg / kg ···", information indicating that the doctor has confirmed the update order candidate, in other words, has made a judgment of either approval or rejection, is displayed as a message "Confirmed by doctor". For example, the control function 114 notifies the nurse in a display form such as blinking display or highlighting display of the message "Confirmed by doctor" on the screen 510. For example, when the nurse places the cursor on the message "Confirmed by doctor" on the screen 510 using the terminal 20, in the situation where the doctor has approved, a message "Prescription order confirmed. Antibacterial drug B 6 mg / kg has been added and antibacterial drug A 2 g once has been cancelled." is displayed near the message "Confirmed by doctor" on the screen 510. In this case, the nurse executes the order with the order name "Antibacterial drug B 6 mg / kg ···". Note that when the doctor has rejected it, a message "The update order candidate has been rejected." is displayed on the screen.

[0050] For example, when the doctor has neither approved nor rejected the update order candidates, as shown in FIG. 7B, on the screen 510, further, for the order name "Antibacterial drug B 6 mg / kg ···", as information indicating that the doctor has not approved the update order candidates, a message "Not confirmed by doctor" is displayed. For example, the control function 114 notifies the nurse on the screen 510 of the message "Not confirmed by doctor" in a display form such as blinking display or highlighting display. For example, when the nurse uses the terminal 20 to place the cursor on the message "Confirmed by doctor" on the screen 510, as information for prompting the doctor to confirm the update order candidates from the nurse, a message "Please confirm the prescription order. Antibacterial drug B 6 mg / kg has been added. There is a possibility of canceling 2 g of antibacterial drug A once. Please confirm with the doctor." is displayed near the message "Not confirmed by doctor" on the screen 510.

[0051] Here, when the control function 114 causes the message "Not confirmed by doctor" to be displayed on the nurse's terminal 20, it further displays a button for notifying the doctor that update order candidates are presented. Such a button is the button 512. The button 512 is an example of a second reception unit. For example, when the control function 114 receives an operation on the button 512 from the nurse, it causes the doctor's terminal 10 to display that there are unconfirmed update candidates and notifies the doctor.

[0052] FIG. 8 is a diagram for explaining other processes of steps S105 to S107 as processes by the electronic medical record server 100 according to the present embodiment. For example, in the update order DB 122, there may be a plurality of registered update contents corresponding to the patient attributes and the contents of changes in medical information (points of change in medical information). In this case, when the extraction function 113 of the electronic medical record server 100 refers to the update order DB 122 and acquires a plurality of update contents corresponding to the patient attributes and the points of change in medical information, the control function 114 causes a plurality of update candidates (candidates for update orders) corresponding to each of the acquired plurality of update contents to be displayed on the doctor's terminal 10.

[0053] For example, as shown in FIG. 8, in the update order DB 122, in the patient group X to which the patient with the patient name "Patient A" belongs, the candidate for the update order is "antibacterial agent A, 2 g once every 8 hours", the update content is "discontinuation", and the change point of the medical information is "<order addition> antibacterial agent B, 6 mg / kg every 12 hours" is registered. Also, in the update order DB 122, in the patient group X to which the patient with the patient name "Patient A" belongs, the candidate for the update order is "antibacterial agent A, 2 g once every 8 hours", the update content is "change", and the change point of the medical information is "<order addition> antibacterial agent B, 6 mg / kg every 12 hours" is registered. Here, examples of the update content "change" include the case of using "antibacterial agent A" and "antibacterial agent B" in combination. Also, examples of the update content "change" include the case of using "antibacterial agent A" and "antibacterial agent B" in combination by reducing the amount of "antibacterial agent A" to half as the difference in the order content before and after the change.

[0054] In the example shown in FIG. 8, when the extraction function 113 refers to the update order DB 122 and acquires a plurality of candidates for the update order corresponding to the patient group X to which the patient with the patient name "Patient A" belongs and the change point of the medical information, in step S105 described above, the control function 114 causes the plurality of candidates for the update order corresponding to each of the plurality of acquired change points of the medical information to be displayed on the screen of the doctor's terminal 10. At this time, on the screen of the terminal 10, a message "Please confirm the prescription order. Antibacterial agent B 6 mg / kg has been added. Please confirm the necessity of the update for the order of antibacterial agent A, 2 g once" is displayed.

[0055] Further, the control function 114 causes a button for receiving whether to approve each of the plurality of update order candidates to be displayed on the screen of the terminal 10 together with the plurality of update order candidates. Specifically, on the screen of the terminal 10, the update contents "Cancel" and "Change" are respectively displayed as buttons. In the above step S106, the doctor uses the terminal 10 to operate a button representing the update content "Cancel" or a button representing the update content "Change", thereby canceling "Antibacterial agent A, 2 g once every 8 hours" and adding "Antibacterial agent B, 6 mg / kg once every 12 hours" as an order candidate, or selecting an order candidate for changing "Antibacterial agent A, 2 g once every 8 hours" to "Antibacterial agent B, 6 mg / kg once every 12 hours". The button representing the update content "Cancel" and the button representing the update content "Change" are examples of the third reception unit. Here, when changing the content of the order, for example, the doctor can register the change content using the text input screen displayed by operating the button representing "Change". In addition, on the screen 500 shown in FIG. 6, a button representing "Change" may be further displayed to provide the doctor with options other than approval and rejection.

[0056] Then, in the above step S107, based on the update order candidate for which approval has been received by the operation of the doctor, the control function 114 of the electronic medical record server 100 updates the content of the issued order and outputs it to the ordering server 200.

[0057] FIG. 9 is a diagram for explaining other processes of steps S105 to S107 as the processes by the electronic medical record server 100 according to the present embodiment. For example, the detection function 112 of the electronic medical record server 100 acquires a plurality of medical information change points, which are information on changes in the patient's medical information. Each of the plurality of medical information change points may correspond to a different issued order. In this case, the control function 114 causes the update candidates (update order candidates) corresponding to each of the plurality of medical information change points to be displayed on the doctor's terminal 10 in the order of proximity of the scheduled execution date and time.

[0058] For example, as shown in FIG. 9, in the patient group X belonging to the patient with the patient name "Patient A" in the update order DB 122, the candidate for the update order is "Analgesic B, 2 g once every 8 hours", the update content is "Cancellation", and the change point of the medical information is registered as "<Order addition> Analgesic A, 6 mg / kg once every 12 hours". Also, in the update order DB 122, in the patient group X belonging to the patient with the patient name "Patient A", the candidate for the update order is "Antibacterial agent A, 2 g once every 8 hours", the update content is "Cancellation", and the change point of the medical information is registered as "<Order addition> Antibacterial agent B, 6 mg / kg once every 12 hours".

[0059] In the example shown in FIG. 9, when each of the plurality of detected medical information change points detected by the detection function 112 corresponds to a different issued order, in step S105 described above, the control function 114 causes the candidates for the update orders corresponding to each of the plurality of medical information change points to be displayed on the screen of the doctor's terminal 10. At this time, the control function 114 displays the priorities of the candidates for the plurality of update orders on the screen on the terminal 10. For example, an order for prescribing "Analgesic B, 2 g once every 8 hours" was issued at "9:00 on February 3, 2021", and then an order for prescribing "Antibacterial agent A, 2 g once every 8 hours" was issued at "12:00 on February 3, 2021". In this case, the control function 114 causes the candidates for the plurality of update orders to be displayed on the screen 530 in the order of the proximity of the scheduled execution date and time. Specifically, on the screen of the terminal 10, for the candidate for the order to "Cancel" "Analgesic B, 2 g once every 8 hours" and add "Analgesic A, 6 mg / kg once every 12 hours", and the candidate for the order to "Cancel" "Antibacterial agent A, 2 g once every 8 hours" and add "Antibacterial agent B, 6 mg / kg once every 12 hours", priorities "1" and "2" are respectively displayed. At this time, the control function 114 causes the candidates for the plurality of update orders to be displayed on the screen of the terminal 10 in the order of the higher priority.

[0060] In addition, the control function 114 causes a button for receiving a selection of an update order candidate to be displayed on the screen of the terminal 10. Specifically, on the screen of the terminal 10, priorities “1” and “2” are each displayed as buttons. In the above-described step S106, the doctor uses the terminal 10 to operate the button representing priority “1” or the button representing priority “2” to cancel “Analgesic B 2 g once every 8 hours” and add an order candidate of “Analgesic A 6 mg / kg once every 12 hours”, or cancel “Antibacterial agent A 2 g once every 8 hours” and add an order candidate of “Antibacterial agent B 6 mg / kg once every 12 hours”.

[0061] Then, in the above-described step S107, based on the update order candidate approved by the operation of the doctor, the control function 114 of the electronic medical record server 100 updates the content of the issued order and outputs it to the ordering server 200. Note that, on the screen of the terminal 10, the control function 114 displays a plurality of update order candidates in descending order of priority, but only the update order candidate with the highest priority among the plurality of update order candidates may be displayed.

[0062] FIG. 10 is a diagram for explaining other processes of steps S105 to S107 as processes by the electronic medical record server 100 according to the present embodiment. The detection function 112 of the electronic medical record server 100 acquires a plurality of medical information change points, which are information on changes in the patient's medical information, and each of the plurality of medical information change points may correspond to the same issued order. In this case, the control function 114 causes update candidates (update order candidates) based on the plurality of medical information change points to be displayed on the doctor's terminal 10.

[0063] For example, as shown in FIG. 10, in the update order DB 122, under the condition that the change point 1 of the medical information is "Add antibacterial agent A" and the change point 2 of the medical information is "Discontinue anticancer agent B", the candidate for the update order is "Anticancer agent C", and it is registered that the update content is "Discontinue". Also, as shown in FIG. 10, in the update order DB 122, under the condition that the change point 1 of the medical information is "Discontinue antibacterial agent A" and the change point 2 of the medical information is "Add anticancer agent B", the candidate for the update order is "Anticancer agent C", and it is registered that the update content is "Add".

[0064] In the example shown in FIG. 10, when the detection function 112 detects the condition that the change point 1 of the medical information is "Add antibacterial agent A" and the change point 2 of the medical information is "Discontinue anticancer agent B", the candidate for the update order is "Anticancer agent C", and it is obtained that the update content is "Discontinue". In step S105 described above, the control function 114 causes the candidate for the update order based on the change points 1 and 2 of the medical information to be displayed on the screen of the doctor's terminal 10. At that time, the control function 114 displays the update content "Discontinue" as a button on the screen of the terminal 10. In step S106 described above, for example, when the doctor approves the update content, the doctor presses the button representing "Discontinue" using the terminal 10. After that, step S107 described above is executed.

[0065] Also, when the detection function 112 detects the condition that the change point 1 of the medical information is "Discontinue antibacterial agent A" and the change point 2 of the medical information is "Add anticancer agent B", the candidate for the update order is "Anticancer agent C", and it is obtained that the update content is "Add". In step S105 described above, the control function 114 causes the candidate for the update order based on the change points 1 and 2 of the medical information to be displayed on the screen of the doctor's terminal 10. At that time, the control function 114 displays the update content "Discontinue" as a button on the screen of the terminal 10. In step S106 described above, for example, when the doctor approves the update content, the doctor presses the button representing "Discontinue" using the terminal 10. After that, step S107 described above is executed.

[0066] The above-mentioned changes in medical treatment information are information regarding the drugs prescribed to patients. For example, information such as "Antibacterial drug B 6 mg / kg every 12 hours" is added and "Antibacterial drug A 2 g once every 8 hours" is discontinued, but it is not limited to this. For example, the changes in medical treatment information may be information regarding the patient's vital signs.

[0067] In the example shown in FIG. 11A, as the attribute information 320 of the patient group Y, information indicating that the department of medicine is "NICU (Neonatal Intensive Care Unit)", the symptom (weight) is "3200 g or less at the time of order issuance", and the execution order that is the currently executed order is "Diet order: Milk" is registered in the update order DB 122. Here, as an example of the conditions for defining the patient group Y, the department of medicine, symptoms, and execution order are listed, but the patient group Y may be defined for each symptom, or the patient group Y may be defined only by the disease name. Furthermore, as conditions for defining the patient group Y, the patient ID, patient name, gender, date of birth, etc. may be combined.

[0068] Also, in the example shown in FIG. 11A, as the update order information 420, in the patient group Y, information indicating that the candidate for the update order is "Diet order: 80 ml of milk 7 times every 3 hours", the update content is "Change", and the change point in medical treatment information is "weight increase of 700 mg" is registered in the update order DB 122. In this case, the control function 114 of the electronic medical record server 100 causes the terminal 10 of the doctor involved in the patient's medical treatment to display the update candidate (candidate for the update order) of the content of the issued order. For example, the control function 114 notifies the doctor by causing the terminal 10 to display the candidate for the update order by e-mail or the like.

[0069] For example, the control function 114 causes the screen as shown in FIG. 11B to be displayed on the doctor's terminal 10. On the screen shown in FIG. 11B, information associating the date and weight is displayed as a graph. Further, a message such as "Please check the meal order." is displayed on the screen. At this time, for example, a button for receiving the doctor's operation regarding the approval of the update order candidate is displayed within the message.

[0070] The above-described medical treatment information of the patient is a nursing record implemented for the patient and an electronic medical record in which the nursing record is recorded. For example, it may be information such as a prescription of a drug by a doctor, a nursing record by a nurse, an examination for an examination department, and an arrangement of meals at the time of hospitalization. For example, the detection function 112 detects a change point in medical treatment information from the nursing record.

[0071] In the example shown in FIG. 12A, as a nursing record by the nurse with the nurse name "Nurse A", on "March 1, 2019", when the patient named "Patient M" had a rash on the arm, on "March 2, 2019", the issued order was updated to an order to discontinue "Antibiotic A" and add "Antibiotic B". Further, as a nursing record by the nurse "Nurse A", on "August 2, 2019", when the patient named "Patient M" had a rash on the arm, on "August 3, 2019", the issued order was updated to an order to discontinue "Antibiotic A" and add "Antibiotic B". In this case, the detection function 112 detects a change point in medical treatment information from the nursing record, and the control function 114 causes the screen as shown in FIG. 12B to be displayed on the doctor's terminal 10, and a message such as "Please check the medication order." is displayed on the screen. At this time, for example, a button for receiving the doctor's operation regarding the approval of the update order candidate is displayed within the message.

[0072] The above-described change point in medical treatment information may be information regarding an event for the patient.

[0073] For example, in FIG. 13A, when the discharge of the hospitalized patient is postponed by three days, the change point of the medical information is the addition of the patient's discharge event. In this case, the control function 114 causes the screen including messages such as "Please check the meal order... The execution period of the meal order does not include the scheduled discharge date." to be displayed on the doctor's terminal 10. At this time, for example, a button for receiving the doctor's operation regarding the approval of the update order candidate is displayed in the message.

[0074] Also, in FIG. 13B, when the discharge of the hospitalized patient is advanced by three days, the change point of the medical information is the deletion of the patient's discharge event. In this case, the control function 114 causes the screen including messages such as "Please check the meal order... The execution period of the meal order is set after the scheduled discharge date." to be displayed on the doctor's terminal 10. At this time, for example, a button for receiving the doctor's operation regarding the approval of the update order candidate is displayed in the message.

[0075] From the above description, in the electronic medical record server 100 according to the present embodiment, the detection function 112 acquires information on changes in the patient's medical information, the extraction function 113 acquires information on the orders already issued to the patient, and the control function 114 causes the update candidates of the contents of the already issued orders to be displayed on the terminal of the person in charge related to the patient's medical treatment based on the change information. Thereby, in the electronic medical record server 100 according to the present embodiment, it is possible to prevent overlooking orders that need to be updated.

[0076] (Other Embodiments) Although the embodiments have been described so far, in addition to the above-described embodiments, they may be implemented in various different forms.

[0077] (First Modification Example) In the above-described embodiment, a doctor uses the terminal 10 to associate a patient attribute (patient group X with similar symptoms), the content of the change in the medical information of the patient attribute (medical information change point), and the updated content of the order associated with the change (candidate for updated order), and registers them in the updated order DB 122 of the electronic medical record server 100. Here, in the first modification example, the electronic medical record server 100 extracts, for an order that has been issued in the past to a patient group with similar symptoms and whose content has been updated, the update content with a high update frequency (candidate for updated order) and the content of the change in the medical information when the update content is updated (medical information change point), and registers them in the updated order DB 122 in association with the attributes of the patient group.

[0078] The processing of the electronic medical record server 100 according to the first modification example of the present embodiment will be described with reference to FIGS. 14 to 17. FIG. 14 is a flowchart showing the procedure of the processing by the electronic medical record server 100 according to the first modification example of the present embodiment. FIGS. 15 to 17 are diagrams for explaining the processing by the electronic medical record server 100 according to the first modification example of the present embodiment.

[0079] In step S201 of FIG. 14, the control function 114 of the electronic medical record server 100 extracts information on a patient group with similar symptoms and the like from the order DB 221 of the ordering server 200. In step S202 of FIG. 14, the control function 114 acquires information on the issued orders that have been issued in the past for the extracted patient group from the order DB 221 of the ordering server 200.

[0080] In the example shown in FIG. 15, as information of patient group X, the department of medicine is "Department of Breast Surgery", the disease name is "breast cancer", the disease stage is "Stage III", the treatment phase is "Classical CMF during chemotherapy", the symptom is "Febrile neutropenia", and information indicating that the order currently being implemented, the implemented order, is "Antibacterial agent A 2 g once every 8 hours" is registered in the update order DB 122. Here, as conditions for defining patient group X, the department of medicine, the treatment phase, the symptom, and the implemented order are given as examples, but patient group X may be defined for each symptom. Further, as conditions for defining patient group X, a combination of patient ID, patient name, gender, date of birth, etc. may be used.

[0081] In step S203 of FIG. 14, the control function 114 acquires the medical information of the patient group from the medical information DB 121. Then, in step S204 of FIG. 14, the control function 114 extracts, as candidates for update orders, candidates for updating the contents of the issued orders based on the medical information of the patient group.

[0082] Here, in step S204, the control function 114 extracts, for patient groups with similar symptoms, the update content (candidates for update orders) with a high update frequency (relative frequency) for orders that have been issued in the past and whose contents have been updated, and the content of the change in medical information (points of change in medical information) when the said update content was updated.

[0083] For example, in FIG. 16, the relative frequency of the candidate for the order to discontinue "Antibacterial agent A 2 g once every 8 hours" and add "Antibacterial agent B 6 mg / kg once every 12 hours" is "0.45". Here, the relative frequency "0.45" is equal to or higher than the threshold value (for example, "0.3"). In this case, the control function 114 extracts the candidate for the order to discontinue "Antibacterial agent A 2 g once every 8 hours" and add "Antibacterial agent B 6 mg / kg once every 12 hours" as a candidate for the update order.

[0084] In the example shown in FIG. 17, within a certain period from the patient's hospitalization, the relative frequency of the candidate order to discontinue "antibacterial agent A, 2 g once every 8 hours" and add "antibacterial agent B, 6 mg / kg every 12 hours" is "0.34", and the relative frequency of the candidate order to discontinue "antibacterial agent A, 2 g once every 8 hours" and add "antibacterial agent C, 100 - 150 mg once every 24 hours" is "0.32". Here, the relative frequencies "0.34" and "0.32" are equal to or higher than the threshold value. In this case, the control function 114 extracts, as candidates for updated orders, the candidate order to discontinue "antibacterial agent A, 2 g once every 8 hours" and add "antibacterial agent B, 6 mg / kg every 12 hours", and the candidate order to discontinue "antibacterial agent A, 2 g once every 8 hours" and add "antibacterial agent C, 100 - 150 mg once every 24 hours".

[0085] In step S205 of FIG. 14, the control function 114 detects, as points of change in the medical information, information on changes in the medical information of the patient group for the candidate updated orders extracted in step S204. In step S206 of FIG. 14, the control function 114 registers, in the updated order DB 122, the attribute information of the patient group with similar symptoms and the like as patient attributes, and registers, in the updated order DB 122, the candidate updated orders extracted in step S204 and the points of change in the medical information detected in step S205 in association with the attribute information of the patient group.

[0086] As described above, in the first modification example, the electronic medical record server 100 automatically registers, in the updated order DB 122, in association with the attributes of the patient group, the candidates for updated orders with a high update frequency and the points of change in the medical information for the orders that were issued in the past to the patient group with similar symptoms and whose contents have been updated.

[0087] (Second Modification Example) In the second modification example, the electronic medical record server 100 obtains, from orders issued in the past for groups of patients with similar symptoms, each update content (candidate for update order) and the content of the change in medical information (point of change in medical information) when the update content is updated, and generates a model that outputs the update probability of each candidate for update order. Then, the electronic medical record server 100 inputs the attributes of the patient and the information on the change in the patient's medical information (point of change in medical information), and extracts the update content (candidate for update order) with a high update frequency.

[0088] The processing of the electronic medical record server 100 according to the second modification example of the present embodiment will be described with reference to FIGS. 18 to 23. FIGS. 18A and 18B are flowcharts showing the procedure of the processing by the electronic medical record server 100 according to the second modification example of the present embodiment. FIGS. 19 to 23 are diagrams for explaining the processing by the electronic medical record server 100 according to the second modification example of the present embodiment.

[0089] In step S301 of FIG. 18A, the control function 114 of the electronic medical record server 100 extracts information on a group of patients with similar symptoms and the like from the order DB221 of the ordering server 200. In step S302 of FIG. 18A, the control function 114 acquires information on issued orders issued in the past for the extracted group of patients from the order DB221 of the ordering server 200, acquires the medical information of the group of patients from the medical information DB121, and based on the medical information of the group of patients, extracts candidates for updating the content of the issued orders as candidates for updated orders. Then, the control function 114 detects information on changes in the medical information of the group of patients as medical information change points based on the candidates for updated orders in the group of patients, and the control function 114 registers the attribute information of the group of patients in the updated order DB122, and registers the candidates for updated orders and the medical information change points in the updated order DB122 in association with the attribute information of the group of patients. In step S303 of FIG. 18A, the control function 114 generates a model that outputs the update probability of each candidate for an updated order based on the candidates for updated orders and the medical information change points in the group of patients. Then, in step S304 of FIG. 18A, the control function 114 registers the generated model in the updated order DB122 in association with the candidates for updated orders and the medical information change points in the group of patients.

[0090] For example, in FIG. 19, for an order candidate that cancels "antibacterial drug A, 2 g once every 8 hours" as a candidate for an updated order and adds "antibacterial drug B, 6 mg / kg every 12 hours" as a medical information change point, "Model A" is registered in the updated order DB122 as a model. Also, in FIG. 19, for an order candidate that cancels "antibacterial drug A, 2 g once every 8 hours" as a candidate for an updated order and adds "antibacterial drug B, 6 mg / kg every 12 hours" as a medical information change point, "Model B" is registered in the updated order DB122 as a model.

[0091] In step S401 of FIG. 18B, the detection function 112 of the electronic medical record server 100 acquires the patient's medical information from the medical information DB 121 and detects information on changes in the patient's medical information as medical information change points. In step S402 of FIG. 18B, the extraction function 113 acquires information on orders already issued to the patient from the order DB 221 of the ordering server 200 as an ordering history, and extracts candidates for updating the content of the already issued orders as candidates for updated orders based on the medical information change points of the patient. Here, in step S403 of FIG. 18B, the control function 114 acquires a model for the candidates for updated orders. For example, as shown in FIG. 20, the control function 114 acquires a model in which the medical information change points match within a certain period from the patient's hospitalization.

[0092] In step S404 of FIG. 18B, by inputting the patient's attribute information and the medical information change points of the patient's medical information into the model by the control function 114, the model calculates the update probability of each candidate for updated orders. In the example shown in FIG. 21, by inputting the patient's medical information (attribute information such as the patient's age, gender, weight, etc.), the medical information change points, and the information on the orders to be implemented into the model by the control function 114, the model calculates the update probability "72%" of the order candidate for canceling the candidate for updated order "antibacterial drug A 2 g once every 8 hours" and adding "antibacterial drug B 6 mg / kg once every 12 hours". Here, as shown in FIG. 22, the control function 114 may input information considering medical data such as body temperature, disease name, and treatment method into the model as the patient's medical information.

[0093] In step S405 of FIG. 18B, the control function 114 extracts candidates for updated orders whose order update probability is equal to or higher than a set value (for example, "70%"). Then, in step S406 of FIG. 18B, the control function 114 causes the candidates for updated orders extracted to be displayed on the terminal 10 of the doctor involved in the patient's medical treatment. In the example shown in FIG. 23, "order update probability 72%" is displayed in the message on the screen 500.

[0094] As described above, in the second modification example, the electronic medical record server 100 can extract candidates for update orders with high update frequencies by using a model that outputs the update probability of candidates for update orders.

[0095] (Third Modification Example) In the third modification example, the electronic medical record server 100 uses a model that predicts changes in a patient's medical information to predict the content of the change in the patient's medical information and the timing of the change in the patient's medical information.

[0096] With reference to FIGS. 24A and 24B, the processing of the electronic medical record server 100 according to the third modification example of the present embodiment will be described. FIG. 24A is a flowchart showing the procedure of the processing by the electronic medical record server 100 according to the third modification example of the present embodiment. FIG. 24B is a diagram for explaining the processing by the electronic medical record server 100 according to the third modification example of the present embodiment.

[0097] In step S501 of FIG. 24A, the control function 114 of the electronic medical record server 100 acquires, as an ordering history, information on orders already issued to a patient from the order DB221 of the ordering server 200. Further, in step S502 of FIG. 24A, the control function 114 acquires the patient's medical information from the medical information DB121. Here, in step S503 of FIG. 24A, the control function 114 uses a model that predicts changes in the patient's medical information. At this time, in step S504 of FIG. 24A, the model predicts the content of the change in the patient's medical information and detects the predicted change content as a medical information change point. Further, the model predicts the timing of the change in the patient's medical information and detects the predicted change timing as a medical information change point. In this case, in step S505 of FIG. 24A, the extraction function 113 extracts, based on the patient's medical information change point, candidates for updating the content of the already issued order as candidates for update orders. Then, in step S506 of FIG. 24A, the control function 114 causes the terminal 10 of the doctor involved in the patient's medical treatment to display the predicted change content and the predicted change timing as medical information change points together with the extracted candidates for update orders.

[0098] In FIG. 24B, the control function 114 causes the screen including messages such as "Please confirm the medication order. There is a risk that the blood Ca concentration may increase. Please confirm the addition of the next order. Infusion: physiological saline Prescription: diuretic" to be displayed on the terminal 10 of the doctor as the content of the predicted change. At this time, for example, information associating the date (time) with the serum total calcium concentration is displayed as a graph, and the predicted change timing (the dotted line part in FIG. 24B) is displayed in the graph.

[0099] As described above, in the third modification example, the electronic medical record server 100 can predict the change in the patient's medical information by using the model, and display the necessity of updating the issued order in the patient to the terminal 10 of the doctor involved in the patient's medical treatment.

[0100] Note that each component of each device illustrated in the present embodiment is a functional concept, and it is not necessarily physically configured as illustrated. That is, the specific form of the distribution and integration of each device is not limited to that illustrated, and all or part of it can be functionally or physically distributed and integrated in any unit according to various loads, usage situations, etc. Further, each processing function performed by each device can be realized by all or any part of it being realized by a CPU and a program analyzed and executed by the CPU, or can be realized as hardware by wired logic.

[0101] Also, the method described in the present embodiment can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. This program can be distributed via a network such as the Internet. Further, this program can be recorded on a non-temporary recording medium readable by a computer such as a hard disk, a flexible disk (FD), a CD-ROM, an MO, a DVD, etc., and can also be executed by being read from the recording medium by the computer.

[0102] According to at least one embodiment described above, it is possible to prevent overlooking an order that requires updating.

[0103] Although several embodiments have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, replacements, changes, and combinations of embodiments can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, as well as in the invention described in the claims and its equivalent scope.

Explanation of Reference Numerals

[0104] 10 Terminal 20 Terminal 100 Electronic Medical Record Server 112 Detection Function 113 Extraction Function 114 Control Function 410 Change Point of Medical Information

Claims

1. a first acquisition unit that acquires information on changes in a patient's medical treatment information; a second acquisition unit that refers to a database in which patient attributes, the content of changes in medical treatment information, and the updated content of an order associated with the change are associated, and acquires, as an update candidate for the content of the order already issued to the patient, the updated content corresponding to the patient's attributes and the change information; a control unit that causes the update candidate to be displayed on a terminal of a person in charge of the patient's medical treatment; A medical information processing apparatus comprising the above.

2. A first acquisition unit that acquires information on changes in a patient's medical treatment information; a second acquisition unit that acquires an update candidate for the content of an order already issued to the patient based on the content of an order updated in accordance with a change in medical treatment information in a group of patients similar to the patient's attributes and the change information; a control unit that causes the update candidate to be displayed on a terminal of a person in charge of the patient's medical treatment; Comprising the control unit causes information indicating whether or not a doctor as the person in charge has confirmed the update candidate to be displayed together with the update candidate on a terminal of a nurse as the person in charge; A medical information processing apparatus.

3. A first acquisition unit that acquires information on changes in a patient's medical treatment information; a second acquisition unit that acquires an update candidate for the content of an order already issued to the patient based on the content of an order updated in accordance with a change in medical treatment information in a group of patients similar to the patient's attributes and the change information; a control unit that causes the update candidate to be displayed on a terminal of a person in charge of the patient's medical treatment; Comprising the control unit acquires, for each update content and the content of the change in medical treatment information when the update content was updated, in orders issued in the past to a group of patients with similar symptoms, and inputs the patient's attributes and the information on the change in the patient's medical treatment information to a model that outputs the update probability of each update content, thereby extracting update contents with a high update frequency as the update candidates; A medical information processing apparatus.

4. the control unit displays, on a terminal of a doctor as the person in charge, a first reception unit that receives whether or not to approve the update candidate together with the update candidate; when receiving approval of the update candidate by the operation of the doctor, updates the already issued order based on the approved update candidate; The medical information processing apparatus according to any one of Claims 1 to 3.

5. the control unit When displaying information indicating that the doctor has not confirmed the update candidates on the terminal of the nurse, a second reception unit for notifying the doctor that the update candidates are presented is further displayed. When an operation on the second reception unit is received from the nurse, it is notified to the terminal of the doctor that there are unapproved update candidates. The medical information processing apparatus according to claim 2.

6. When a plurality of update contents corresponding to the attributes of the patient and the information of the change are registered in the database, The second acquisition unit refers to the database and acquires a plurality of update contents corresponding to the attributes of the patient and the information of the change. The control unit displays a plurality of update candidates corresponding to each of the plurality of acquired update contents on the terminal of the doctor as the person in charge. The medical information processing apparatus according to claim 1.

7. The control unit On the terminal of the doctor, a third reception unit for receiving whether or not to approve each of the plurality of update candidates is displayed together with the plurality of update candidates. Among the plurality of update candidates, the issued order is updated based on the update candidates approved by the operation of the doctor. The medical information processing apparatus according to claim 6.

8. The control unit displays the plurality of update candidates on the terminal of the doctor in the order of proximity of the scheduled execution date and time. The medical information processing apparatus according to claim 7.

9. When the control unit acquires a plurality of pieces of information on changes in the medical treatment information of the patient by the first acquisition unit, and each of the plurality of pieces of change information corresponds to a different issued order, on the terminal of the doctor as the person in charge, the update candidates corresponding to each of the plurality of pieces of change information are displayed in the order of proximity of the scheduled execution date and time. The medical information processing apparatus according to any one of claims 1 to 8.

10. When the control unit acquires a plurality of pieces of information on changes in the medical treatment information of the patient by the first acquisition unit, and the plurality of pieces of change information correspond to the same issued order, on the terminal of the doctor as the person in charge, update candidates based on the plurality of pieces of change information are displayed. The medical information processing apparatus according to any one of claims 1 to 9.

11. The control unit extracts, for orders issued in the past to patient groups with similar symptoms and whose content has been updated, the update content with a high update frequency and the content of the change in medical information when the update content was updated, and registers them in the database in association with the attributes of the patient group. The medical information processing device according to claim 1.

12. The control unit uses a model that predicts changes in medical information created based on the history of past medical information to predict the content of changes in the patient's medical information, and displays the changing content on the terminal of the person in charge. The medical information processing device according to any one of claims 1 to 11.

13. The control unit uses a model that predicts changes in medical information created based on the history of past medical information to predict the timing of changes in the patient's medical information, and displays the changing timing on the terminal of the person in charge. The medical information processing device according to any one of claims 1 to 11.

14. The information on the change is information regarding the drug prescribed to the patient. The medical information processing device according to any one of claims 1 to 13.

15. The information on the change is information regarding the patient's vital signs. The medical information processing device according to any one of claims 1 to 13.

16. The information on the change is information regarding an event for the patient. The medical information processing device according to any one of claims 1 to 13.

17. The patient's medical information is the nursing record implemented for the patient or the electronic medical record in which the nursing record is recorded. The first acquisition unit acquires the information on the change from the nursing record. The medical information processing device according to any one of claims 1 to 16.

Images