JP6257999B2 - Medical device operation management device - Google Patents

Description

  Embodiments described herein relate generally to a medical device operation management apparatus.

  In the medical device maintenance system operated by the medical device vendor (medical device manufacturer), the operation history and exposure dose log output by the medical device are used, for example, maintenance work such as tube replacement timing and pre-prediction of failure occurrence. Is running.

  In this type of medical device maintenance system, for example, a technology that predicts with high accuracy that there is a high need for maintenance on medical devices and parts is used. This technology requires maintenance by extracting the category of parts that cause defects based on various types of information related to medical devices and parts, and by extracting parts that belong to the same category as the defective parts category. Is expected to be high.

  On the other hand, the International Electrotechnical Commission (IEC) has formulated IEC80001 with some exceptions. IEC 80001-1 is a standard for “Risk management of IT networks connected to medical devices (issued in October 2010)” and defines important characteristics (safety, effectiveness, data system security), and risk of important characteristics Realize management. In addition, IEC 80001-1 is mainly a responsible department (a facility such as a hospital), and realizes risk management in cooperation with a related party (manufacturer) of the subject.

  That is, according to IEC80001-1, the hospital side “assembles and uses a finished product (for example, a medical device system that can be operated via a network)” from “a standpoint of using a finished product (single medical device)”. Change to a position. For this reason, the hospital side needs to be regarded as a manufacturer and perform risk management. With the formulation of such international standards, it is highly likely that the hospital will be responsible for risk management in the future.

  In the current situation, each manager of the clinical department (radiology department if it is assumed to handle medical equipment) performs risk management in consideration of the risk of medical practice. Such current risk management includes, for example, a policy established by a hospital or a periodic risk assessment using an evaluation item defined by a hospital evaluation mechanism. However, it is considered that each manager needs to execute risk management in consideration of the risk in the future when, for example, the operation of the medical device is involved in addition to the risk of medical practice.

JP 2007-316860 A

  However, since the administrator is not familiar with the medical device, it cannot execute risk management when the operation of the medical device is involved, and therefore cannot manage the problem (risk) when the operation of the medical device is involved. .

  The problem to be solved by the present invention is to provide a medical device operation management apparatus that can cope with a problem in the case where an administrator who is not familiar with a medical device is involved in the operation of the medical device.

  The medical device operation management apparatus according to the embodiment includes a recommended operation log acquisition unit, a problem importance level acquisition unit, a problem handling acquisition unit, an operation log acquisition unit, a problem identification unit, an importance level extraction unit, a handling method selection unit, and a process execution unit. I have.

  The recommended operation log acquisition unit acquires a recommended operation log of a medical device.

  The problem importance level acquisition unit acquires importance level information associating a problem related to the operation of the medical device and the importance level of the problem.

  The problem coping acquisition means acquires problem coping information in which the problem, the importance, and a coping method of the problem are associated.

  The operation log acquisition unit acquires an operation log of the medical device.

  The problem specifying means specifies the problem based on a difference between the acquired recommended operation log and the acquired operation log.

  The importance level extraction unit extracts the importance level associated with the identified problem from the importance level information.

  The coping method selection means selects a coping method for the problem from the problem coping information based on the identified problem, the extracted importance, and the acquired problem coping information.

The process execution means executes a process based on the selected countermeasure method.
The recommended operation log includes permitter list information for each operation of the medical device, and the operation log includes operator identification information for identifying an operator of the medical device.

It is a schematic diagram which shows the medical device operation management apparatus which concerns on 1st Embodiment, and its periphery structure. It is a schematic diagram for demonstrating the recommended operation log memory | storage part in the same embodiment. It is a schematic diagram for demonstrating the problem importance storage part in the embodiment. It is a schematic diagram for demonstrating the problem coping memory part in the same embodiment. It is a flowchart for demonstrating the operation | movement in the embodiment. It is a schematic diagram for demonstrating the operation | movement in the embodiment. It is a schematic diagram for demonstrating an example of the operation | movement in the embodiment. It is a schematic diagram for demonstrating an example of the operation | movement in the embodiment. It is a schematic diagram for demonstrating an example of the operation | movement in the embodiment. It is a schematic diagram for demonstrating an example of the operation | movement in the embodiment. It is a schematic diagram for demonstrating an example of the operation | movement in the embodiment. It is a schematic diagram for demonstrating an example of the operation | movement in the embodiment. It is a mimetic diagram for explaining an example of a report in the embodiment. It is a mimetic diagram for explaining an example of a report in the embodiment. It is a schematic diagram which shows the medical device operation management apparatus which concerns on 2nd Embodiment, and its periphery structure. It is a schematic diagram for demonstrating the operator information storage part in the embodiment. It is a flowchart for demonstrating the operation | movement in the embodiment. It is a schematic diagram which shows the medical device operation management apparatus which concerns on 3rd Embodiment, and its periphery structure. It is a schematic diagram for demonstrating the recommended operation log in the same embodiment. It is a flowchart for demonstrating the operation | movement in the embodiment.

  Each embodiment will be described below with reference to the drawings. The following apparatus can be implemented with either a hardware configuration or a combined configuration of hardware resources and software. As the software of the combined configuration, a program installed in advance on a computer from a network or a storage medium, and a program for causing the computer to realize the functions of the apparatus is used.

