JP2006099479A - Hospital audit log management support system and hospital audit log server - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a hospital audit log management support system capable of easily setting a hospital audit log and performing maintenance and management of the audit log for reduction in a work load of a manager. <P>SOLUTION: A hospital audit log policy is generated on a hospital audit log server 20 side collectively managing a system to be sent to a hospital audit log client device 30 arranged in each medical information appliance to be audited. The hospital audit log client device 30 generates an audit log according to the audit log policy generated in the hospital audit log server. The generated audit log is automatically collected to the hospital audit log server 20 side to be joined for each medial information appliance for management. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  It relates to security maintenance management of hospital information systems. In particular, setting, recording, and management of hospital audit logs that are legally effective and required to be collected and managed in hospitals that are recorded by medical information devices that handle patient information. It relates to what is used to assist.

  A medical information device has a recording function of a log (operation log) related to all events that occur in itself, such as an operation log, an operation trace, an apparatus component status log, and an alert. These can be used for notifying the user of information, or for maintenance of equipment or analysis of malfunctions and failures.

  The primary use / administrator of various data related to the recorded operation log is each medical information device manufacturer. Therefore, the log recorded by the medical information device is sufficient if the items required by the medical information device manufacturer are satisfied, and the specific trigger (trigger) to be logged is determined by the medical information device manufacturer. Logged data is held by each medical information device itself. As a means for transmitting the logged data, a service engineer visits a medical information device installed in a hospital and acquires it, or a remote maintenance service is transmitted to a maintenance management center through a network. The log function is set by a service engineer or controlled by the maintenance management center through a network.

  Apart from such an operation log, there is a so-called “hospital audit log” in which information related to an event dealing with patient information is recorded in the 5W1H system for the purpose of security maintenance management. The usage is recorded and used for security maintenance management, unlike a conventional log such as an operation log.

  By the way, the maintenance and management of the recorded hospital audit log is performed at the responsibility of the hospital where the log is generated. Therefore, the hospital has the right to make decisions regarding log settings such as items to be described in the hospital audit log and specific triggers to be logged. Also, log policies (generation triggers, items to be logged, log storage forms / methods, etc.) related to maintenance / management of hospital audit logs are entrusted to hospital policies. For example, in IHE Technical Framework (Rev5.5), the hospital audit log is collected by each medical information device installed in the hospital and accumulated in the hospital audit log server through a network using a communication protocol such as Syslog. It is written that the log is recorded in. In addition, the description is devoted to medical information equipment in the radiation department, but specific triggers for collecting hospital audit logs, hospital audit log generation actors, and schemas (Schema) of hospital audit logs are defined.

  However, in the maintenance / management of the hospital audit log by the conventional system, for example, the following problems exist.

  That is, in accordance with an audit log policy that differs for each hospital, a number of items such as a trigger for log generation on the medical information device side that handles patient information, items included in the generated log, and management of logs to be stored must be set. In addition, it is necessary to set items in accordance with audit log policies for various devices existing in hospitals. Furthermore, the audit log generated for each apparatus is fragmented, and in order to collect a consistent audit log in a hospital, it is necessary to collect and combine information separately. It is a heavy burden for the hospital administrator to perform these operations individually, and as a result, hospital audit log setting and audit log maintenance are difficult.

