JP2016123575A - Management device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To suppress occurrence of incident.SOLUTION: A management device of an embodiment includes a collection part, an association part, and a display control part. The collection part collects incident information corresponding to a clinical work flow of an execution target, from a first storage unit storing the incident information where information on incident occurring in past times and the clinical work flow where the incident occurs, are associated with each other. The association part associates the incident information collected by the collection part, with the clinical work flow of the execution target. The display control part displays the incident information associated with the clinical work flow of the execution target.SELECTED DRAWING: Figure 3

Description

  Embodiments described herein relate generally to a management apparatus.

  2. Description of the Related Art Conventionally, there is known a medical image diagnostic apparatus that executes each process in the order of processes indicated by the clinical workflow based on the clinical workflow arranged in the order in which the processes in which the business contents are defined are executed.

  Here, an event (incident) unexpected by a user such as a doctor or engineer may occur while the medical image diagnostic apparatus is executing each process based on a clinical workflow.

JP 2011-30583 A JP 2011-181084 A

  The problem to be solved by the present invention is to provide a management apparatus capable of suppressing the occurrence of incidents.

  The management device of the embodiment includes a collection unit, an association unit, and a display control unit. The collection unit collects incident information corresponding to a clinical workflow to be executed from a first storage device that stores information related to incidents that occurred in the past and incident information in which the clinical workflow in which the incident occurred is associated. To do. The association unit associates incident information collected by the collection unit with the clinical workflow to be executed. The display control unit displays incident information associated with the clinical workflow to be executed.

FIG. 1 is a diagram illustrating a configuration example of a management system to which the management apparatus according to the first embodiment is applied. FIG. 2 is a diagram illustrating an example of a data structure of incident information. FIG. 3 is a block diagram illustrating a configuration example of the management apparatus and the workflow management system according to the first embodiment. FIG. 4 is a diagram illustrating an example of incident information in which the clinical workflow ID “coronary subtraction” to be executed is included in the item “clinical workflow”. FIG. 5 is a diagram illustrating an example of a clinical workflow to be executed. 6 is a diagram for explaining a case where the incident information illustrated in the example of FIG. 4 is transmitted to the incident application unit and the clinical workflow illustrated in the example of FIG. 5 is transmitted. FIG. 7 is a diagram for explaining an example when risk contents are associated with processes. FIG. 8 is a diagram for explaining an example in which statistical information is associated with a process. FIG. 9 is a diagram illustrating an example in which a comment “XX check” is associated with a process, and a comment “ΔΔ check” is associated with a process. FIG. 10 is a diagram illustrating an example in which incident information is displayed as Tips. FIG. 11 is a diagram illustrating an example of displaying incident information as Tips. FIG. 12 is a diagram for explaining an example in which incident information associated with a clinical workflow is displayed together with the clinical workflow on the display device of the workflow management system. FIG. 13 is a diagram for explaining an example in which incident information associated with a clinical workflow is displayed together with the clinical workflow on the display device of the workflow management system. FIG. 14 is a block diagram illustrating a configuration example of a management apparatus according to the second embodiment. FIG. 15 is a diagram illustrating an example of a partial data structure of the clinical flow DB according to the second embodiment. FIG. 16 is a diagram illustrating another example of the data structure of the clinical flow DB according to the second embodiment. FIG. 17 is a flowchart for explaining an example of the clinical workflow change process according to the second embodiment.

  Hereinafter, embodiments of a management device will be described in detail with reference to the accompanying drawings.