<First Embodiment>
FIG. 1 is a schematic diagram showing a medical device operation management apparatus and its peripheral configuration according to the first embodiment. This medical device operation management apparatus may be provided as a part of a hospital information system (HIS), for example, or may be incorporated in a medical device.

  The medical device operation management apparatus includes a recommended operation log storage unit 1, a problem importance storage unit 2, a problem handling storage unit 3, and an apparatus body 10. The apparatus main body 10 includes an operation log acquisition unit 11, a recommended operation log acquisition unit 12, a problem importance level acquisition unit 13, a problem analysis unit 14, a problem coping unit 15, and a problem notification unit 16, and includes a medical device ME and an administrator. Communication with the terminal MT is possible.

  Here, the recommended operation log storage unit 1 stores a recommended operation log of the medical device ME as shown in FIG.

  The recommended operation log is information created based on, for example, a policy (for example, inspection work procedure manual, inspection device management procedure manual, etc.) determined on the hospital side. The recommended operation log includes, for example, operation procedure information for each medical device (recommended operation order), an estimated exposure dose for each part to be examined (exposure dose according to the current tube voltage setting), and an authorized person for each operation. Includes list information and recommended time of operation.

  Such a recommended operation log is preferably managed by narrowing down to the minimum necessary information so that information can be exchanged smoothly.

  The recommended operation log storage unit 1 may be managed at the own hospital or may be managed by external storage (for example, cloud or the like). That is, the recommended operation log storage unit 1 may be omitted from the medical device operation management apparatus. Further, the recommended operation log storage unit 1 may manage the recommended operation log with a database, or may manage the recommended operation log with a file. Such recommended operation log storage unit 1 constitutes recommended operation log storage means.

  As illustrated in FIG. 3, the problem importance storage unit 2 stores importance information that associates a problem associated with the operation of the medical device ME and the importance of the problem. The problem may be associated with importance and supplemental information. The supplemental information may be, for example, the number of problems (risks) that have occurred in the past on the hospital side (for each disease, for each patient, for each department). The problem may be associated with a plurality of importance levels for each important characteristic (safety, efficiency, data security) of IEC80001.

  Here, the problem (risk) represents a situation where the actual operation log is different from the predetermined recommended operation log.

  The importance indicates the degree of influence (patient condition, frequency of occurrence, cost) of the problem (risk) ranked according to a certain standard. The importance may be a fixed value or a fluctuation value (such as a monthly rate). The individual importance is represented by a value within a range of 0 or more and 1 or less, for example. However, when the importance for each important characteristic is added, the importance of the addition result may exceed 1.

  Such a problem importance storage unit 2 can be prepared, for example, by assigning importance to a policy (recommended operation log) determined on the hospital side in advance.

  When assigning importance, for example, the number of problems (risks) that occurred in the past on the hospital side, or the importance and number of problems that have been publicly disclosed (risks) (for example, near-miss cases, hospitals, etc.) Evaluation mechanism items, etc.) may be used. Also, the importance may be given as a default value by the vendor.

  The problem importance degree storage unit 2 may be managed at its own hospital or may be managed by external storage (for example, cloud). That is, the problem importance degree storage unit 2 may be omitted from the medical device operation management apparatus. The problem importance level storage unit 2 may manage the importance level information as a database, or may manage the importance level information as a file. Such a problem importance storage unit 2 constitutes a problem importance storage unit.

  As shown in FIG. 4, the problem coping storage unit 3 stores problem coping information in which a problem, importance, and a coping method (specific coping in the figure) of the problem are associated. The problem may be further associated with a coping person.

  The coping person is information indicating the coping person, and may be any combination of, for example, an administrator, an operator, a vendor service person, and the like.

  The specific countermeasure is information indicating what kind of countermeasure is to be taken, and basically indicates a process that can be executed immediately. Processes that can be executed immediately include, for example, command transmission to the medical device ME, setting change of the medical device ME, notification or operation request to the administrator, advice (Tips) display to the operator, vendor (serviceman) It is processing such as contact. The processing that cannot be executed immediately is, for example, actual processing by the vendor (eg, processing for exchanging parts such as a tube) after contacting the vendor. For example, the problem coping section 15 uses event processing to notify the medical device ME of a setting change command, and the medical device ME side changes the setting based on the setting change command. It may be executed by the process of executing. Further, the problem coping section 15 may change the setting of the medical device ME.

  When the importance level is higher than a predetermined value (for example, when importance level = 1), immediate action is required, and therefore, it may be expressed as “immediate”. In the case of low importance, no (urgent) action is required.

  The problem-handling storage unit 3 may be managed at its own hospital, or may be managed by external storage (for example, cloud or the like). That is, the problem handling storage unit 3 may be omitted from the medical device operation management apparatus. Further, the problem handling storage unit 3 may manage the problem handling information in a database, or may manage the problem handling information in a file. Such a problem handling storage unit 3 constitutes a problem handling storage means.

  The operation log acquisition unit (operation log acquisition means) 11 acquires an operation log of the medical device ME.

  A recommended operation log acquisition unit (recommended operation log acquisition means) 12 acquires a recommended operation log in the recommended operation log storage unit 1.

  The problem importance level acquisition unit (problem importance level acquisition means) 13 acquires the importance level information in the problem importance level storage unit 2.

  The problem analysis unit 14 has the following functions (f14-1) to (f14-2).

  (f14-1) A problem identification function that identifies a problem based on the difference between the recommended operation log acquired by the recommended operation log acquisition unit 12 and the operation log acquired by the operation log acquisition unit 11. Note that the term “problem analysis unit” may be read as “problem identification unit”.

  (f14-2) An importance extraction function for extracting the importance associated with the identified problem from the importance information acquired by the problem importance acquisition unit 13.

  The problem analysis unit 14 as described above constitutes a problem specifying unit and an importance level extracting unit.

  The problem coping section 15 has the following functions (f15-1) to (f15-2).

  (f15-1) Based on the problem identified by the problem analysis unit 14 and the importance extracted by the problem analysis unit 14, a method for dealing with the problem is selected from the problem handling information in the problem handling storage unit 3. Coping method selection function.

  (f15-2) A process execution function for executing a process based on the selected countermeasure.

  The problem coping section 15 as described above constitutes coping method selection means and processing execution means.

  The problem notifying unit 16 totals the problems identified by the problem analyzing unit 14 and transmits a report including a graph representing the totaled result to the administrator terminal MT.

  Supplementally, the problem notifying unit 16 summarizes operation logs determined to be problems (for a certain period of time) by the problem analyzing unit 14 in a report format and notifies the administrator terminal MT.

  This type of report includes information that is easy to understand visually for the administrator, for example, including a graph. Here, the administrator can set what information is included in the report. The information included in the report includes, for example, comparison / transition of the number of problem occurrences, operators with many problems, correlations between examinations and problems (what kind of problems are likely to occur at what kind of examinations) ), Etc. can be set as appropriate.

  In addition, the problem notification unit 16 can set the frequency (report period) of reporting a report, for example, once every two hours every month or every week.