In addition, as a well-known document relevant to this application, there exist the following, for example.
JP-A-6-62130

  The present invention has been made in view of the above circumstances, a hospital audit log management support system and a hospital that can easily perform hospital audit log setting and audit log maintenance management, and can reduce the workload of the administrator The purpose is to provide an audit log server.

  In order to achieve the above object, the present invention takes the following measures.

  A first aspect of the present invention is a plurality of audit log client devices, each of which is provided corresponding to a medical information device to be audited, and generates an audit log that is a log of information related to an event dealing with patient information; A system comprising a hospital audit log server connected to each of the audit log client devices via a network, wherein the hospital audit log server stores log items and logs related to the medical information device to be audited A determination means for determining an audit log policy for determining at least one of a form, a log transmission method, and a log generation trigger; and the audit log policy is transmitted to each of the audit log client devices via a network. Each of the audit log client devices via a network, Receiving means for receiving the audit log policy and generating an audit log for the medical information device to be audited based on the audit log policy and an event occurring in the medical information device to be audited A hospital audit log management support system comprising: means; and storage means for storing the generated audit log.

  A second aspect of the present invention provides a plurality of audit logs that are provided corresponding to medical information devices to be audited via a network and generate an audit log that is a log of information related to an event that handles patient information. A system comprising a client device and a hospital audit log server connected to each of the audit log client devices, wherein the hospital audit log server stores log items relating to the medical information device to be audited and logs A determination means for determining an audit log policy for determining at least one of a form, a log transmission method, and a log generation trigger; and a transmission means for transmitting the audit log policy to each of the audit log client devices. Each of the audit log client devices includes a receiving means for receiving the audit log policy, Based on an audit log policy and an event that occurs in the medical information device to be audited, an audit log generation unit that generates an audit log related to the medical information device to be audited, and stores the generated audit log And a hospital audit log management support system.

  A third aspect of the present invention is a plurality of audit log client devices provided corresponding to medical information devices to be audited, and a hospital audit log server connected via a network, A determination means for determining an audit log policy for determining at least one of a log item relating to the medical information device, a log storage form, a log transmission method, and a log generation trigger; and the audit via a network Transmission means for transmitting a log policy to each of the audit log client devices, and generation in at least one of the plurality of audit log client devices based on the audit log policy and an event occurring in the medical information device to be audited The audit log related to the medical information device to be audited is Receiving means for receiving via a hospital audit log server, characterized by comprising storage means for storing the audit log received, the.

  A fourth aspect of the present invention is a hospital audit log server connected via a network to a medical information device to be audited, log items relating to the medical information device to be audited, a log storage mode, A determination means for determining an audit log policy for determining at least one of a log transmission method and a log generation trigger, and information related to an event occurring in the medical information device to be audited is received via a network. A receiving unit; an audit log generating unit configured to generate an audit log relating to the medical information device to be audited based on the audit log policy and information relating to the event to be audited; and storing the generated audit log A hospital audit log server.

  As described above, according to the present invention, a hospital audit log management support system and a hospital audit log server that can easily execute hospital audit log setting and audit log maintenance and reduce the workload of the administrator are realized. Can do.

  Hereinafter, first and second embodiments of the present invention will be described with reference to the drawings. In the following description, components having substantially the same function and configuration are denoted by the same reference numerals, and redundant description will be given only when necessary.