(First embodiment)
First, the configuration of the management device according to the first embodiment will be described. FIG. 1 is a diagram illustrating a configuration example of a management system to which the management apparatus according to the first embodiment is applied. As shown in FIG. 1, the management system 1 according to the first embodiment includes a center server 90 and a hospital system 91. The center server 90 and the hospital system 91 are connected so as to be able to communicate with each other via the network 92.

  The center server 90 is a server that centrally manages incidents (phenomena) that occur during the execution of clinical workflow in the hospital system 91 and a plurality of hospital systems other than the hospital system 91. For example, the center server 90 has an incident DB (Data Base) 90a, collects incidents occurring in a plurality of hospital systems other than the hospital system 91 and the hospital system 91 in real time, and information on the collected incidents And the collected incident information are registered in the incident DB 90a. The incident DB 90a is an example of a first storage unit.

  FIG. 2 is a diagram illustrating an example of a data structure of incident information. As shown in the example of FIG. 2, incident information includes “date and time”, “type”, “event”, “risk”, “clinical workflow”, “corresponding process”, “corresponding department”, “corresponding condition”, “ Each item includes “comment” and “importance”. The item “date and time” includes the date and time when the incident occurred. The item of “Type” includes the type of incident. The item of “event” includes the contents of the incident. The item “risk” includes the content of the risk caused by the occurrence of an incident. The item “clinical workflow” includes an ID (Identification) of a clinical workflow in which an incident has occurred. The item of “corresponding process” includes the ID of the process of the clinical workflow in which the incident has occurred. The item “corresponding department” includes the department in which the incident occurred. The item “applicable condition” includes a condition in which an incident has occurred. The item “comment” includes a comment such as a method for dealing with a risk caused by an incident. The “importance” item includes an importance indicating the magnitude of the risk caused by the incident.

  In other words, the incident information includes the date and time when the incident occurred, the type and content of the incident, the risk arising from the occurrence of the incident, the department in which the incident occurred, the conditions under which the incident occurred, the target method of the risk arising from the incident, and the like. The information relating to the incident including the importance indicating the magnitude of the risk caused by the incident is associated with the clinical workflow in which the incident has occurred and the clinical workflow process in which the incident has occurred.

  Moreover, it can be said that the risk caused by the occurrence of an incident has an influence on the execution of the clinical workflow in which the incident occurs when the incident occurs. Moreover, it can be said that the risk coping method is a coping method for this influence. Further, the importance indicating the magnitude of the risk caused by the incident can be said to be an influence indicating the degree of influence of the incident on the execution of the clinical workflow when the incident occurs.

  Incident information having a data structure as shown in the example of FIG. 2 is registered in the incident DB 90a. Hereinafter, the center server 90 has an incident DB 90a, and incident DB 90a is registered with incidents that occur during the execution of clinical workflow in the hospital system 91 and a plurality of hospital systems other than the hospital system 91. As will be described, the incident DB 90a is not limited to this. For example, the incident DB 90a may be disclosed externally in the form of cloud computing after giving access authority to a specific user so that the specific user can access it from anywhere. An incident DB 90a may be provided in the hospital system 91. When the incident DB 90a is provided in the in-hospital system 91, only incident information related to incidents occurring in the hospital in which the in-hospital system 91 is provided is registered in the incident DB 90a.

  In addition, the incident information may include not only information related to the incident that actually occurred, but also information related to a so-called near-miss incident that was about to occur. In addition, the incident information may include information on an incident that causes a disadvantage in the hospital (for example, an incident that requires extra costs), although the patient (subject) has no disadvantage.

  In addition, the incident information may include not only information obtained as a result of text conversion but also an image and sound when an actual incident occurs. Further, the incident information may include a handwritten sentence converted into a PDF (Portable Document Format). Further, the incident information may include a path of this file for reading a file in which various contents as shown in the example of FIG. 2 are described.

  In addition, the incident information may include physical information of a patient to be examined, characteristics of a member such as a medical employee who is involved in the examination (for example, a medical company witnessed when an incident occurs), and the like.

  The in-hospital system 91 is a system in one hospital, and includes a management apparatus 10, an X-ray CT (Computed Tomography) apparatus 21, an MRI (Magnetic Resonance Imaging) apparatus 22, a workstation (WS) 23, EMR (Electronic Medical Records) 24, which is an electronic medical record, and a workflow management system 25.

  The in-hospital system 91 includes not only medical image diagnostic apparatuses such as the X-ray CT apparatus 21 and the MRI apparatus 22, but also other types of medical image diagnostic apparatuses (for example, an ultrasonic diagnostic apparatus and a nuclear medicine diagnostic apparatus). You may prepare.

  For example, the workstation 23 has a function of analyzing a medical image of a patient obtained by a medical image diagnostic apparatus such as the X-ray CT apparatus 21 or the MRI apparatus 22 and supporting the creation of a report.

  The EMR 24 is an electronic medical record, and various patient information and the like are registered in the EMR 24.

  The workflow management system 25 is a system that determines a clinical workflow according to the purpose of the examination, and is, for example, a single server.

  The management device 10 is a device that manages incident information displayed on a device that executes a clinical workflow (an X-ray CT device 21, an MRI device 22, a workstation 23, or the like).

  FIG. 3 is a block diagram illustrating a configuration example of the management apparatus and the workflow management system according to the first embodiment. As shown in the example of FIG. 3, the workflow management system 25 includes a clinical flow determination unit 25a and a clinical flow DB 25b.

  The clinical flow DB 25b stores a plurality of clinical workflows associated with the purpose of the examination. That is, the clinical flow DB 25b stores an optimum clinical workflow in association with the purpose of the examination.

  The clinical flow determination unit 25a acquires a clinical workflow corresponding to the purpose of the test to be performed from the clinical flow DB 25b, and determines the acquired clinical workflow as an execution target clinical workflow. Then, the clinical flow determination unit 25a transmits the clinical workflow to be executed to the incident application unit 10b described later. Further, the clinical flow determination unit 25a transmits the ID of the clinical workflow to be executed to the incident collection unit 10a described later.

  As illustrated in the example of FIG. 3, the management apparatus 10 includes an incident collection unit 10a, an incident application unit 10b, and an incident display control unit 10c.

  The incident collection unit 10a acquires incident information corresponding to the clinical workflow to be executed from the incident DB 90a. For example, when the incident collection unit 10a receives the ID “coronary artery subtraction” of the clinical workflow to be executed transmitted from the clinical workflow determination unit 24a, the incident collection unit 10a receives the ID “coronary artery subtraction” from all the records in the incident DB 90a. ”Is searched. Then, the incident collection unit 10a acquires a record obtained as a result of the search as incident information corresponding to the clinical workflow to be executed.

  FIG. 4 is a diagram illustrating an example of incident information in which the clinical workflow ID “coronary subtraction” to be executed is included in the item “clinical workflow”. In the incident information shown in the example of FIG. 4, the “event” item includes “increased breathing confirmation” that is the content of the incident, and the “risk” item includes “re-examination” "Exposure" is included, and the item "Clinical workflow" includes the ID "Coronary artery subtraction" of the clinical workflow where the incident occurred, and the item "Corresponding process" includes the ID of the process of the clinical workflow where the incident occurred " “Ultra low-dose positioning scan” is included, and “Comment” includes a comment “Let's check the patient's breathing rate before imaging!” Such as a target method of risk caused by the incident.

  If the incident information registered in the incident DB 90a includes the physical information of the patient to be examined and the characteristics of members such as medical workers involved in the examination, the incident collection unit 10a In addition to the ID of the clinical workflow to be performed transmitted from the determination unit 24a, the physical information of the patient to be examined and the characteristics of members such as medical employees who are involved in the examination are used as keys to record all records in the incident DB 90a. You may search the corresponding record from the inside. Thereby, more appropriate incident information can be narrowed down and acquired.

  Moreover, after acquiring incident information, the incident collection part 10a may acquire the various statistical information regarding the incident which incident information shows. For example, the incident collection unit 10a may acquire statistical information regarding an incident from the EMR 24 or EHR (Electronic Health Records) (not shown). Here, the EHR is a database in which various medical information such as patient information shared not only between departments in a hospital where the in-hospital system 91 is provided but also among a plurality of hospitals is registered. . As an example of statistical information regarding incidents, there are the number of incidents for each hospital and time period in a specific period, and the number of incidents for the same patient.

  Then, the incident collection unit 10a transmits the acquired incident information to the incident application unit 10b. The incident collection unit 10a is an example of a collection unit.

  The incident application unit 10b associates the incident information transmitted from the incident collection unit 10a with the clinical workflow to be executed transmitted from the clinical flow determination unit 25a. The incident application unit 10b is an example of an association unit.

  FIG. 5 is a diagram illustrating an example of a clinical workflow to be executed. The clinical workflow 30 shown in the example of FIG. 5 is a clinical workflow for the purpose of examining a patient's coronary artery. The clinical workflow 30 includes an analysis for extracting a calcified region of a patient's coronary artery from a CT image obtained by imaging with an ultra-low dose X-ray and calculating an index (score) based on the extracted calcified region. Further, the clinical workflow 30 subtracts the CT image before the contrast medium is injected from the CT image after the contrast medium is injected in order to obtain an image in which the coronary artery of the patient is clearly depicted. Includes processing for analyzing a clearly rendered image. The clinical workflow 30 is performed mainly by the X-ray CT apparatus 21. The ID of the clinical workflow 30 is “coronary artery subtraction”.

  In the clinical workflow 30, the processes 31 to 41 in which the business contents are defined are arranged in the order of execution. The process 31 is a process in which contents relating to imaging of a two-dimensional scano image of a patient as a positioning image are defined. The process 32 is a process in which the contents related to CT image capturing are defined at an ultra-low dose comparable to that of positioning imaging. The process 33 is a process in which the contents relating to the calculation of the calcification score of the patient's coronary artery are defined. The process 34 is a process in which contents relating to the analysis of the calculated calcification score are defined.

  The process 35 is a process in which contents relating to the CT image of the region of interest of the patient before the projection agent is administered to the patient are defined. The process 36 is a process related to monitoring whether or not the projection agent has reached the patient's region of interest (coronary artery). The process 37 is a process in which contents relating to the imaging of the CT image of the region of interest when the projection agent reaches the region of interest of the patient are defined. Process 38 includes the phase of the CT image of the region of interest of the patient before administration of the projection agent imaged in multiple phases, and the interest in the state where the projection agent has reached the region of interest of the patient imaged in multiple phases. This is a process in which the contents regarding the determination of the pair with the phase of the CT image of the region are defined. Process 39 subtracts the CT image of the region of interest of the patient prior to administration of the phased projection agent from the CT image of the region of interest with the projection agent reaching the region of interest of the patient whose phase has been determined. A process with defined content for traction. The process 40 is a process in which contents relating to image processing for a coronary artery image obtained by subtraction are defined. The process 41 is a process in which the contents relating to the creation of the coronary artery calcification report are defined.

  Processes 31 to 40 are executed by the X-ray CT apparatus 21, and process 41 is executed by the workstation 23. Note that the workstation 23 may execute the process 34.

  Here, the case where the incident information shown in the example of FIG. 4 is transmitted from the incident information collection unit 10a to the incident application unit 10b and the clinical workflow 30 shown in the example of FIG. . FIG. 6 is a diagram for explaining a case where the incident information illustrated in the example of FIG. 4 is transmitted to the incident application unit 10b and the clinical workflow illustrated in the example of FIG. 5 is transmitted.

  The incident application unit 10b acquires the content “increased breath confirmation” of the incident included in the “event” item of the incident information illustrated in the example of FIG. Further, the incident application unit 10b acquires the process ID “ultra-low dose positioning Scan” included in the “corresponding process” item of the incident information illustrated in the example of FIG. Further, the incident application unit 10b obtains a comment “Make sure to check the patient's breathing rate before imaging!” Of the risk countermeasure method included in the “comment” item of the incident information shown in the example of FIG. . Then, as illustrated in FIG. 6, the incident application unit 10 b associates the acquired incident content “excessive respiratory confirmation” 42 with the process 32 indicated by the acquired process ID “ultra low dose positioning Scan”. In addition, the incident application unit 10b associates the acquired comment “Be sure to check the patient's respiratory rate before imaging!” 43 with the process 32.

  In addition, the incident application unit 10b may associate the content of the risk caused by the occurrence of the incident included in the item “risk” of the incident information with the process. FIG. 7 is a diagram for explaining an example when risk contents are associated with processes. For example, the “Comment” item in the incident information includes a comment “Relate β-blocker” in the risk management method, and the “Risk” item includes the risk content “CTA becomes difficult to shoot”. The case will be described.

  In such a case, the incident application unit 10b acquires the comment “associate β-blocker” included in the “comment” item of the incident information, and the content of the risk included in the “risk” item “CTA becomes difficult to capture. Is obtained. Then, as shown in the example of FIG. 7, the incident application unit 10 b associates the comment “associate β blocker” and the risk content “difficult to shoot with CTA” 44 with the process 32.

  The incident application unit 10b may associate the above statistical information acquired by the incident collection unit 10a with the process. FIG. 8 is a diagram for explaining an example in which statistical information is associated with a process. For example, a case will be described in which the incident collection unit 10a acquires the number of occurrences of a target incident for each hospital in a specific period and the number of occurrences of the target incident in the same patient.

  In such a case, the incident application unit 10b associates, with the process 32, an image 45 that indicates the number of occurrences for each hospital in the specific period of the target incident. Further, the incident application unit 10b associates the number of occurrences 46 of the target incident in the same patient with the process 32.

  In addition, as illustrated in the example of FIG. 9, the case where the comment “XX confirmation” 47 is associated with the process 34 and the comment “ΔΔ confirmation” 48 is associated with the process 40 is described. To do. In this case, the processes 31 to 37 are executed by the X-ray CT apparatus of the hospital A, and the processes 38 to 41 are executed by the workstation of the hospital B which is the interpretation center. In the present embodiment, when the X-ray CT apparatus of Hospital A executes the process 34, the comment “XX confirmation” 47 is displayed on the display device of the X-ray CT apparatus by the incident display control unit 10c described later. . In this embodiment, when the workstation of hospital B executes the process 40, the comment “ΔΔ confirmation” 48 is displayed on the display device of the workstation by the incident display control unit 10c described later.

  The incident application unit 10b may transmit the clinical workflow associated with the incident information to the workflow management system 25 in order to store the clinical workflow associated with the incident information in the clinical flow DB 25b. When the clinical workflow associated with the incident information is received, the clinical flow determination unit 25a of the workflow management system 25 stores the received clinical workflow in the clinical flow DB 25b. As a result, when the incident application unit 10b acquires the clinical workflow for which this clinical workflow is to be executed again from the workflow management system 25, the incident corresponding to the difference from the last association of the incident information to this clinical workflow until the present time. Information may be associated with this clinical workflow. Thereby, since it is not necessary to associate the incident information with the clinical workflow from the beginning, the processing time required for the association can be shortened.

  The incident display control unit 10c displays incident information associated with the clinical workflow to be executed.

  For example, the incident display control unit 10c displays the incident information associated with the process being executed on the display unit of the device that is executing this process. Here, as shown in the example of FIG. 6, the process content 32 is associated with the incident content “respiratory hyperconfirmation” 42 and the comment “Be sure to check the patient's respiration rate before imaging!” 43 A case where the line CT apparatus 21 is executing the process 32 will be described. In this case, the incident display control unit 10c causes the display device of the X-ray CT apparatus 21 to display the comment “Be sure to check the patient's respiratory rate before imaging!”. FIG. 10 is a diagram illustrating an example in which incident information is displayed as Tips. For example, an application for displaying received data as Tips is resident in the display device of the X-ray CT apparatus 21, and the incident display control unit 10 c includes a comment “The patient's respiratory rate before imaging”. Please be sure to check! ” Then, as shown in the example of FIG. 10, the application displays Tips “Be sure to check the patient's respiratory rate before imaging!” 61 on the screen 60 of the display device. Thereby, the user of the X-ray CT apparatus 21 that is executing the process 32 can be made aware of how to deal with the risk due to the incident that occurs. Therefore, it is possible to cause an appropriate person to grasp the occurrence of risk and the method of dealing with risk at an appropriate timing. Therefore, the occurrence of incidents can be suppressed.

  In addition, a case will be described in which the comment “Let the patient speak!” Is associated with the process 40 and the X-ray CT apparatus 21 is executing the process 40. In this case, the incident display control unit 10c displays the comment “Let's speak to the patient!” On the display device of the X-ray CT apparatus 21. FIG. 11 is a diagram illustrating an example of displaying incident information as Tips. For example, the incident display control unit 10c transmits a comment “Let's speak to the patient!” To the application that displays the received data as Tips. Then, as shown in the example of FIG. 11, the application displays Tips “Let's speak to the patient!” 62 on the screen 60 of the display device. Thereby, the user of the X-ray CT apparatus 21 that is executing the process 40 can be made aware of how to deal with the risk due to the incident that occurs. Therefore, an appropriate person can be made aware of the occurrence of risk and the target method of risk at an appropriate timing. Therefore, the occurrence of incidents can be suppressed.

  Further, the incident display control unit 10c may cause the display device of the workflow management system 25 to display incident information associated with the clinical workflow together with the clinical workflow. FIG. 12 is a diagram for explaining an example in which incident information associated with a clinical workflow is displayed together with the clinical workflow on the display device of the workflow management system. For example, the incident display control unit 10c may display the comment 55 associated with the process 51 on the display device of the workflow management system 25 together with the clinical workflow 50 in which the processes 51 to 54 are arranged in order. As a result, the administrator of the workflow management system can grasp the risk handling method and the like due to the incident that has occurred, and can communicate the risk handling method and the like to the operator of the apparatus that is executing the process.

  In addition, the incident display control unit 10c displays the incident information as a user or phase when an incident whose various types of information are indicated by the incident information affects a process after the process associated with the incident information. Regardless of the display, it may be displayed with priority.

  Moreover, the incident display control part 10c may change the display mode of the incident information to display according to the importance contained in incident information. For example, the incident display control unit 10c increases the font size of the incident information to be displayed or brings the color of the incident information to be displayed closer to a dark red color so that the greater the importance, the easier the visual recognition is. Also good. The incident display control unit 10c may reduce the font size of the incident information to be displayed or reduce the color of the incident information to be displayed to light black as the importance is small. Thereby, appropriate display according to the importance can be performed.

  Further, the incident display control unit 10c may change the incident information to be displayed according to the skill level of the operation of the user device. For example, the management apparatus 10 holds a defined DB in which the skill level of a user who has placed an inspection order is registered as a score, and the incident display control unit 10c acquires the skill level from this DB. Here, it seems that it does not make much sense to make a highly skilled user confirm incident information with low importance. Therefore, the incident display control unit 10c may not display incident information whose importance is equal to or lower than a predetermined standard on a display device of a device operated by a highly skilled user.

  In addition, the incident display control unit 10c may display at least one of a risk caused by the occurrence of an incident, a risk handling method, and statistical information about the incident on a display device of a device that is executing the process.

  FIG. 13 is a flowchart for explaining an example of the incident information display control process according to the first embodiment. As illustrated in FIG. 13, the clinical flow determination unit 25a acquires an examination order (step S101).

  Then, the clinical flow determination unit 25a acquires a clinical workflow corresponding to the purpose of the test to be performed indicated by the test order from the clinical flow DB 25b, and determines the acquired clinical workflow as a clinical workflow to be executed. Then, the clinical flow determination unit 25a transmits the clinical workflow to be executed to the incident application unit 10b, and transmits the ID of the clinical workflow to be executed to the incident collection unit 10a (Step S102).

  When the incident collection unit 10a receives the ID of the clinical workflow to be executed transmitted from the clinical workflow determination unit 24a, the incident collection unit 10a searches the records in which the received ID is registered from all the records in the incident DB 90a ( Step S103).

  Then, the incident collection unit 10a acquires the record obtained as a result of the search as incident information corresponding to the clinical workflow to be executed (step S104).

  The incident application unit 10b then associates the incident information transmitted from the incident collection unit 10a with the clinical workflow to be executed transmitted from the clinical flow determination unit 25a (step S105).

  Then, the incident display control unit 10c displays the incident information associated with the clinical workflow to be executed (Step S106), and ends the incident information display control process.

  The management device 10 according to the first embodiment has been described above. According to the management device 10, as described above, the occurrence of incidents can be suppressed.