Moreover, the means for the problem notification part 16 to notify a report is arbitrary, For example, the following (a)-(c) etc. can be used suitably.
(A) The problem notifying unit 16 transmits an instruction for displaying advice (Tips) including link information to a Web page for publishing a report to the administrator terminal TM.
(B) The problem notification unit 16 transmits an email including a report to the administrator terminal TM.
(C) The problem notification unit 16 transmits an instruction to start application software for displaying a report to the administrator terminal TM.

  Further, the notification destination such as a report by the problem notification unit 16 is not limited to the administrator terminal TM, but may include the medical device ME (or an operation terminal / console immediately before the target operation). For example, a part of the information totaled by the problem notification unit 16 (for example, attention is necessary because there are many XX problems this month) is transmitted not only to the administrator terminal TM but also to the medical device ME. You may directly present (for example, tips display) on the top (or the operation terminal / console immediately before the target operation).

  Next, the operation of the medical device operation management apparatus configured as described above will be described with reference to the flowchart of FIG. 5 and the schematic diagrams of FIGS.

  In the medical device operation management apparatus, the recommended operation log acquisition unit 12 acquires the recommended operation log in the recommended operation log storage unit 1 (ST1).

  The problem importance level acquisition unit 13 acquires the importance level information in the problem importance level storage unit 2 (ST2).

  The operation log acquisition unit 11 determines whether or not an operation log of the medical device ME has been generated (ST3). If not, the determination in step ST3 is continued.

  When an operation log is generated as a result of the determination in step ST3, the operation log acquisition unit 11 acquires an operation log of the medical device ME.

  The problem analysis unit 14 compares the recommended operation log acquired by the recommended operation log acquisition unit 12 with the operation log acquired by the operation log acquisition unit 11 (ST4), and determines whether there is any separation (difference) between the two. A determination is made (ST5), and if no, the process returns to step ST3.

  If there is separation (difference) as a result of the determination in step ST5, the problem analysis unit 14 identifies the problem based on the difference (ST6).

  In step ST6, for example, (1) operation procedure omission, (2) execution of unauthorized operation, (3) operation time abnormality, (4) unexpected grasp in advance, (5) throughput decrease, ( 6) The problem can be identified for various situations such as the importance of the problem.