(First embodiment)
FIG. 1 is a diagram showing a configuration of a hospital audit log management support system 10 according to the present embodiment. As shown in the figure, the hospital audit log management support system 10 includes a plurality of medical information devices and a hospital audit log server 20 connected to each medical information device via a network N. In this embodiment, for the sake of specific explanation, the network N is a hospital LAN, and a hospital audit log management support system 10 comprising a plurality of medical information devices and a hospital audit log server 20 installed in the hospital. Will be described as an example. However, the present invention is not limited to this mode. For example, the hospital audit log server 20 is arranged outside the hospital, for example, in an information management provider, and the network N is an Internet network (or a complex composed of an in-hospital LAN and an Internet network). Network) Other telecommunication lines may be used.

  First, the configuration of the hospital audit log server 20 will be described. The hospital audit log server 20 centrally manages the audit log policy for each hospital or each device by exchanging with the audit log client device 30 via the network. In the present embodiment, a single device provided on the network is assumed. For example, other servers such as a hospital information system (HIS) and a radiology information system (RIS) are used. You may install according to the information equipment which has a function.

  FIG. 2 is a block diagram showing the configuration of the hospital audit log server 20. As shown in the figure, the hospital audit log server 20 includes a control unit 201, a log policy generation unit 202, a check unit 203, a storage unit 204, a transmission / reception unit 205, a display unit 206, and an input unit 207.

  The control unit 201 performs overall control of the operation of the hospital audit log server 20 statically or dynamically.

  The log policy generation unit 202 generates an audit log policy based on an input from the operator. Here, the “hospital audit log policy” is for determining at least one of a trigger for generating a (hospital) audit log, an item to be logged, a log storage form / storage method, a transmission form, device recognition information, and the like. This is the policy.

  FIG. 4 is a diagram illustrating an example of the data structure of the audit log policy. The example of the audit log policy shown in the figure is composed of three major items: “Machine Info” indicating device recognition information, “Send Configuration” indicating transmission mode, and “Log Configuration” indicating information for generating an audit log. Has been. The audit log policy generation process and the like will be described in detail later.

  The check unit 203 refers to the correspondence table stored in the storage unit 204 and the identification information attached to the audit log received from the audit log client device 30 to confirm the correspondence between the audit log and the medical information device.

  The storage unit 204 stores specification information and audit log information transmitted / received via the transmission / reception unit 205, information on the audit log policy generated by the log policy generation unit 202, and the like for each medical information device (or corresponding audit log client device). (Every 30) is combined and stored. The storage unit 204 also stores a correspondence table in which each audit log client device 30 is associated with a medical information device to be audited.

  The transmission / reception unit 205 transmits an audit log policy to the audit log client device 30 via the network, and receives specification information and audit log information from the audit log client device 30.

  The display unit 206 has a display and presents various information to the operator in a predetermined form.

  The input unit 207 has an input device (mouse, trackball, mode switch, keyboard, etc.) for capturing various instructions, commands, and information from an observer (operator).

  Next, a medical information device and a monitoring log client device provided corresponding to each medical information device will be described.

  Medical information devices include X-ray computed tomography devices, ultrasonic diagnostic devices, medical imaging devices represented by magnetic resonance imaging devices, medical image observation devices (viewers), surgical devices, various ecological information measuring devices, doctors and engineers, etc. Terminals, medical expense accounting terminals, electronic medical record hospital audit log servers, hospital audit log servers for information processing systems such as HIS and RIS, and other devices that can present patient information to medical workers. Hereinafter, in this embodiment, each operation (including not only an external operation that can be confirmed by the operator but also an internal operation) in the medical information device is referred to as an “event”.

  The medical information device has an audit log client device 30 for generating a hospital audit log related to the medical information device. FIG. 3 is a block diagram showing the configuration of the audit log client device 30. As shown in the figure, the audit log client device 30 includes a control unit 301, a specification information generation unit 303, an audit log generation unit 305, a storage unit 307, and a transmission / reception unit 309.

  The control unit 301 comprehensively controls the operation of the audit log client device 30 statically or dynamically.

  The specification information generation unit 303 generates audit log support specification information regarding the corresponding audit log client device 30. Here, the audit log support spec information is the event name that can be generated to the maximum by the corresponding (information subject to audit) medical information device, the maximum item that can be recorded in each event, the audit log transmission method, the medical information device Information including at least one of the identification information.

  The audit log generation unit 305 generates an audit log related to the medical information device to be monitored according to a predetermined method. The generation of the audit log by the audit log generation unit 305 will be described in detail later.

  The storage unit 307 stores the generated audit log support specification information, audit log, and audit log policy received from the hospital audit log server 20.

  The transmission / reception unit 309 transmits the audit log support specification information and the audit log to the hospital audit log server 20 via the network, and receives the audit log policy from the hospital audit log server 20.

(Audit log management function)
Next, the audit log management function of the hospital audit log management support system 10 will be described. This function is a function for centrally maintaining and managing the audit log of each medical information device.

  FIG. 5 is a sequence diagram showing a flow of audit log management processing realized by the audit log management function. As shown in the figure, the audit log management process includes an audit log support specification acquisition request (step S1), an audit log support specification distribution (step S2), an audit log policy generation (step S3), and an audit log policy distribution (step S4), audit log generation (step S5), audit log distribution / storage (steps S6 and S7), and audit log presentation (step S8). Hereinafter, each process will be described in detail.