(Second Embodiment)
Next, a management apparatus according to the second embodiment will be described. In addition, about the structure similar to 1st Embodiment, the same code | symbol may be attached | subjected and description may be abbreviate | omitted. FIG. 14 is a block diagram illustrating a configuration example of a management apparatus according to the second embodiment. As shown in the example of FIG. 14, the management device 80 according to the second embodiment is further provided with an incident monitoring unit 80a, a clinical flow control unit 80b, and a monitoring condition DB 80c, according to the first embodiment. Different from 10. Also, the point that the log DB 99 is connected to the management device 80 is different from the first embodiment. Here, the management device 80 can execute all the processes that can be executed by the management device 10 according to the first embodiment.

  The log DB 99 is a database in which logs generated by devices such as various medical image diagnostic apparatuses and workstations included in a plurality of hospital systems other than the hospital system 91 and the hospital system 91 are registered in real time. is there. For example, a server (not shown) collects logs generated in a plurality of hospital systems in real time and registers the collected logs in the log DB 99 one after another.

  The log will be explained. For example, there are a log that is generated when a certain incident occurs, and a log that is generated a predetermined time before a certain incident occurs, such as a few seconds or a few minutes. That is, when it is desired to detect that an incident has occurred, the presence or absence of a log generated with the occurrence of this incident may be monitored. Therefore, in the monitoring condition DB 80c, a log that is generated when the detection target incident occurs and a log that is generated a predetermined time before the detection target incident occurs are registered by the user. In this way, that is, when the incident monitoring control unit 80a receives an instruction to register a log from the user, the incident monitoring control unit 80a registers a log as a monitoring condition in the monitoring condition DB 80c according to the instruction. Thus, receiving an instruction from a user and registering a log as a monitoring condition in the monitoring condition DB 80c is referred to as setting an incident monitoring condition in the monitoring condition DB 80c.

  The incident monitoring unit 80a detects the occurrence of an incident to be detected. For example, the incident monitoring unit 80a repeatedly determines whether or not a log registered in the monitoring condition DB 80c is newly registered in the log DB 99. Here, the case where the incident monitoring unit 80a determines that the log registered in the monitoring condition DB 80c is newly registered in the log DB 99 will be described. If the newly determined log is a log generated at the timing when the detection target incident occurs, the incident monitoring unit 80a detects the type of the detection target incident that has occurred.

  On the other hand, when the newly determined log is a log generated a predetermined time before the timing of occurrence of the incident to be detected, the incident monitoring unit 80a detects the detection target to be generated. Detect the type of incident.

  When the incident monitoring unit 80a detects the occurrence of the incident and the type of the incident that has occurred, the clinical flow control unit 80b reads from the clinical flow DB 25b the purpose of the test being performed and the pattern of the type of incident that has occurred. A clinical workflow (recommended clinical workflow) corresponding to (incident occurrence pattern) is acquired.

  Here, the clinical flow DB 25b according to the second embodiment stores in advance a plurality of combinations of incident occurrence patterns and clinical workflows optimal for the incident occurrence patterns for the same examination purpose. FIG. 15 is a diagram illustrating an example of a partial data structure of the clinical flow DB 25b according to the second embodiment. As shown in the example of FIG. 15, the clinical flow DB 25 b has the same type of incident “XXX”, the incident of the type “incident 1”, the incident of the type “incident 2”, and other A plurality of combinations of occurrence patterns of types of incidents and optimal clinical workflows for the occurrence patterns are stored. Here, the optimal clinical workflow for the incident occurrence pattern refers to a clinical workflow that minimizes the risk due to the incident that has occurred.

  In the example of FIG. 15, “X” indicates that the corresponding type of incident has not occurred, and “◯” indicates that the corresponding type of incident has occurred. A clinical workflow 81 is registered in the first record of the clinical flow DB 25b shown in the example of FIG. The clinical workflow 81 includes two processes of simple imaging, contrast imaging, reconstruction, imaging diagnosis, and reporting. The clinical workflow 82 is registered in the second record. The clinical workflow 82 includes a simple imaging process, a contrast imaging process, a reconstruction process, a diagnostic imaging process, and a reporting process. A clinical workflow 83 is registered in the third record. The clinical workflow 83 includes a simple imaging process, a contrast imaging process, a reconstruction process, two diagnostic imaging processes, and a reporting process. These clinical workflows 81 to 83 have the same examination purpose but different incident occurrence patterns.

  Returning to FIG. 14, the clinical flow control unit 80 b displays the acquired recommended clinical workflow on the display device of the device that is executing the process. Then, the clinical flow control unit 80b changes the clinical workflow being executed to the recommended clinical workflow, and causes the device that is executing the process to execute the recommended clinical workflow instead of the clinical workflow being executed. Thereby, even if an incident occurs, a clinical workflow that minimizes the risk of the incident is executed, so that the occurrence of the incident can be suppressed.

  In addition, when a plurality of recommended clinical workflows are acquired, the clinical flow control unit 80b displays the plurality of recommended clinical workflows on the display device of the device that is executing the process, and selects the recommended clinical workflow to be executed by the user. You may let them.

  Here, the data structure of the clinical flow DB 25b according to the second embodiment is not limited to the data structure shown in the example of FIG. FIG. 16 is a diagram illustrating another example of the data structure of the clinical flow DB 25b according to the second embodiment. As shown in the example of FIG. 16, the clinical flow DB 25b has an incident occurrence pattern, a clinical workflow optimal for the incident occurrence pattern, and a user who requests an examination (examination requesting physician) for the same examination purpose. ) Are stored in advance. In FIG. 16, in addition to the purpose of the examination, even if the incident occurrence pattern is the same, the examination requesting physician “AAA”, the examination requesting physician “BBB”, and the examination requesting physician “CCC” are recommended. The case where clinical workflows are different is illustrated.

  When the data structure of the clinical flow DB 25b according to the second embodiment has a data structure as shown in the example of FIG. 16, the clinical flow control unit 80b will explain an example of a method for acquiring a recommended clinical workflow. The clinical flow control unit 80b acquires from the clinical flow DB 25b the purpose of the test being performed, the pattern of the incident that has occurred, and the recommended clinical workflow corresponding to the test requesting physician who requested the test.

  FIG. 17 is a flowchart for explaining an example of the clinical workflow change process according to the second embodiment. As shown in FIG. 17, in response to an instruction from the user, incident monitoring conditions are set in the monitoring condition DB 80c (step S201).

  Then, the incident monitoring unit 80a starts monitoring whether or not the log set as the monitoring condition is newly registered in the log DB 99 (step S202).

  Then, medical image diagnostic apparatuses such as the X-ray CT apparatus 21 and the MRI apparatus 22, and apparatuses such as workstations start (restart) the examination (step S203).

  The incident monitoring unit 80a determines whether a detection target incident has occurred by determining whether the log set as the monitoring condition is newly registered in the log DB 99 (step S204). .

  When the log set as the monitoring condition is newly registered in the log DB 99 (step S204; Yes), the clinical flow control unit 80b has generated the purpose of the test being performed and the clinical flow from the clinical flow DB 25b. The recommended clinical workflow corresponding to the incident type pattern is acquired (step S208).

  The clinical flow control unit 80b displays the acquired recommended clinical workflow on the display device of the device that is executing the process (step S209). Then, the clinical flow control unit 80b changes the clinical workflow that is being executed to the recommended clinical workflow, and causes the device that is executing the process to execute the recommended clinical workflow instead of the clinical workflow that is being executed (step S210). The process returns to step S201.

  On the other hand, when the log set as the monitoring condition is not newly registered in the log DB 99 (step S204; No), the incident monitoring unit 80a determines whether or not to end the inspection (step S205). . If the inspection is not terminated (step S205; No), the incident monitoring unit 80a returns to step S204. On the other hand, when the inspection is ended (step S205; Yes), the incident monitoring unit 80a ends the inspection (step S206). Then, the incident monitoring unit 80a finishes monitoring whether the log set as the monitoring condition is newly registered in the log DB 99, that is, monitoring the occurrence of the incident to be detected (step S207), and the clinical workflow End the change process.

  The management device 80 according to the second embodiment has been described above. According to the management device 80, the occurrence of an incident can be suppressed as described above.

  In the above-described embodiment, each component of each illustrated device is functionally conceptual and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. Furthermore, all or a part of each processing function performed in each device may be realized by a CPU and a program that is analyzed and executed by the CPU, or may be realized as hardware by wired logic.

  In addition, the management method described in the above embodiment can be realized by executing a management program prepared in advance on a computer such as a personal computer or a workstation. This management program can be distributed via a network such as the Internet. The management program is recorded on a computer-readable non-transitory recording medium such as a hard disk, a flexible disk (FD), a CD-ROM, an MO, a DVD, a flash memory such as a USB memory and an SD card memory. It can also be executed by being read from a non-transitory recording medium by a computer.

  According to the management device of at least one embodiment described above, the occurrence of an incident can be suppressed.

  Although several embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are also included in the invention described in the claims and the equivalents thereof.