(1) Missing Operation Procedure The problem analysis unit 14 compares the recommended operation log 1a and the operation log L as shown in FIG. 6, and identifies the problem of missing the operation procedure based on the difference between the two.

  In the example shown in FIG. 6, a problem that “confirmation of time sequence (TimeSequence)” defined in the recommended operation log 1 a is missing from the actual operation log L is specified. The time sequence is an operation for confirming in advance the transition of the actual time at the time of shooting.

(2) Execution of unauthorized operation As shown in FIG. 7, the problem analysis unit 14 compares the recommended operation log 1a with the operation log L, and executes an unauthorized operation based on the difference between the two. Is identified.

  In the example illustrated in FIG. 7, the problem that the authorized person defined in the recommended operation log 1 a is different from the setting change operator recorded in the operation log L is specified.

(3) Abnormal operation time The problem analysis unit 14 compares the recommended operation log 1a and the operation log L, and identifies a problem indicating an abnormal operation time based on the difference between the two.

  In the example illustrated in FIG. 8, an abnormality is specified such that the difference between the operation time set in the recommended operation log 1 a and the operation time recorded in the operation log L is too short or too long. If the operation time is too short, the setting screen may not be confirmed sufficiently. If the operation time is too long, the patient may be left unattended.

(4) Grasping Unexpected Problem As shown in FIG. 9, the problem analysis unit 14 compares the recommended operation log 1a with the operation log L, and grasps (identifies) an unexpected problem based on the difference between the two. To do.

  In the example shown in FIG. 9, a problem that cannot normally occur is identified, such as a large difference between the estimated exposure amount set in the recommended operation log 1a and the actual exposure amount recorded in the operation log L. To do.

(5) Decrease Throughput As shown in FIG. 10, the problem analysis unit 14 compares the recommended operation log 1a with the operation log L, and identifies a problem that the throughput has decreased based on the difference between the two.

  In the example illustrated in FIG. 10, when the maximum performance (or recommended performance) determined in the recommended operation log 1a does not satisfy the data communication speed recorded in the operation log L, a problem in which the throughput is reduced is identified. In this case, for example, the problem coping part 15 prohibits connection of a low-priority medical device based on the priority of the device in the recommended operation log 1a to deal with the problem. In this example, the low-priority medical devices are a medical information printing printer and an ultrasonic diagnostic apparatus UL-1.