[Audit log support specification acquisition request: S1]
As shown in FIG. 5, first, an “audit log support specification acquisition request” is transmitted from the hospital audit log server 20 to each hospital audit log client device 30 via the network N. This request method may be a one-to-many communication method such as a network broadcast.

[Audit log support specification distribution: S2]
In response to the “audit log support specification acquisition request” received in step S1, each hospital audit client device 30 returns the audit log support specification information to the hospital audit log server 20 via the network. As described above, this information includes the names of events that can be generated to the maximum by the own device, the maximum items recorded in each event, the audit log transmission method supported by the own device, and the medical information device of the own device. Identification information is included.

  The transmission of the audit log support spec information to the hospital audit log server 20 is not intended to require an “audit log support spec acquisition request”, but is configured to be voluntarily transmitted from the hospital audit log client device. Also good.

[Audit log policy generation: S3]
The hospital audit log server 20 generates an audit log policy based on the audit log support specification information received from each hospital audit client device 30. The audit log policy is generated as follows, for example.

  First, based on the received audit log support specification information, the hospital audit log server 20 presents the “audit log support specification” to the hospital administrator via, for example, the display unit 206 (step S3a).

  FIG. 6 is a diagram showing an example of an audit log support specification presented by the hospital audit log server 20. In the example shown in the figure, audit log support is provided in a matrix form in which medical information device identification information is arranged in rows and event names are arranged in columns, with the intention of facilitating unified management of information The specs are presented. The hospital administrator executes each function permission / non-permission or selection from a plurality of presented functions with respect to each presented medical information device support specification (step S3b).

  The hospital audit log server 20 generates an audit log policy (audit log policy group) for each medical information device based on the setting information selected via the presentation screen (step S3c). The generated audit log policy group is stored in the storage unit 204 managed by the hospital audit log server 20 itself (step S3d), and the fact that the audit log policy for all medical information devices has been acquired from the storage unit 204 is the hospital audit log. The control unit 201 of the server 20 is notified (step S3e).

  The audit log policy group may store several configurations according to the security policy of the entire hospital. For example, it is assumed that the security regulation level in the hospital is defined in several stages according to the severity, and the security regulation level of the entire hospital is normal. In such a case, for example, a configuration of an audit log policy group that minimizes the selection of audit log events is generated and stored so as to prioritize resource load and performance of each medical information device. Further, when the security regulation level is high, the configuration of the audit log policy group in which all the audit log events that can be realized in each medical information device are selected may be generated and stored.

[Audit log policy distribution: S4]
The hospital audit log server 20 distributes the audit log policy group stored in the storage unit 204 managed by the hospital audit log server 20 to each hospital audit log client device 30 in accordance with an instruction from the hospital administrator. The protocol at the time of distribution is transmitted by any one of the audit log transmission methods presented in the audit log support specification for each medical information device.

  The distribution of the audit log policy group in this step may be performed based on the audit log analysis result by the hospital audit log server 20 itself. For example, when a recent audit log accumulated in the storage unit 204 managed by the hospital audit log server 20 is analyzed and a large number of warning or failure audit logs are generated, the audit log policy is generated in step S3. A more accurate audit log policy group may be automatically distributed from the audit log policy configuration.

[Audit log generation: S5]
Next, each hospital audit log client device 30 generates a hospital audit log for each audit log event related to the corresponding medical information device based on each audit log policy. As a generation method, for example, each application component in the corresponding medical information device calls and generates an audit log event generation interface published in the medical information device of the hospital audit log client device. Or, the corresponding hospital audit log client device 30 periodically scans various logs (operation logs, operation traces, device component status logs, alerts, etc.) that are already generated and stored in each medical information device. Extract and create information. Particularly in the latter case, each hospital audit log client device 30 maintains the correspondence between various log items, audit log events, and audit log event items.

  In each hospital audit log client device 30, the audit log event actually generated is only the audit log event specified in the audit log policy and the items in the audit log event, and the format thereof is, for example, IHE. A standardized schema definition is used.