DESCRIPTION OF SYMBOLS 10 Management apparatus 10a Incident collection part 10b Incident application part 10c Incident display control part

Claims (7)

A collection unit that collects incident information corresponding to a clinical workflow to be executed from a first storage device that stores information relating to incidents that occurred in the past and incident information in which the clinical workflow in which the incident occurred is associated; ,
An association unit that associates the incident information collected by the collection unit with the clinical workflow to be executed;
A display control unit for displaying incident information associated with the clinical workflow to be executed;
A management device comprising:   The management device according to claim 1, wherein the display control unit displays the incident information associated with the clinical workflow to be executed on a display unit of a device that is executing the clinical workflow to be executed. The associating unit associates incident information collected by the collecting unit with a process included in the execution-target clinical workflow, in which an incident has occurred in the past indicated by the incident information,
The management apparatus according to claim 1, wherein the display control unit displays incident information associated with the process on a display unit of the apparatus that is executing the process during the execution of the process. The information related to the incident that occurred in the past includes an influence degree indicating the degree of influence on the execution of the clinical workflow associated with the information when the incident occurs,
The management apparatus according to any one of claims 1 to 3, wherein the display control unit varies a display mode of the incident information according to an included degree of influence.   The display control unit displays, as incident information to be displayed, at least one of the influence on the execution of the clinical workflow in which the incident occurs, the coping method for the influence, and the statistical information on the incident when the incident occurs The management device according to any one of claims 1 to 4, wherein A detection unit that detects the type of incident that occurred during the execution of the clinical workflow to be executed or the type of incident that would occur;
For the same examination purpose, from the second storage device in which a plurality of combinations of incident occurrence patterns and clinical workflows are stored, the purpose of the examination being performed and the type detected by the detection unit A flow control unit that acquires a clinical workflow corresponding to a corresponding incident occurrence pattern, and executes the acquired clinical workflow instead of the clinical workflow to be executed;
The management apparatus of any one of Claims 1-5 provided with these. The second storage device stores a plurality of combinations of the incident occurrence pattern, the clinical workflow, and the user who requests the examination for the same examination purpose,
The flow control unit acquires, from the second storage device, an incident occurrence pattern corresponding to the type detected by the detection unit, and a clinical workflow corresponding to a user who performs the examination, and executes the execution The management apparatus according to claim 6, wherein the acquired clinical workflow is executed instead of the target clinical workflow.

Images