(6) Problem importance level Since the problem analysis unit 14 is substantially difficult to deal with all genre problems in parallel, the priority genre input from an input unit (not shown) and the result obtained in step ST2 Based on the importance level information, a priority problem is identified with priority among the priority genre importance levels.

  For example, as shown in FIG. 11, when a patient with a high degree of urgency is examined, a problem with a high degree of importance is identified among the importance levels of genres (important characteristics) of “efficiency” and “safety”.

  Further, for example, when a new medical device is introduced, a problem of high importance is identified from the importance of the “efficiency” genre.

  When there are many system problems due to viruses or the like, a problem with a high importance is identified from the importance of the genre of “data security”.

  By any one of the above processes (1) to (6), the problem is identified in step ST6.

  After step ST6, the problem analysis unit 14 extracts (specifies) the importance associated with the identified problem from the importance information acquired by the problem importance acquisition unit 13 (ST7).

  The problem coping section 15 selects a problem coping method from the problem coping information in the problem coping storage section 3 based on the problem identified in step ST6 and the importance identified in step ST7 (ST8). .

  For example, as shown in FIG. 12, based on the problem “time sequence unconfirmed” identified in step ST6 and the importance “0.7” of “safety”, the problem handling information in the problem handling storage unit 3 Select “Troubleshooting (Forced update of configuration file)” to solve the problem.

  Next, the problem coping section 15 executes processing based on the selected coping method (ST9).

  As shown in FIG. 13 or FIG. 14, the problem notification unit 16 aggregates the problems identified by the problem analysis unit 14, and creates a report 16r including a graph representing the aggregation result (ST10).

  After that, the problem notification unit 16 transmits the report 16r to the administrator terminal MT (ST11).

  As described above, according to the present embodiment, the problem is identified based on the difference between the acquired recommended operation log and the acquired operation log, the importance associated with the identified problem is extracted, and the identified problem The management method is selected from the problem response information based on the extracted importance and the processing based on the selected response method, so that even an administrator who is not familiar with the medical device can operate the medical device. Can deal with the problem of entanglement.

  In addition, in general, a medical device provided by a medical device vendor does not consider a hospital policy. Also, managers tend not to be familiar with medical devices. For this reason, the conventional administrator is forced to rely on the vendor even if a problem involving the operation of the medical device occurs. On the other hand, in this embodiment, the problem is identified based on the difference between the acquired recommended operation log and the acquired operation log, and the processing based on the coping method selected based on the problem and the importance is executed. Even an administrator who is not familiar with medical devices can deal with problems associated with operations of medical devices.

<Second Embodiment>
FIG. 15 is a schematic diagram showing a medical device operation management apparatus and its peripheral configuration according to the second embodiment. The same reference numerals are assigned to the same parts as those in FIG. The part is mainly described. In the following embodiments, the same description is omitted.

  The second embodiment is a modification of the first embodiment, and has a configuration in which a countermeasure is selected based on the correlation between the operator and the problem (problem that tends to occur for each operator). ing.

  Specifically, the medical device operation management apparatus includes an operator information storage unit 4 as compared with the configuration shown in FIG.

  As shown in FIG. 16, the operator information storage unit 4 is operator identification information for identifying the operator of the medical device ME (“operator A”, “operator B”, “operator C” in the figure). And the operator information in which the problem related to the operation of the medical device ME and the statistical value of the occurrence of the problem are associated with each other.

  Here, as the statistical value of the occurrence of a problem, the total cumulative number, the cumulative number for each important characteristic, the cumulative number in a specific period, the frequency of occurrence, the number of occurrences in a specific condition, and the like can be used as appropriate. The total cumulative number is the number of all problems generated by the operator. The cumulative number by important characteristic is the number of problems that have occurred in an important characteristic of the operator. The cumulative number of cases in a specific period is the number of problems that the operator has caused during a specific period such as last month. The occurrence frequency is a value indicating how often the problem has occurred. The number of occurrences under a specific condition is a value indicating how many problems have occurred under a certain work condition.

  In addition, as a statistical value, any type of value can be used as long as it is a statistical value (feature value) representing a feature for each operator, regardless of the format of numerical values, ratios, and the like.

  The operator information storage unit 4 may be managed at the own hospital or may be managed by external storage (for example, cloud or the like). That is, the operator information storage unit 4 may be omitted from the medical device operation management device. Further, the operator information storage unit 4 may manage the operator information with a database, or may manage the operator information with a file. Such an operator information storage unit 4 constitutes an operator information storage means.

  In the example of the operator information shown in FIG. 16, the operator B has a large total cumulative number of problems “time sequence unconfirmed”. For this reason, it is desirable for the operator B to raise the importance of the problem based on the total cumulative number of cases and to deal with it strictly.

  Accordingly, the coping method selection function (f15-1) of the problem coping section 15 includes the following functions (f15-1-1) to (f15-1-5).

  (f15-1-1) Operator information in which operator identification information for identifying an operator of the medical device ME, a problem associated with the operation of the medical device, and a statistical value of the occurrence of the problem is associated with the operator An operator information acquisition function acquired from the information storage unit 4.

  (f15-1-2) A function that extracts operator identification information from the acquired operation log.

  (f15-1-3) A function of extracting statistical values from the operator information based on the problem identified in step ST6 and the extracted operator identification information.

  (f15-1-4) A function of weighting the importance extracted (specified) in step ST7 by the extracted statistical value.

  (f15-1-5) A function for selecting a problem coping method from the problem coping information in the problem coping storage unit 3 based on the problem identified in step ST6 and the weighted importance.

  Next, the operation of the medical device operation management apparatus configured as described above will be described with reference to the flowchart of FIG.

  Now, in the medical device operation management apparatus, it is assumed that steps ST1 to ST7 are executed in the same manner as in the first embodiment, and the problem and the importance are identified.

  The problem coping section 15 selects a problem coping method from the problem coping information in the problem coping storage section 3 based on the problem identified in step ST6 and the importance identified in step ST7 (ST8). .

  At this time, the problem handling unit 15 obtains operator information that associates the operator identification information for identifying the operator of the medical device ME, the problem related to the operation of the medical device, and the statistical value of the occurrence of the problem. Obtained from the operator information storage unit 4.

  The problem coping section 15 extracts operator identification information from the operation log acquired in step ST3.

  The problem coping section 15 extracts a statistical value from the operator information based on the problem identified in step ST6 and the extracted operator identification information.

  The problem coping section 15 weights (recalculates) the importance extracted (specified) in step ST7 based on the extracted statistical value (ST8-1).

  The problem coping section 15 selects a problem coping method from the problem coping information in the problem coping storage section 3 based on the problem identified in step ST6 and the weighted importance (ST8-2). .

  Thereafter, steps ST9 to ST11 are executed in the same manner as described above.

  That is, the problem coping section 15 executes processing based on the selected coping method (ST9).

  The problem notification unit 16 aggregates the problems identified by the problem analysis unit 14, and transmits a report including a graph representing the aggregation result to the administrator terminal MT (ST10 to ST11).

  As described above, according to the present embodiment, in step ST8, the operator identification information is extracted from the operation log, the statistical value is extracted from the operator information based on the problem and the operator identification information, and the statistical value is more important. In addition to the effects of the first embodiment, an operation is performed by weighting the degree and selecting a problem coping method from the problem coping information in the problem coping storage unit 3 based on the problem and the weighted importance. The problem coping method can be selected according to the statistical value for each person.