[Audit log distribution / storage: S6, S7]
The hospital audit log for each audit log event generated in each hospital audit log client device 30 is transmitted from the hospital audit log client device 30 to the hospital audit log server 20. Although the transmission method is not particularly limited, for example, immediately after each hospital audit log client device 30 generates a hospital audit log in units of audit log events, the network is configured using the protocol specified in the sequential audit log policy. The technique of transmitting to the hospital audit log server 20 can be adopted. In addition, a plurality of audit log events are temporarily stored in the storage unit 307 of each hospital audit log client device 30 or a storage device in each medical information device, and can be determined according to the convenience of the own device, for example, when there is no load. At the specified time, it may be transmitted to the hospital audit log server 20 via the network using the protocol specified by the audit log policy. Furthermore, without being limited to transmission via a network, for example, a plurality of audit log events are temporarily stored in the storage unit 307 of each hospital audit log client device 30 or a storage device in each medical information device, and hospitals A configuration may be adopted in which the data is transmitted to the hospital audit log server 20 via a storage medium such as an MO, a CD, or a DVD according to an instruction from the side administrator. In addition, the flow of the process from step S3 to S6 is conceptually shown in FIG.

  The hospital audit log server 20 receives the hospital audit log generated by each hospital audit log client device 30 and stores it in the storage unit 204 managed by itself. At this time, although it can be received by methods other than those specified in the audit log policy (for example, only the network protocol is specified in the audit log policy for the medical information device A, the log transmitted by the media can also be received). ) By the check of the check unit 203, it is assumed that the device identifier attached to the audit log and the table stored in the storage unit 203 are referred to, and only matching items can be received.

[Audit log presentation: S8]
The hospital audit log server 20 displays the hospital audit log of each medical information device stored in the storage unit 204 managed by the hospital audit log server 20 in a predetermined form via the display unit 206, for example. For a consistent display, it is preferable to use a time-series display that combines all medical information device audit logs. Moreover, display for every medical information apparatus, every audit log event, every apparatus operator (login user) attached to the log, etc. are also possible as needed.

  Through the series of processing in steps S1 to S8 described above, the audit log of each medical information device is centrally maintained and managed on the hospital audit log server 20 side. If it is desired to change the audit log policy, the above-described processes may be executed again and reset as necessary.

  According to the configuration described above, the following effects can be obtained.

  According to the hospital audit log management support system, a hospital audit log policy is generated on the hospital audit log server side that centrally manages the system, and the hospital audit log client device 30 provided for each medical information device to be audited is used. Send it out. The hospital audit log client device 30 generates an audit log according to the audit log policy generated in the hospital audit log server. The generated audit log is automatically collected on the hospital audit log server side, and is combined and managed for each medical information device. Therefore, the administrator can maintain and manage the audit log in a lump without visiting many medical information devices in the hospital. As a result, the workload of the administrator can be reduced, and the audit log can be managed consistently (for example, without errors, contradictions, omissions, etc.) according to the desired criteria, improving the reliability of medical services. Can be made.

  Also, according to the hospital audit log management support system, an audit log policy can be generated on the hospital audit log server side based on the audit log support specification information for each medical information device. Therefore, an audit log policy suitable for the characteristics of each device can be set, and the degree of freedom of audit log management can be easily expanded.

  Further, according to the hospital audit log management support system, the audit policy of each medical information device can be freely changed at any timing on the hospital audit log server side as necessary. For example, when a hospital policy of “the patient name is not included in the audit log” is made, the administrator can collectively change and manage the audit log policy of a large number of apparatuses in the hospital. Also, regarding the operational aspects such as whether the hospital audit log generated by each device is transmitted for the convenience of its own device, whether it is transmitted in response to a request from the hospital audit log server side, or retained in its own device, This can be done by changing and managing the audit log policy of the device in a batch. Therefore, it is not necessary to go to a large number of medical information devices in the hospital, and the work burden on the administrator can be reduced.

