Medical information processing device, medical information processing method, and medical information processing program

Abstract

To support the generation of an incident report.SOLUTION: A medical information processing device includes an acquisition section, a detection section, and a generation section. The acquisition section acquires a first order, which is an order of a plurality of first events occurring to a patient, and a second order, which is an order of a plurality of second events necessary for treating the patient. When the first order does not match the second order, the detection section detects a plurality of third events that do not match each other between the first order and the second order. The generation section generates a report that describes the contents related to the plurality of third events.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The embodiments disclosed in this specification and the drawings relate to a medical information processing device, a medical information processing method, and a medical information processing program. [Background technology]

[0002] In the medical field, medical incidents that could lead to serious medical accidents can occur. To prevent accidents from occurring, medical personnel have traditionally prepared reports on the details of the incident (incident reports).

[0003] In an incident report, medical professionals must chronologically record the events that led up to the incident. Additionally, medical professionals must describe the details of medical procedures that were performed in a manner that differed from the original intention as an incident.

[0004] However, in emergency situations (especially emergency medical care), medical personnel often do not have time to prepare incident reports. On the other hand, when medical personnel prepare incident reports later, the contents of the reports are likely to be incomplete (e.g., discrepancies or omissions). [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Special Publication No. 2015-534141 [Patent Document 2] Japanese Patent Application Laid-Open No. 2010-262466 Summary of the Invention [Problem to be solved by the invention]

[0006] One of the problems to be solved by the embodiments disclosed in this specification and the drawings is to support the creation of incident reports. However, the problems to be solved by the embodiments disclosed in this specification and the drawings are not limited to the above problem. Problems corresponding to the effects of each configuration shown in the embodiments described below can also be positioned as other problems. [Means for solving the problem]

[0007] A medical image processing device according to an embodiment includes an acquisition unit, a detection unit, and a generation unit. The acquisition unit acquires a first order, which is an order of multiple first events that occurred in a patient, and a second order, which is an order of multiple second events necessary to treat the patient. If the first order does not match the second order, the detection unit detects multiple third events that do not match between the first order and the second order. The generation unit generates a report that describes details related to the multiple third events. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a medical information processing system according to an embodiment of the present invention. [Figure 2] FIG. 1 is a block diagram showing an example of the arrangement of a medical image processing apparatus according to the present embodiment. [Figure 3] FIG. 2 is a block diagram showing an example of the configuration of an operation terminal according to the embodiment. [Figure 4] 4 is a flowchart showing an example of the operation of the medical image processing apparatus according to the present embodiment. [Figure 5] FIG. 4 is a diagram showing a first example of a discrepancy detection process according to the present embodiment. [Figure 6] FIG. 10 is a diagram showing a second example of the discrepancy detection process according to the embodiment. [Figure 7] FIG. 10 is a diagram showing a third example of the discrepancy detection process according to the embodiment. [Figure 8] FIG. 10 is a diagram showing a fourth example of the discrepancy detection process according to the embodiment. [Figure 9] FIG. 10 is a diagram showing a fifth example of the discrepancy detection process according to the embodiment. [Figure 10] FIG. 10 is a diagram showing an example of a process for checking check items according to the embodiment. [Figure 11] 10A and 10B are diagrams showing an example of a registration process of the correct order according to the embodiment; [Figure 12] FIG. 10 is a diagram showing an example of an incident report generation process according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, the present embodiment will be described with reference to the drawings. In the present embodiment, a plurality of parts with the same reference numerals are assumed to operate in the same manner, and redundant description will be omitted as appropriate.

[0010] 1 is a block diagram showing an example of the configuration of a medical information processing system 100 according to this embodiment. The medical information processing system 100 is a system that processes medical information. The medical information processing system 100 includes, as its components, a medical information processing device 1, a guideline DB 21, a patient information DB 22, an examination information DB 23, a collection device 30, and an operation terminal 4. The components are connected to each other via a network NW so that they can communicate with each other.

[0011] The medical information processing device 1 is a device that processes medical information. The medical information processing device 1 functions as a server in the medical information processing system 100. The medical information processing device 1 acquires and processes various data from each component belonging to the medical information processing system 100, and outputs the processing results to the operation terminal 4.

[0012] The guideline DB 21 is a database that stores treatment guidelines 210. The treatment guidelines 210 are guidelines that indicate standard treatment policies. The treatment guidelines 210 include the sequence of multiple medical events required to treat a patient. The treatment guidelines 210 may include a series of medical procedure procedures required in emergency medical care.

[0013] The patient information DB 22 is a database that stores patient information 220. The patient information 220 includes basic patient information (eg, name, sex, age), medical history, and contraindications for each patient.

[0014] The test information DB 23 is a database that stores test information 230. The test information 230 includes measurement results and interpretation results for each patient. The measurement results include measurement values of specimen tests performed on the patient and measurement values of vital signs measured on the patient. The interpretation results include findings on medical images obtained by photographing the patient using a medical image diagnostic device.

[0015] The guideline DB 21, the patient information DB 22, and the test information DB 23 may be integrated into one or two databases. The treatment guideline 210, the patient information 220, and the test information 230 may be integrated into one or two data files. The patient information 220 and the test information 230 may be associated with each other for each patient.

[0016] The collection device 30 is a device that collects event records that record multiple medical events that have occurred to a patient. The collection device 30 is used by medical personnel to collect medical events in real time. The collection device 30 may collect patient information 220 and examination information 230. The collection device 30 includes a camera 31, a microphone 32, and a reader 33. The collection device 30 may be a device that supports IoT (Internet of Things) (IoT device).

[0017] The camera 31 captures images of a medical event to collect image data and video data related to the medical event. The microphone 32 records audio of the medical event to collect audio data related to the medical event. The reader 33 scans a barcode to collect scan data related to the barcode. The image data, video data, audio data, and scan data are collectively referred to as an "event record ER." The event record ER includes time information related to the time when the medical event occurred.

[0018] The operation terminal 4 is a terminal operated by an operator (e.g., a medical professional). The operation terminal 4 functions as a client in the medical information processing system 100. The operation terminal 4 presents various information to the operator based on the processing results output from the medical information processing device 1.

[0019] 2 is a block diagram showing an example of the configuration of a medical information processing device 1 according to this embodiment. The medical information processing device 1 includes, as its components, a processing circuit 11, a memory 12, and a communication IF 13. The components are connected to each other via an internal bus so that they can communicate with each other.

[0020] The processing circuit 11 is a circuit that comprehensively controls each component of the medical information processing device 1. The processing circuit 11 has at least one processor. The processor refers to circuits such as a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), and a programmable logic device (PLD). The programmable logic device refers to circuits such as a simple programmable logic device (SPLD), a complex programmable logic device (CPLD), and a field programmable gate array (FPGA).