<Third Embodiment>
FIG. 18 is a schematic diagram showing a medical device operation management apparatus and its peripheral configuration according to the third embodiment, and FIG. 19 is a schematic diagram for explaining a recommended operation log in the same embodiment.

  The third embodiment is a modification of the second embodiment, but may be a modification of the first embodiment. In the third embodiment, the recommended operation log in the recommended operation log storage unit 1 is recommended by the operation log recommended by the hospital in which the medical device EM is installed (for example, examination work procedure) and the vendor of the medical device EM. An operation log (eg, an operation manual) is included.

  Here, the recommended operation log in the recommended operation log storage unit 1 is a procedure or operation that differs between the hospital side and the vendor side (especially for medical devices that are recommended by the vendor side but not recommended by the hospital side). (Operation) has all added information.

  In the example shown in FIG. 19, the recommended operation log 1a in the recommended operation log storage unit 1 includes a difference d3 between the hospital-side work procedure manual d1 and the vendor-side operation manual d2.

  In addition, the recommended operation log 1a in the recommended operation log storage unit 1 is stored in the recommended operation log 1a so that the operation log after being processed by the problem coping unit 15 is not further separated from the recommended operation log 1a. Is updated by adding a difference d3 (also referred to as a countermeasure log).

  Accordingly, the medical device operation management apparatus includes a recommended operation log creation unit 5 as compared with FIG.

  The recommended operation log creation unit 5 creates or updates a recommended operation log using, for example, a hospital policy, information provided from a vendor, and a problem list.