(Second Embodiment)
A second embodiment of the present invention will be described. In this embodiment, the hospital audit log client device 30 is not an element of the medical information device, and the hospital audit log management support system is configured as an element of the hospital audit log server 20, for example.

  FIG. 8 is a diagram conceptually showing the configuration of the hospital audit log management support system 10 according to the present embodiment. In the figure, the exchange of information such as audit logs with the hospital audit log client device 30 corresponding to each medical information device is executed via a network.

  In the present embodiment, the hospital audit log generated by each medical information device in the audit log generation in step S5 is all the hospital audit logs that can be generated by each medical information device. The format may be a format that can be determined by the corresponding C) hospital audit log client.

  Each hospital audit log client device 30 is responsible for receiving the hospital audit log in step S6. Accordingly, the hospital audit log transmission protocol may be a transmission protocol defined by each medical information device.

  Furthermore, the hospital audit log client device 30 converts only the audit log event selected in the audit log policy into a standardized schema definition such as IHE based on the received hospital audit log, and then converts the hospital audit log server 20 to the hospital audit log server 20. The data is stored in the storage unit 204 managed by itself.

  Even if it is such a structure, the effect similar to 1st Embodiment can be acquired.

  Note that the present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. Specific examples of modifications are as follows.

  (1) Each function according to the present embodiment can also be realized by installing a program for executing the processing in a computer such as a workstation and developing the program on a memory. At this time, a program capable of causing the computer to execute the technique is stored in a recording medium such as a magnetic disk (floppy (registered trademark) disk, hard disk, etc.), an optical disk (CD-ROM, DVD, etc.), or a semiconductor memory. It can also be distributed.

  (2) In the audit log policy generation in step S3, encrypted communication can be specified for the hospital audit log communication protocol. In this case, the encryption method and the public key of the hospital audit log server 20 are included in the audit log policy. The hospital audit log client device 30 encrypts the hospital audit log itself to be transmitted or the communication path itself when receiving the hospital audit log in step S6 in accordance with the designation of the audit log policy.

  (3) In each of the above embodiments, an example of an assumed audit log schema is assumed to be defined by IHE. However, the target schema is not specified as defined by IHE, and any schema for hospital audit logs established by a standardization organization can be applied.

  In addition, various inventions can be formed by appropriately combining a plurality of components disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, constituent elements over different embodiments may be appropriately combined.

  As described above, according to the present invention, a hospital audit log management support system and a hospital audit log server that can easily execute hospital audit log setting and audit log maintenance and reduce the workload of the administrator are realized. Can do.

FIG. 1 is a diagram showing a configuration of a hospital audit log management support system 10 according to the first embodiment. FIG. 2 is a block diagram showing the configuration of the hospital audit log server 20. FIG. 3 is a block diagram showing the configuration of the audit log client device 30. FIG. 4 is a diagram illustrating an example of the data structure of the audit log policy. FIG. 5 is a sequence diagram showing a flow of audit log management processing realized by the audit log management function. FIG. 6 is a diagram showing an example of an audit log support specification presented by the hospital audit log server 20. FIG. 7 is a conceptual diagram for explaining an audit log management process executed by the audit log management function. FIG. 8 is a diagram showing a configuration of the hospital audit log management support system 10 according to the second embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 ... Hospital audit log management support system, 20 ... Hospital audit log server, 30 ... Audit log client apparatus, 201 ... Control part, 202 ... Log policy production | generation part, 204 ... Memory | storage part, 205 ... Transmission / reception part, 206 ... Display part, 207... Input unit, audit log client device 30 includes control unit 301, specification information generation unit 303, audit log generation unit 305, storage unit 307, transmission / reception unit 309, N ... network

Claims (10)