[0021] If the processor is a CPU, the CPU reads and executes each program stored in the memory 12 to realize each function. If the processor is an ASIC, each function is incorporated as a logic circuit inside the ASIC. The processor may be configured as a single circuit or may be configured by combining multiple circuits. The processor realizes an acquisition function 111, a detection function 112, a generation function 113, a confirmation function 114, a registration function 115, and a system control function 116.

[0022] The acquisition function 111 is a function that performs various acquisitions. The acquisition function 111 acquires a first order OR1, which is the order of multiple medical events (first events) ME1 that have occurred for a patient. The acquisition function 111 acquires a second order OR2, which is the order of multiple medical events (second events) ME2 that are necessary to treat the patient.

[0023] The detection function 112 is a function that performs various detections. The detection function 112 determines whether the first order OR1 matches the second order OR2. If the first order OR1 does not match the second order OR2, the detection function 112 detects multiple medical events (third events) ME3 that do not match each other between the first order OR1 and the second order OR2.

[0024] The generation function 113 is a function for generating various types of reports, such as a report containing information related to a plurality of medical events ME3.

[0025] The confirmation function 114 is a function for performing various confirmations. The confirmation function 114 analyzes the event record ER in which a plurality of medical events ME1 are recorded, thereby confirming the contents of the confirmation items related to the plurality of medical events ME1.

[0026] The registration function 115 is a function for performing various registrations. The registration function 115 registers the first order OR1 as the correct order in response to an operation from the operator.

[0027] The system control function 116 is a function that comprehensively controls each component of the medical information processing device 1. The system control function 116 provides an operating system (OS) that enables the processing circuitry 11 to realize each function. The system control function 116 communicates various types of data via the communication IF 13.

[0028] The memory 12 is a device for storing various types of data. The memory 12 is configured by a magnetic disk, a semiconductor memory, etc. The memory 12 stores various programs executed by the processing circuit 11.

[0029] The communication IF 13 is an interface for communicating various types of data, and communicates with each component belonging to the medical information processing system 100 via the network NW.

[0030] 3 is a block diagram showing an example of the configuration of the operation terminal 4 according to this embodiment. The operation terminal 4 includes, as its components, a processing circuit 41, a memory 42, an input IF 43, a display 44, and a communication IF 45. The components are connected to each other via an internal bus so that they can communicate with each other.

[0031] The processing circuitry 41 is a circuit that comprehensively controls each component of the operation terminal 4. The processing circuitry 41 of the operation terminal 4 has a hardware configuration similar to that of the processing circuitry 11 of the medical information processing device 1. The processing circuitry 41 realizes an acquisition function 411, a display control function 412, and a system control function 413.

[0032] The acquisition function 411 is a function for performing various acquisitions. The acquisition function 411 acquires the processing results output from the medical image processing apparatus 1.