Here, as the hospital policy, for example, an inspection work procedure manual, an inspection equipment management procedure manual, and the like can be used as appropriate. )
As provided information from the vendor, for example, medical device operation manuals, answer information from help desks, and the like can be used as appropriate.

  As the problem list, for example, a list of problems with high importance among the problems executed by the problem coping section 15 can be used as appropriate. The problem list represents, for example, a list of problems such as an operation log being output when advice (Tips) is displayed.

  Further, the recommended operation log creation unit 5 updates the recommended operation log 1a stored in the recommended operation log storage unit 1 to a recommended operation log determined based on an operation determined to be appropriate in the processing based on the coping method. Thus, the recommended operation log 1a in the recommended operation log storage unit 1 is always maintained in the latest state. In this case, the recommended operation log creation unit 5 constitutes a recommended operation log update unit. Here, “Recommended operation log determined based on operation determined to be appropriate by processing based on coping method” is replaced with “Recommended operation log determined based on operation determined to be appropriate for problem handling” Alternatively, it may be read as “recommended operation log determined in processing based on coping method” or the like. Further, for example, such a recommended operation log creation unit 5 can execute creation or update of the recommended operation log 1a according to the operation of the administrator terminal TM or the medical device ME (or the operation terminal / console) by the operator. It has become. The operator may be, for example, a person who determines that a certain operation is appropriate by coping with a problem and determines a recommended operation log based on the operation determined to be appropriate. Alternatively, this operator may be an operator who performs an operation of updating the recommended operation log 1a in the recommended operation log storage unit 1 to the recommended operation log determined by an administrator or the like.

  Next, the operation of the medical device operation management apparatus configured as described above will be described with reference to the flowchart of FIG.

  First, in the medical device operation management apparatus, the recommended operation log creation unit 5 creates a recommended operation log using, for example, a hospital policy, information provided by the vendor, and a problem list, and recommends this recommended operation log. Writing to the operation log storage unit 1 (ST0). Alternatively, the recommended operation log creation unit 5 updates the recommended operation log storage unit 1 with the created recommended operation log.

  Subsequently, in the medical device operation management apparatus, steps ST1 to ST8 are executed in the same manner as in the first or second embodiment, and a problem coping method is selected.

  The problem coping section 15 executes processing based on the selected coping method (ST9).

  Further, the recommended operation log creation unit 5 updates the recommended operation log storage unit 1 so as to add an operation log (processing log) indicating the process of step ST9 to the recommended operation log (ST9a).

  Hereinafter, as described above, the problem notification unit 16 aggregates the problems identified by the problem analysis unit 14, and transmits a report including a graph representing the aggregation result to the administrator terminal MT (ST10 to ST11).

  As described above, according to this embodiment, the recommended operation log in the recommended operation log storage unit 1 is converted into an operation log recommended by the hospital in which the medical device EM is installed, Since it is configured to include the operation log recommended by the vendor of the device EM, in addition to the effects of the first or second embodiment, the difference between the recommended operation on the hospital side and the recommended operation on the vendor side is eliminated. Can do.

  According to at least one embodiment described above, the problem is identified based on the difference between the acquired recommended operation log and the acquired operation log, and the importance associated with the identified problem is extracted and specified. Based on the problem and the extracted importance, a configuration that selects the coping method of the problem from the problem coping information, and executes processing based on the selected coping method, so that even an administrator who is not familiar with the medical device can It is possible to deal with problems when operations are involved.

  Note that the methods described in the above embodiments are, as programs that can be executed by a computer, magnetic disks (floppy (registered trademark) disks, hard disks, etc.), optical disks (CD-ROMs, DVDs, etc.), magneto-optical disks. (MO), stored in a storage medium such as a semiconductor memory, and distributed.

  In addition, as long as the storage medium can store a program and can be read by a computer, the storage format may be any form.

  In addition, an OS (operating system) running on a computer based on an instruction of a program installed in the computer from a storage medium, MW (middleware) such as database management software, network software, and the like realize the above-described embodiment. A part of each process may be executed.

  Furthermore, the storage medium in each embodiment is not limited to a medium independent of a computer, but also includes a storage medium in which a program transmitted via a LAN, the Internet, or the like is downloaded and stored or temporarily stored.

  Further, the number of storage media is not limited to one, and the case where the processing in each of the above embodiments is executed from a plurality of media is also included in the storage media in the present invention, and the media configuration may be any configuration.

  The computer in each embodiment executes each process in each of the above embodiments based on a program stored in a storage medium, and a single device such as a personal computer or a plurality of devices are connected to a network. Any configuration of the system or the like may be used.

  In addition, the computer in each embodiment is not limited to a personal computer, and includes an arithmetic processing device, a microcomputer, and the like included in an information processing device, and is a generic term for devices and devices that can realize the functions of the present invention by a program. Yes.

  In addition, although some embodiment of this invention was described, these embodiment is shown as an example and is not intending limiting the range of invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

  DESCRIPTION OF SYMBOLS 1 ... Recommended operation log memory | storage part, 2 ... Problem importance degree memory | storage part, 3 ... Problem handling memory | storage part, 4 ... Operator information storage part, 5 ... Recommended operation log creation part, 10 ... Apparatus main body, 11 ... Operation log acquisition part , 12 ... Recommended operation log acquisition unit, 13 ... Problem importance level acquisition unit, 14 ... Problem analysis unit, 15 ... Problem coping unit, 16 ... Problem notification unit, ME ... Medical device, MT ... Administrator terminal.