A plurality of audit log client devices, each of which is provided corresponding to a medical information device to be audited and generates an audit log that is a log of information related to an event in which patient information is handled, and the audit log client device via a network A hospital audit log server connected to each of the
The hospital audit log server
A determination unit for determining an audit log policy for determining at least one of a log item relating to the medical information device to be audited, a log storage mode, a log transmission method, and a log generation trigger;
Transmitting means for transmitting the audit log policy to each of the audit log client devices via a network;
Have
Each of the audit log client devices
Receiving means for receiving the audit log policy via a network;
Based on the audit log policy and an event occurring in the medical information device to be audited, an audit log generating means for generating an audit log related to the medical information device to be audited;
Storage means for storing the generated audit log;
Having
Hospital audit log management support system characterized by A plurality of audit log client devices, each of which is provided corresponding to a medical information device to be audited via a network, and generates an audit log that is a log of information relating to an event dealing with patient information, and the audit log client device A hospital audit log server connected to each of the
The hospital audit log server
A determination unit for determining an audit log policy for determining at least one of a log item, a log storage mode, a log generation method, and a log generation trigger regarding the medical information device to be audited;
Transmitting means for transmitting the audit log policy to each of the audit log client devices;
Have
Each of the audit log client devices
Receiving means for receiving the audit log policy;
Based on the audit log policy and an event occurring in the medical information device to be audited, an audit log generating means for generating an audit log related to the medical information device to be audited;
Storage means for storing the generated audit log;
Having
Hospital audit log management support system characterized by The hospital audit log server includes, via a network, identification information of the medical information device to be audited, the number and name of events that can be generated by the medical information device to be audited, and the medical information to be audited Receiving means for receiving audit log support information having at least one of items that can be recorded in each event that can be generated by the device and a method for transmitting the audit log to the hospital audit log server;
The determining means is a determining means for determining the audit log policy based on the received audit log support information;
The hospital audit log management support system according to claim 1 or 2.   At least one of the plurality of audit log client devices includes an audit log support information generation unit that generates the audit log support information related to the medical information device to be audited and transmits the audit log support information to the hospital audit log server via a network. The hospital audit log management support system according to claim 3, further comprising:   Each of the audit log client devices further includes a transmission unit that transmits the audit log support information to the hospital audit log server spontaneously or in response to a predetermined request. 4. The hospital audit log management support system according to any one of four.   6. Each of the audit log client devices further includes a transmission unit that transmits the audit log stored in the storage unit to the server via a network. A hospital audit log management support system according to one item. The determining means includes
Based on the audit log support information for each medical information device, generate a log policy input screen for each medical information device to be audited,
Determining the audit log policy according to the input through the log policy input screen;
The hospital audit log management support system according to any one of claims 1 to 6.   The hospital audit log management support system according to any one of claims 1 to 7, wherein the server further comprises storage means for receiving and storing the audit log from each of the audit log client devices. A hospital audit log server connected via a network with a plurality of audit log client devices each provided corresponding to a medical information device to be audited,
A determination unit for determining an audit log policy for determining at least one of a log item relating to the medical information device to be audited, a log storage mode, a log transmission method, and a log generation trigger;
Transmitting means for transmitting the audit log policy to each of the audit log client devices via a network;
An audit log relating to the medical information device to be audited, generated in at least one of the plurality of audit log client devices based on the audit log policy and an event occurring in the medical information device to be audited, Receiving means for receiving via a network;
Storage means for storing the received audit log;
The hospital audit log server characterized by comprising. A hospital audit log server connected to a medical information device to be audited via a network,
A determination unit for determining an audit log policy for determining at least one of a log item relating to the medical information device to be audited, a log storage mode, a log transmission method, and a log generation trigger;
Receiving means for receiving information about an event occurring in the medical information device to be audited via a network;
Based on the audit log policy and information on the event to be audited, an audit log generating means for generating an audit log on the medical information device to be audited;
Storage means for storing the generated audit log;
The hospital audit log server characterized by comprising.

Images