[0033] The display control function 412 is a function for controlling various displays, and displays an image based on the processing result acquired by the acquisition function 411 on the display 44.

[0034] The system control function 413 is a function that comprehensively controls each component of the operation terminal 4. The system control function 413 provides an operating system (OS) that enables the processing circuit 41 to realize each function. The system control function 413 communicates various types of data via the communication IF 45.

[0035] The memory 42 is a device for storing various types of data. The memory 42 of the operation terminal 4 has a hardware configuration similar to that of the memory 12 of the medical information processing device 1. The memory 42 stores various programs executed by the processing circuitry 41.

[0036] The input IF 43 is an interface that accepts input operations from an operator. The input IF 43 is composed of a mouse, a keyboard, buttons, switches, a trackball, a touch panel, etc. The input IF 43 converts the input operations from the operator into electrical signals and outputs these electrical signals to the processing circuit 41.

[0037] The display 44 is a device that displays various images. The display 44 is configured by a liquid crystal display, an organic EL (Electro-luminescence) display, or the like. The display 44 displays a GUI (Graphical User Interface) for receiving input operations from an operator. The display 44 may also have the function of the input IF 43.

[0038] The communication IF 45 is an interface for communicating various types of data, and communicates with each component of the medical information processing system 100 via the network NW.

[0039] 4 is a flowchart showing an example of operation of the medical information processing device 1 according to this embodiment. The medical information processing device 1 may acquire a start instruction input by the operator through the operation terminal 4, and start this example of operation in response to this start instruction.

[0040] (Step S1) First, the medical information processing device 1 acquires an event record ER through the acquisition function 111. Specifically, the acquisition function 111 acquires the event record ER from the collection device 30. The event record ER includes various data related to multiple medical events ME1 that have occurred for a patient. The multiple medical events ME1 include at least one of changes in the patient's condition (e.g., symptoms, vital signs), the issuance of medical instructions for the patient (e.g., transfusion instructions, surgery instructions, measurement instructions), and the performance of medical procedures for the patient (e.g., blood transfusion, surgery, measurement of vital signs). The multiple medical events ME1 do not need to be arranged in chronological order.

[0041] (Step S2) Next, the medical information processing device 1 acquires the first order OR1 through the acquisition function 111. Specifically, for the event record ER acquired in step S1, the acquisition function 111 uses the time at which each of the multiple medical events ME1 in the event record ER occurred. The acquisition function 111 acquires the first order OR1 by arranging the multiple medical events ME1 in chronological order based on this time. That is, the acquisition function 111 acquires the first order OR1, which is the order in which the multiple medical events ME1 occurred along the timeline, by listing the multiple medical events ME1 in chronological order.

[0042] (Step S3) Next, the medical information processing device 1 acquires the second order OR2 through the acquisition function 111. Specifically, the acquisition function 111 accesses the guideline DB 21 and acquires the treatment guideline 210. The acquisition function 111 acquires the second order OR2, which is the order of multiple medical events ME2 required to treat the patient, from the treatment guideline 210. Step S3 may be executed before step S1 or S2.

[0043] (Step S4) Subsequently, the medical image processing device 1 determines, through the detection function 112, whether the first order OR and the second order OR2 match. Specifically, the detection function 112 determines whether the first order OR1 acquired in step S2 matches the second order OR2 acquired in step S3. If the first order OR1 matches the second order OR2 (step S4-YES), the process proceeds to step S8. If the first order OR1 does not match the second order OR2 (step S4-NO), the process proceeds to step S5 (see FIGS. 5, 6, 7, 8, and 9).

[0044] In step S4, the medical information processing device 1 may check the contents of the check items related to the multiple medical events ME1 through the check function 114. Specifically, the check function 114 may check whether the contents of the check items are correct by analyzing the event record ER acquired in step S1 (see FIG. 10).

[0045] (Step S5) Next, the medical information processing device 1 determines whether or not to register the first order OR1 through the registration function 115. Specifically, the registration function 115 registers the first order OR1 as the correct order in response to an operation from the operator. The correct order is an order that is assumed to be correct for dealing with the patient, even though it does not conform to the treatment guideline 210. The correct order can also be described as an exceptional measure, avoidance measure, or new measure that differs from the treatment guideline 210. If the first order OR1 is to be registered (step S5-YES), the process proceeds to step S6A. If the first order OR1 is not to be registered (step S5-NO), the process proceeds to step S6B.

[0046] (Step S6A) In this case, the medical information processing device 1 registers the correct order list L through the registration function 115. Specifically, the registration function 115 registers the first order OR1 as a new entry in the correct order list L. That is, the registration function 115 updates the existing correct order list L with the new entry. After step S6A, the process proceeds to step S8 (see FIG. 11).

[0047] In step S4, if the first order OR1 does not match the second order OR2 (step S4-NO), the detection function 112 may further determine whether the first order OR1 is registered in the correct order list L. If the first order OR1 is registered in the correct order list L, step S8 may be executed following step S4. In this case, the detection function 112 may not execute steps S5, S6A, S6B, and S7. Furthermore, the detection function 112 may display the correct order list L on the display 44 (see FIG. 11).

[0048] Steps S5 and S6A may be omitted, in which case step S6B may be executed following step S4-NO.

[0049] (Step S6B) In this case, the medical information processing device 1 detects discrepant events through the detection function 112. Specifically, the detection function 112 detects multiple medical events ME3 (i.e., discrepant events) that do not match between the first order OR1 and the second order OR2. After step S6B, the process proceeds to step S7 (see FIGS. 5, 6, 7, 8, and 9).

[0050] (Step S7) Subsequently, the medical information processing device 1 generates a report through the generation function 113. Specifically, the generation function 113 generates a report (i.e., an incident report) that describes the contents related to the multiple discrepancy events detected in step S6B. The generation function 113 may display an image related to the generated report on the display 44. After step S7, the process proceeds to step S8 (see FIG. 12).

[0051] (Step S8) Finally, the medical information processing device 1 determines whether or not to end the process through the system control function 116. If the process is to be ended (step S8-YES), the medical information processing device 1 ends the series of processes. If the process is not to be ended (step S8-NO), the process returns to step S1.

[0052] 5 is a diagram showing a first example of the discrepancy detection process according to this embodiment, which shows a generation order table 510A, a generation order timeline 510B, a definition order table 610A, and a definition order timeline 610B.

[0053] The occurrence order table 510A is a table showing a first order OR1, which is the order in which multiple medical events ME1 occurred for a patient. The occurrence order table 510A correlates six medical events #1A to #6A with the time at which each medical event occurred. The occurrence order (first order OR1) of the six medical events #1A to #6A is #1A, #2A, #3A, #4A, #5A, and #6A.

[0054] As shown in area 511A, medical event #1A is "bleeding." Medical event #2A is "instructions: bleeding, please give a blood transfusion." Medical event #3A is "blood transfusion." Medical event #4A is "blood pressure stable." Medical event #5A is "blood pressure stabilized, please give a TAE." Medical event #6A is "TAE." TAE stands for transcatheter arterial embolization.

[0055] The occurrence order timeline 510B is a timeline that schematically shows the occurrence order of six medical events #1A to #6A. The occurrence times of the six medical events #1A to #6A are shown as arrows on a number line that indicates the flow of time. The number line has tick marks every 10 seconds.

[0056] The definition order table 610A is a table showing a second order OR2, which is the order of multiple medical events ME2 required to treat a patient. The definition order table 610A includes three definitions (definition 1 to definition 3) related to the second order OR2. The definition order table 610A includes four medical events #1B to #4B for each definition. The implementation order (second order OR2) of the four medical events #1B to #4B is #1B, #2B, #3B, and #4B.

[0057] According to "Definition 1" shown in area 611A, medical event #1B is "no bleeding," medical event #2B is "stable blood pressure," and medical event #3B is "TAE." According to "Definition 2" shown in area 612A, medical event #1B is "bleeding," medical event #2B is "blood transfusion," medical event #3B is "stable blood pressure," and medical event #4B is "TAE." According to "Definition 3" shown in area 613A, medical event #1B is "bleeding," medical event #2B is "blood transfusion," medical event #3B is "drop in blood pressure," and medical event #4B is "surgical procedure to stop bleeding."

[0058] The definition order timeline 610B is a timeline that schematically shows four medical events #1B to #4B. The order in which the four medical events #1B to #4B are performed is shown as arrows on a number line that indicates the flow of time.

[0059] The detection function 112 determines whether the order of the six medical events #1A to #6A shown in area 511A matches the order of the four medical events #1B to #4B shown in area 611A, 612A, or 613A. As a result of the determination, the detection function 112 determines that the order of the six medical events #1A to #6A matches the order of "Definition 2" shown in area 612A (corresponding to step S4-YES). The detection function 112 does not detect a discrepancy event.

[0060] 6 is a diagram showing a second example of the discrepancy detection process according to this embodiment, which shows a generation order table 520A, a generation order timeline 520B, a definition order table 610A, and a definition order timeline 610B.

[0061] The occurrence order table 520A is similar to the occurrence order table 510A. The occurrence order table 520A correlates five medical events #1A to #5A with the time at which each medical event occurred. The occurrence order (first order OR1) of the five medical events #1A to #5A is #1A, #2A, #3A, #4A, and #5A.

[0062] As shown in area 521A, medical event #1A is "bleeding." Medical event #2A is "instruction: bleeding, please give a blood transfusion." Medical event #3A is "blood transfusion." Medical event #4A is "please give a TAE." Medical event #5A is "TAE."

[0063] The chronological timeline 520B is similar to the chronological timeline 510B. The chronological order of occurrence of the five medical events #1A to #5A is shown as arrows on a number line indicating the flow of time.

[0064] The detection function 112 determines whether the order of the five medical events #1A to #5A shown in area 521A matches the order of the four medical events #1B to #4B shown in area 611A, 612A, or 613A. As a result of the determination, the detection function 112 determines that the order of the five medical events #1A to #5A does not match the order of "Definition 1," "Definition 2," or "Definition 3" (corresponding to step S4-NO).

[0065] In particular, the order of the five medical events #1A to #5A is similar to the order of the four medical events #1B to #4B in "Definition 2." However, medical event #4A "Please perform TAE" does not match medical event #3B "Blood pressure stable." That is, a medical instruction to perform TAE has been issued to the patient without confirming that blood pressure is stable as described in "Definition 2." The detection function 112 detects medical events #4A and #3B as discrepant events.

[0066] 7 is a diagram showing a third example of the discrepancy detection process according to this embodiment, which shows a generation order table 530A, a generation order timeline 530B, a definition order table 610A, and a definition order timeline 610B.

[0067] The occurrence order table 530A is similar to the occurrence order table 510A. The occurrence order table 530A correlates six medical events #1A to #6A with the time at which each medical event occurred. The occurrence order (first order OR1) of the six medical events #1A to #6A is #1A, #2A, #3A, #4A, #5A, and #6A.

[0068] As shown in area 531A, medical event #1A is "bleeding." Medical event #2A is "instruction: bleeding, please give a blood transfusion." Medical event #3A is "blood transfusion." Medical event #4A is "blood pressure stabilized." Medical event #5A is "blood pressure stabilized, please give surgical treatment to stop the bleeding." Medical event #6A is "surgical treatment to stop the bleeding."

[0069] The chronological timeline 530B is similar to the chronological timeline 510B. The chronological order of occurrence of six medical events #1A to #6A is shown as arrows on a number line indicating the flow of time.

[0070] The detection function 112 determines whether the order of the six medical events #1A to #6A shown in area 531A matches the order of the four medical events #1B to #4B shown in area 611A, 612A, or 613A. As a result of the determination, the detection function 112 determines that the order of the six medical events #1A to #6A does not match the order of "Definition 1," "Definition 2," or "Definition 3" (corresponding to step S4-NO).

[0071] In particular, the order of the six medical events #1A to #6A is similar to the order of the four medical events #1B to #4B in "Definition 2." However, medical event #6A "Hemostatic Surgical Procedure" does not match medical event #4B "TAE." That is, "TAE" should be performed on the patient, but "Hemostatic Surgical Procedure" has been performed. The detection function 112 detects medical events #6A and #4B as discrepant events.

[0072] 8 is a diagram showing a fourth example of the discrepancy detection process according to this embodiment, which shows a generation order table 540A, a generation order timeline 540B, a definition order table 620A, and a definition order timeline 620B.

[0073] The occurrence order table 540A is similar to the occurrence order table 510A. The occurrence order table 540A correlates four medical events #1A to #4A with the time at which each medical event occurred. The occurrence order (first order OR1) of the four medical events #1A to #4A is #1A, #2A, #3A, and #4A.

[0074] As shown in area 541A, medical event #1A is "bleeding." Medical event #2A is "instruction: bleeding, please give a blood transfusion." Medical event #3A is "blood transfusion." Medical event #4A is "transfusion completed."

[0075] The chronological timeline 540B is similar to the chronological timeline 510B. The chronological order of occurrence of the four medical events #1A to #4A is shown as arrows on a number line indicating the flow of time. In particular, the length of time (transfusion time) between medical events #3A and #4A is 1 minute 30 seconds.

[0076] Definition sequence table 620A is similar to definition sequence table 610A. Area 621A in definition sequence table 620A is the same as area 611A in definition sequence table 610A. Meanwhile, for areas 622A and 623A in definition sequence table 620A, medical event #2B is "blood transfusion 3 minutes."

[0077] Definition order timeline 620B is similar to definition order timeline 610B, in particular the duration of medical event #2B (3 minutes) is shown as a band on a number line indicating the flow of time.

[0078] The detection function 112 determines whether the order of the four medical events #1A to #4A shown in area 541A matches the order of the four medical events #1B to #4B shown in area 621A, 622A, or 623A. As a result of the determination, the detection function 112 determines that the order of the four medical events #1A to #4A does not match the order of "Definition 1," "Definition 2," or "Definition 3" (corresponding to step S4-NO).

[0079] In particular, the order of the four medical events #1A to #4A is similar to the order of the four medical events #1B to #4B in "Definition 2" and "Definition 3." However, the length of time (transfusion time) between medical event #3A and medical event #4A (1 minute 30 seconds) does not match the length of time (transfusion time) indicated by medical event #2B in "Definition 2" and "Definition 3" (3 minutes). In other words, the patient was expected to receive a "3 minute" transfusion, but only a "1 minute 30 second" transfusion was actually performed. The detection function 112 detects medical events #3A, #4A, and #2B as discrepant events.

[0080] In this way, the detection function 112 may detect whether the length of time of the medical event ME1 performed on the patient is reasonable. The detection function 112 may calculate the length of time between two medical events ME1 based on the occurrence times of the two medical events ME1. The detection function 112 may determine whether the calculated length of time matches the length of time of the medical event ME2 assumed in the treatment guideline 210.

[0081] 9 is a diagram showing a fifth example of the discrepancy detection process according to this embodiment, which shows a generation order table 550A, a generation order timeline 550B, a definition order table 630A, and a definition order timeline 630B.

[0082] The occurrence order table 550A is similar to the occurrence order table 510A. The occurrence order table 550A correlates two medical events #1A and #2A with the time at which each medical event occurred. The occurrence order (first order OR1) of the two medical events #1A and #2A is #1A and #2A.

[0083] As shown in area 551A, medical event #1A is "respiratory arrest." Medical event #2A is "defibrillation (shock)."

[0084] Chronological timeline 550B is similar to chronological timeline 510B. The chronological order of occurrence of two medical events #1A and #2A is shown as arrows on a number line indicating the flow of time. In particular, the length of time (breathing arrest time) between medical event #1A and medical event #2A is 10 minutes and 10 seconds.

[0085] Definition sequence table 630A is similar to definition sequence table 610A. As shown in area 631A, medical event #1B is "respiratory arrest" and medical event #2B is "defibrillation (shock): within 2 minutes of respiratory arrest."

[0086] The defined order timeline 630B is similar to the defined order timeline 610B. The order of the two medical events #1B and #2B is shown as arrows on a number line indicating the flow of time. In particular, the length of time (breathing time) between medical events #1B and #2B is 2 minutes.

[0087] The detection function 112 determines whether the order of the two medical events #1A and #2A shown in area 551A matches the order of the two medical events #1B and #2B shown in area 631A. As a result of the determination, the detection function 112 determines that the order of the two medical events #1A and #2A does not match the order in the "definition" (corresponding to step S4-NO).

[0088] In particular, the order of the two medical events #1A and #2A is similar to the order in the "Definition." However, the length of time (respiratory arrest time) between medical events #1A and #2A (10 minutes 10 seconds) does not match the length of time (respiratory arrest time) between medical events #1B and #2B in the "Definition" (within 2 minutes). In other words, although the patient was supposed to receive a defibrillation shock "within 2 minutes" of respiratory arrest, the defibrillation shock was administered "10 minutes 10 seconds" after respiratory arrest. The detection function 112 detects medical events #1A, #2A, #1B, and #2B as discrepant events.

[0089] In this manner, the detection function 112 may detect the time difference between when a medical event ME1 occurs for a patient and when another medical event ME1 occurs for a medical professional to treat the patient. The detection function 112 may determine whether the detected time difference matches the time difference between two medical events ME2 assumed in the treatment guidelines 210. The detection function 112 may make this determination by setting a tolerance for the detected time difference.

[0090] 10 is a diagram showing an example of a check item checking process according to this embodiment. This example shows a check item table 700A and a check item list table 700B. The check item table 700A and the check item list table 700B may be stored in the memory 12.

[0091] The check item table 700A is a table listing multiple check items related to multiple medical events ME1 that have occurred for a patient. The check item table 700A includes six check items #1A to #6A. Three check items #1A to #3A are check items related to the patient. The remaining three check items #4A to #6A are check items related to the blood pack used for this patient.

[0092] Check item #1A is "Patient's blood type." Check item #2A is "Amount of blood to be transfused to the patient." Check item #3A is "Type of blood needed by the patient." Check item #4A is "Blood type of blood pack." Check item #5A is "Volume of blood pack." Check item #6A is "Type of blood pack."

[0093] The confirmation function 114 analyzes the event record ER related to the patient, etc., to confirm the contents of confirmation items #1A to #6A. For example, the confirmation function 114 searches the patient information 220 or the test information 230 and confirms the contents of confirmation item #1A. The confirmation function 114 analyzes the voice data included in the event record ER and confirms the contents of confirmation items #2A and #3A. The confirmation function 114 analyzes the scan data included in the event record ER and confirms the contents of confirmation items #4A to #6A. This scan data may be obtained in advance by the reader 33 scanning a barcode attached to the blood pack. The confirmation function 114 associates each confirmation result with the confirmation items #1A to #6A.

[0094] The check item list table 700B is a table that lists check items related to multiple medical events ME1 that have occurred for a patient. The check item list includes check items #1B to #3B related to consistency between the patient and the blood pack. Check item #1B is "Consistency between the patient's blood type and the blood type of the blood pack." Check item #2B is "Consistency between the amount of blood to be transfused to the patient and the volume of the blood pack." Check item #3B is "Consistency between the type of blood required for the patient and the type of blood pack."

[0095] The confirmation function 114 confirms the contents of three confirmation items #1B to #3B in the confirmation item list table 700B based on six confirmation results #1A to #6A in the confirmation item table 700A. First, the confirmation function 114 compares two confirmation results #1A (Type A) and #4A (Type A) and confirms that there is consistency for confirmation item #1B. Second, the confirmation function 114 compares two confirmation results #2A (500 mL) and #5A (300 mL) and confirms that there is no consistency for confirmation item #2B. Third, the confirmation function 114 compares two confirmation results #3A (whole blood) and #6A (whole blood) and confirms that there is consistency for confirmation item #3B. The confirmation function 114 associates each confirmation result with check items #1B to #3B.

[0096] In this way, the confirmation function 114 may confirm the contents of various confirmation items related to multiple medical events ME1 that have occurred for a patient. For example, the confirmation items may include whether or not medical instructions have been issued for the patient based on the patient's condition. That is, the confirmation function 114 may confirm whether or not a medical professional has issued medical instructions for the patient after visually or otherwise checking the patient's condition. The confirmation function 114 may confirm the above contents by analyzing image data, video data, or audio data included in an event record ER that records multiple medical events ME1.

[0097] 11 is a diagram showing an example of a correct order registration process according to this embodiment. This example shows a correct order table 800. The correct order table 800 is an example of the correct order list L. The correct order table 800 may be displayed on the display 44.

[0098] The correct order table 800 is a table that lists the first order OR1 that has been registered by the operator as the correct order. The correct order table 800 includes two definitions (definition 1 and definition 2) related to the first order OR1. The correct order table 800 includes four medical events #1C to #4C for each definition. The occurrence order of the four medical events #1C to #4C is #1C, #2C, #3C, and #4C.

[0099] According to "Definition 1" shown in area 810A, medical event #1C is "bleeding," medical event #2C is "blood transfusion," and medical event #3C is "TAE required." The three medical events #1C to #3C according to "Definition 1" correspond to the three medical events #1A, #3A, and #4A listed in occurrence order table 520A (see FIG. 6). In particular, medical events #3C and #4A correspond to discrepancy events.

[0100] According to "Definition 2" shown in area 820A, medical event #1C is "bleeding," medical event #2C is "blood transfusion," medical event #3C is "blood pressure stabilization," and medical event #4C is "surgical procedure to stop bleeding." The four medical events #1C to #4C according to "Definition 2" correspond to the four medical events #1A, #3A, #4A, and #6A listed in occurrence order table 530A (see FIG. 7). In particular, medical events #4C and #6A correspond to discrepancy events.

[0101] "Definition 1" shown in area 810B corresponds to "Definition 1" shown in area 810A. "Definition 2" shown in area 820B corresponds to "Definition 2" shown in area 820A. The operator can register any desired comments in the blank spaces in areas 810B and 820B. For example, the operator may register the reason why "Definition 1" and "Definition 2" were registered as the correct order. This allows the operator to refer to the registered comment if the same discrepancy occurs. The registration function 115 may statistically analyze the content registered in the correct order table 800. Through this analysis, the registration function 115 can calculate analysis results that are useful for revising the treatment guideline 210 or as material for presentations at academic conferences.

[0102] 12 is a diagram showing an example of the process of generating an incident report according to this embodiment. This example shows a report image 900. The report image 900 may be displayed on the display 44.

[0103] Report image 900 includes the following statement: "On X month Y day, at approximately S time T minute, the dosage was instructed to be V1 mL, but V2 mL was mistakenly administered to patient A." By checking report image 900, the operator can easily understand the discrepancy between the expected dosage of V1 mL and the dosage of V2 mL administered to patient A.

[0104] The report image 900 may display the content of the discrepancy event as a list or text. The report image 900 may emphasize the content of the discrepancy event in various ways (e.g., font change, highlight display). The report image 900 may have a function (e.g., GUI button) that allows the operator to confirm or edit the content. The report image 900 may have a function (e.g., input box) that allows the operator to input comments.

[0105] According to the present embodiment described above, medical personnel collect event records ER related to multiple medical events ME1 that occurred in a patient through the collection device 30. The medical information processing device 1 acquires a first order OR1, which is the order in which the multiple medical events ME1 occurred, based on the collected event records ER. Meanwhile, the medical information processing device 1 acquires a second order OR2, which is the order in which multiple medical events ME2 required to treat the patient are to occur, based on the treatment guideline 210 in the treatment guideline DB2. If the first order OR1 does not match the second order OR2, the medical information processing device 1 detects multiple medical events ME3 that do not match between the first order OR1 and the second order OR2. The medical information processing device 1 generates a report containing details related to the multiple medical events ME3.

[0106] Therefore, at the scene of an emergency, medical personnel simply collect the event records ER through the collection device 30. The medical information processing device 1 automatically generates an incident report based on the collected event records ER, thereby shortening or eliminating the time it takes medical personnel to create the incident report. The medical information processing device 1 can generate the incident report in real time based on the event records ER collected in real time. The medical information processing device 1 can reduce or minimize the frequency of defects (e.g., discrepancies, omissions) in the incident report.

[0107] (Variation) The medical information processing device 1 may analyze the character string written in the incident report to detect contextual discrepancies in the character string. The medical information processing device 1 may output the detected discrepancies as an alert in real time while the patient is being treated. The medical information processing device 1 may confirm that the medical personnel have not taken action despite the alert being output. The medical information processing device 1 may detect discrepancies based on the medical personnel's past performance (e.g., treatment time, time to take action).

[0108] The medical personnel may send a cancellation instruction to cancel the erroneous medical instruction to the medical information processing device 1 via the collection device 30, the IoT device, or the operation terminal 4. The medical information processing device 1 may confirm that the medical personnel has not implemented the erroneous medical instruction related to the cancellation instruction.

[0109] According to at least one of the embodiments described above, it is possible to assist in creating an incident report.

[0110] 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, substitutions, modifications, and combinations of embodiments can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, as well as within the scope of the invention and its equivalents as defined in the claims. [Explanation of symbols]

[0111] 1 Medical information processing device 21 Guideline DB 22 Patient information DB 23 Test Information DB 4 Operation terminal 11,41 Processing circuit 12,42 memory 13,45 Communication IF 30 Collection Equipment 31 Camera 32. Mike 33 Leader 43 Input IF 44 Display 100 Medical Information Processing System 111,411 Acquisition Function 112 Detection Function 113 Generation function 114 Confirmation Function 115 Registration Function 116,413 System Control Functions 210 Treatment Guidelines 220 Patient Information 230 Test Information 412 Display Control Function 510A, 520A, 530A, 540A, 550A Generation Order Table 510B, 520B, 530B, 540B, 550B Occurrence timeline 511A, 521A, 531A, 541A, 551A, 611A, 612A, 613A, 621A, 622A, 623A, 631A, 810A, 810B, 820A, 820B Area 610A, 620A, 630A Definition Sequence Table 610B, 620B, 630B Definition Order Timeline 700A Check Item Table 700B Checklist Table 800 Correct Order Table 900 Report Images

Claims

1. an acquisition unit that acquires a first order, which is an order of a plurality of first events that have occurred to a patient, and a second order, which is an order of a plurality of second events that are required to treat the patient; a detection unit that detects a plurality of third events that do not match between the first order and the second order when the first order does not match the second order; a generation unit that generates a report that describes content related to the plurality of third events; A medical information processing device comprising:

2. the plurality of first events include at least one of a change in the patient's condition, issuance of a medical instruction for the patient, and performance of a medical procedure for the patient; The medical information processing device according to claim 1 .

3. the acquisition unit acquires an event record that records the plurality of first events; obtaining the first order by chronologically arranging the first events based on the time at which each of the first events occurred in the event record; The medical information processing device according to claim 1 .

4. the acquisition unit acquires the second order from a treatment guideline indicating a standard treatment policy. The medical information processing device according to claim 1 .

5. a confirmation unit that confirms the contents of confirmation items related to the plurality of first events by analyzing an event record that records the plurality of first events; The medical information processing device according to claim 1 .

6. The confirmation items include whether medical instructions for the patient have been issued based on the patient's condition. The medical information processing device according to claim 5 .

7. a registration unit that registers the first order as a correct order in response to an operation by an operator, the detection unit does not detect the plurality of third events when the first order does not match the second order and the first order is registered as the correct order. The medical information processing device according to claim 1 .

8. the registration unit registers a comment in association with the first order registered as the correct order in response to another operation from the operator. The medical information processing device according to claim 7 .

9. obtaining a first order of a plurality of first events occurring to a patient and a second order of a plurality of second events required to treat the patient; If the first order does not match the second order, detecting a plurality of third events that are mutually inconsistent between the first order and the second order; generating a report describing the plurality of third events; Medical information processing method.

10. On the computer, an acquisition function for acquiring a first sequence, which is a sequence of a plurality of first events occurring to a patient, and a second sequence, which is a sequence of a plurality of second events required to treat the patient; a detection function for detecting a plurality of third events that are mutually inconsistent between the first order and the second order when the first order does not match the second order; a generation function for generating a report that describes the content related to the plurality of third events; A medical information processing program that makes this possible.

Images