Claims (6)

Recommended operation log acquisition means for acquiring recommended operation logs for medical devices,
Problem importance acquisition means for acquiring importance information that associates the problem associated with the operation of the medical device and the importance of the problem;
Problem coping acquisition means for acquiring problem coping information that associates the problem, the degree of importance, and a coping method of the problem;
Operation log acquisition means for acquiring an operation log of the medical device;
A problem identifying means for identifying the problem based on the difference between the acquired recommended operation log and the acquired operation log;
Importance extracting means for extracting the importance associated with the identified problem from the importance information;
A coping method selecting means for selecting a coping method for the problem from the coping information, based on the identified problem, the extracted importance, and the acquired problem coping information;
Processing execution means for executing processing based on the selected coping method;
Equipped with a,
The recommended operation log includes permitter list information for each operation of the medical device, and the operation log includes operator identification information for identifying an operator of the medical device.
Medical device operation management device characterized by the above. In the medical device operation management apparatus according to claim 1,
Recommended operation log storage means for storing the recommended operation log;
Problem importance storage means for storing the importance information;
Problem-handling storage means for storing the problem-handling information;
With
The recommended operation log acquisition unit acquires the recommended operation log from the recommended operation log storage unit,
The problem importance level acquisition means acquires the importance level information from the problem importance level storage means,
The medical device operation management apparatus, wherein the problem handling acquisition unit acquires the problem handling information from the problem handling storage unit. In the medical device operation management apparatus according to claim 2 ,
The recommended operation log storage unit is configured to update the recommended operation log stored in the recommended operation log storage unit to a recommended operation log determined based on an operation determined to be appropriate in the processing based on the coping method. recommended operation log update means for maintaining the recommended operation log of the inner always up-to-date state,
With
The recommended operation log stored in the recommended operation log storage unit includes an operation log recommended by a hospital where the medical device is installed and an operation log recommended by a vendor of the medical device. Medical device operation management device. The medical device operation management apparatus according to any one of claims 1 to 3,
The coping method selecting means is
Operator information acquisition means for acquiring operator information that associates operator identification information for identifying an operator of the medical device, a problem related to operation of the medical device, and a statistical value of occurrence of the problem;
Means for extracting operator identification information from the acquired operation log;
Means for extracting a statistical value from the operator information based on the identified problem and the extracted operator identification information;
Means for weighting the extracted importance by the extracted statistical value;
Means for selecting a problem handling method from the problem handling information based on the identified problem and the weighted importance;
A medical device operation management apparatus comprising: In the medical device operation management apparatus according to claim 4,
Operator information storage means for storing the operator information;
With
The medical device operation management apparatus, wherein the operator information acquisition unit acquires the operator information from the operator information storage unit.   Recommended operation log acquisition means for acquiring recommended operation logs for medical devices,
  Problem importance acquisition means for acquiring importance information that associates the problem associated with the operation of the medical device and the importance of the problem;
  Problem coping acquisition means for acquiring problem coping information that associates the problem, the degree of importance, and a coping method of the problem;
  Operation log acquisition means for acquiring an operation log of the medical device;
  A problem identifying means for identifying the problem based on the difference between the acquired recommended operation log and the acquired operation log;
  Importance extracting means for extracting the importance associated with the identified problem from the importance information;
  A coping method selecting means for selecting a coping method for the problem from the coping information, based on the identified problem, the extracted importance, and the acquired problem coping information;
  Processing execution means for executing processing based on the selected coping method;
  With
  The coping method selecting means is
  Operator information acquisition means for acquiring operator information that associates operator identification information for identifying an operator of the medical device, a problem related to operation of the medical device, and a statistical value of occurrence of the problem;
  Means for extracting operator identification information from the acquired operation log;
  Means for extracting a statistical value from the operator information based on the identified problem and the extracted operator identification information;
  Means for weighting the extracted importance by the extracted statistical value;
  Means for selecting a problem handling method from the problem handling information based on the identified problem and the weighted importance;
  A medical device operation management apparatus comprising: