CN1416095A - System for automatic monitoring image management and communication - Google Patents

Abstract

A system for automatic monitoring image management and communication, belonging to hospital management equipment, which includes multiple PACS automatic monitoring clients (1), a PACS automatic monitoring server (2), and a pair of A plurality of PACS automatic monitoring service agents (3), the three are connected through a communication network to form an automatic monitoring client (1)  automatic monitoring service agent (3)  automatic monitoring server (2) connected by two-way information flow The three-tier working structure. The invention can monitor the operation of the whole PACS in real time and multi-level, greatly improves the maintainability and safety of the PACS, and reduces the management and use costs of the hospital PACS.

Description

A system for automatic surveillance image management and communication

Technical field:

The invention relates to a system for automatic monitoring image management and communication, in particular, a device for real-time monitoring and management of a clinical image archiving and communication management system (Picture Archiving and Communication System, PACS).

Background technique:

With the rapid development of information technology, hospitals are also gradually realizing the digitization and network management of medical information, and integrate various functions of medical image acquisition, processing, management, copying, analysis, resource sharing, remote transmission, remote consultation, etc. The integrated PACS is the center of modern medical imaging diagnosis and processing. Usually, a simple PACS can only include a PACS controller, collection gateway and display workstation. This small PACS can only achieve relatively single and limited functions, and its management is relatively simple, requiring only specialized personnel to maintain one by one. However, when the scale of PACS expands and multiple medical devices are connected to multi-acquisition gateways, and functions such as mutual access between various units, remote access, and RIS access are to be realized, PACS will be very complicated. How to ensure the efficient, stable and reliable operation of this huge system has become a problem that cannot be ignored, so the management and monitoring of PACS is particularly important. Prior to this, although there were some simple technical solutions for monitoring the PACS unit system, there was no system that could perform unified real-time monitoring and management of clinical PACS at multiple levels such as software, hardware, network, and security.

Invention content:

As mentioned above, how to carry out unified real-time monitoring and management of clinical PACS on multiple levels such as software, hardware, network and security is the technical problem to be solved by the present invention. Therefore, the purpose of the present invention is to provide a PACS automatic monitoring system, It takes each component module and network of clinical PACS as the monitoring object, from the software and hardware working conditions of PACS, the network operation conditions connecting each module, PACS access security, PACS medical image data flow, image storage, query/extraction status, etc. Monitor the PACS in various aspects to improve the work efficiency of PACS and reduce the management and use cost of PACS.

Technical solution of the present invention is:

A kind of PACS automatic monitoring system that the present invention proposes, it comprises a plurality of PACS automatic monitoring clients, is characterized in that a PACS automatic monitoring server end and a 1-to-many PACS automatic monitoring service agent for contacting them are also set, the three They are connected through the communication network, and form a three-layer working structure of PACS automatic monitoring client-PACS automatic monitoring service agent-PACS automatic monitoring server with information flow into two-way connection. Each PACS automatic monitoring client in said PACS automatic monitoring client comprises a client computer work station or server with PACS module function (as, PACS gathers gateway, PACS server or PACS image display workstation) and is arranged on this client The communication interface in the machine, and the event message sending interface (API) and the plug-in (Plugin) based on the DICOM communication standard stored in the client computer, said client computer is a special computer or server with PACS module function; Said PACS automatic monitoring server end comprises a computer or workstation, promptly is referred to as PACS automatic monitoring system server, and is arranged on the communication interface in this computer, and the PACS automatic monitoring system application program stored in the PACS automatic monitoring server ; The said 1-to-many PACS automatic monitoring service agent includes the client service agent program stored in the client computer and the server-side service agent program stored in the PACS automatic monitoring server.

Said PACS automatic monitoring client, PACS automatic monitoring server end and PACS automatic monitoring service agent constitute a client-service agent-server end three-layer work structure, wherein, the client sends monitoring information to this machine service agent, then It is transmitted to the server by the service agent; the memory queue (Queue) or file queue is used to realize asynchronous communication among the three, and the monitoring information is transmitted; it is suitable for the components of PACS based on different operating system platforms (Windows2000 NT/XP or UNIX/LINUX) The unit modules and the network forming the PACS.

The specific monitoring process is as follows:

<1> PACS automatic monitoring client-collecting local monitoring information: including defining PACS event messages and encoding PACS events according to different machines, programs and event categories; using API to embed client PACS applications to obtain PACS event messages or based on DICOM Communication standard plug-ins read PACS log files; periodically receive command queries from the PACS automatic monitoring server through the service agent to obtain local host information, network connectivity and user login information; use SQL-based database query statements to query and compare databases Records and other information collection methods. In addition, by assigning serial numbers to the image series entering the PACS automatic monitoring client, to track the state of the image series in the PACS, such as whether to enter the database, where to be transferred, when to extract, etc., to ensure that the image series in the PACS An image series can still be monitored and tracked for its individual invocation instances while being reused by different users.

<2>PACS automatic monitoring service agent——transfer monitoring information: comprise that said PACS automatic monitoring server actively sends query command to said PACS automatic monitoring client 1 through service agent, thereby obtain the active acquisition mode of monitoring information, and PACS automatic monitoring client 1 automatically sends event messages to the client service agent, and the server-side agent captures the passive mode of the message.

<3>PACS automatic monitoring server-classification and processing of monitoring information: including normal PACS event messages sent to the event log interface and image workflow interface display; user login/logout events sent to the security log interface; resource status of each module machine Events are sent to the host information display interface; image storage or query/extraction events are sent to the image tracking interface for display; error or warning events send different alarm signals according to the error level of the event (event registration record, machine beep, automatic call to the police or send a fax) etc.), notify the PACS maintenance personnel to rush to the scene in time.

In a nutshell, the object of the present invention is accomplished through the following operating principles:

The PACS automatic monitoring client is located in each PACS functional module machine, and obtains relevant PACS application program events on the PACS functional module machine from the local machine through the event message sending interface provided by the client terminal or reads PACS log files based on DICOM communication standard plug-ins. In addition, the state of the image series in PACS is tracked by assigning serial numbers to the image series entering the PACS automatic monitoring client, so as to ensure that the image series in the PACS can be monitored and tracked for each calling instance when they are reused by different users. The PACS automatic monitoring service agent is located at the client and server respectively, and it runs continuously in the background mode, and transmits the relevant monitoring information of the client to the server. The client service agent executes the reception of query commands from the PACS automatic monitoring server, and the collection of local events and information (such as PACS component software and hardware operating conditions, local access security, image data flow, image storage, query/extraction, etc.) , and send monitoring information to the PACS automatic monitoring server. The server-side service agent receives, records and processes the monitoring information sent by the client, and transmits it to the PACS automatic monitoring server in real time. The PACS automatic monitoring server is responsible for collecting the monitoring information from the PACS automatic monitoring client, and regularly checking the connection status of the network, and finally reports the obtained monitoring information to the PACS administrator through the PACS automatic monitoring server front-end user graphical interface or sends out different The alarm signal notifies the PACS administrator. PACS administrators can effectively maintain PACS through these monitoring information.

The client of the present invention is applied to each functional module of PACS, and mainly uses the event message sending interface provided by the client to embed the PACS application program of the client to obtain PACS event messages or to read PACS log files based on the DICOM communication standard plug-in, and the client service agent Periodically receive command queries from the PACS automatic monitoring server, collect local access security, image data flow, image storage, query/extraction and other monitoring information on the PACS functional module machine, and use SQL statements to track the database status. Additionally, serial numbers are assigned to image series entering the client to track the status of the image series within the PACS.

The client service agent of the present invention is not only responsible for monitoring information such as collecting events, PACS function module software and hardware operating conditions, local machine access security, image storage, query/extraction, but also to receive query commands from the server side through the communication port. The server sends the above monitoring information.

The server-side service agent of the present invention receives, records, and processes monitoring information from each client-side service agent, and simultaneously sends query commands to the client-side. It has a one-to-many relationship with the client service agent, and they together form a bridge connecting the client and the server.

The server end of the present invention provides a foreground user graphical interface, which summarizes the monitoring information collected from the client, and divides it into five categories of information, such as event log, security log, host information, image workflow, and image tracking, and displays them to the user. , and send out different alarm signals according to the error level. Among them, the event log can track, store, delete, and refresh the events generated during the current operation of PACS and view the event logs recorded in the past; the security log provides viewing of the user login status of the PACS module machine; the host information displays the hard disk usage and running programs of the PACS module machine And network connection and other conditions; image workflow shows the flow of images in PACS through animation; image tracking provides image usage; therefore, PACS administrators can well grasp the overall operation of PACS through this interface. Once problems are found, can be resolved in a timely manner.

Compared with the prior art, the present invention has outstanding substantive features and remarkable progress:

(1) The system of the present invention provides a powerful PACS automatic monitoring function, which can monitor the operation of the whole PACS in real time and at multiple levels, greatly improving the maintainability and safety of the PACS, so that the operation of the PACS is no longer a Operate in a dark box, and reduce the cost of hospital management and use of PACS.

(2) The system of the present invention can monitor the PACS modules running on Windows 2000/NT/XP, UNIX/LINUX platforms respectively, and follow unified framework and communication protocol; distributed structure and modular design and asynchronous communication mechanism The expansion capability of the automatic monitoring system is enhanced, so as to achieve the purpose of unified monitoring and arbitrary expansion.

(3) The automatic monitoring system of the present invention has no side effects on the operation of the PACS or any influence on its performance, and their operations are relatively independent without any constraints.

(4) The system of the present invention provides functions such as an easy-to-operate interactive interface, animation display image flow, and sending different alarm signals according to error levels, so that the PACS automatic monitoring system is easier to manage.

Brief description of the drawings:

FIG. 1 is a structural schematic diagram of an embodiment of the PACS automatic monitoring system of the present invention.

FIG. 2 is a schematic diagram of an active monitoring mode of the PACS automatic monitoring system according to an embodiment of the present invention.

FIG. 3 is a schematic diagram of a passive monitoring mode of the PACS automatic monitoring system according to an embodiment of the present invention.

FIG. 4 is a schematic diagram of the overall framework of the monitoring process of the PACS monitoring system according to the embodiment of the present invention.

FIG. 5 is a schematic flow chart of the event sending message interface in FIG. 4 .

FIG. 6 is a schematic diagram of the workflow of the event monitoring module in FIG. 4 .

FIG. 7 is a schematic diagram of the workflow of the security login monitoring module in FIG. 4 .

FIG. 8 is a schematic diagram of the workflow of the remote host information monitoring module in FIG. 4 .

FIG. 9 is a schematic diagram of the workflow of the image flow monitoring module in FIG. 4 .

FIG. 10 is a schematic diagram of the workflow of the image access monitoring module in FIG. 4 .

FIG. 11 is a schematic diagram of the workflow of the alarm module in FIG. 4 .

FIG. 12 is a schematic diagram of the workflow of the client service agent of the PACS monitoring system according to the embodiment of the present invention.

FIG. 13 is a schematic diagram of the workflow of the server-side service agent of the PACS monitoring system according to the embodiment of the present invention.

Detailed ways:

A better embodiment of the present invention is provided below in conjunction with Fig. 1～Fig. 13 and further elaborates to the embodiment of the present invention:

The system structure of the PACS automatic monitoring system of the present invention is as shown in Figure 1, comprises a plurality of PACS automatic monitoring clients 1, a PACS automatic monitoring server end 2 and a one-to-many PACS automatic monitoring service agent 3 three parts, client 1 The exchange of information with the server 2 is completed through the PACS automatic monitoring service agent 3, among which the memory queue (Queue) or file queue is used to realize asynchronous communication among the three. The system software includes PACS automatic monitoring system application program, client service agent program, server service agent program, client event message sending interface and plug-in based on DICOM communication standard. The monitoring methods are shown in Figure 2 and Figure 3, which are divided into active mode and passive mode. The active mode is that the PACS automatic monitoring server 21 of the PACS automatic monitoring server 2 sends relevant query commands to the client service agent 112, 122, 132 actively, and the service agent 112, 122, 132 responds to the request, obtains the local information of the client 1, and then The result is returned to the PACS automatic monitoring server 21. In the passive mode, the client 1 sends event messages to the client service agents 112, 122, and 132. After the server service agent 22 captures the messages sent by the client 1, it collects the information and sends it to the monitoring server 21 for display on the front desk of the PACS automatic monitoring server. interface. According to above-mentioned system structure and monitoring pattern, concrete monitoring process is referring to Fig. 4, as shown in the figure, under passive mode (Fig. Application modules 111, 121 are still monitoring objects (such as PACS application program modules 131) on the UNIX platform, and receive the event parameters generated by each component unit module of PACS through event sending message interface (API) 111', 121', 131', and send them Send to local (for NT platform) or write into local event queue 130 (for UNIX platform), notify client service agent 112, 122, 132 to receive. After the client service agent 112, 122, 132 receives, the information is summarized and sent to the server-side service agent 22, and the server-side service agent 22 writes in the local event log file 220 after receiving, for the server-side event monitoring module 221 to read and show. And under the active mode, by the remote host information monitoring module 223 of the server side, the safety login monitoring module 224 actively establishes network connection with the client service agent 112,122,132, sends relevant inquiry order, the client service agent 112,122,132 Collect local information and return the result to the corresponding module of the server.

The components of each part are described as follows:

The first part PACS automatically monitors client 1:

Each PACS automatic monitoring client 11,12,13 in a plurality of PACS automatic monitoring clients 1 of the present embodiment is respectively composed of a special computer workstation or a server with a PACS module function and a communication device arranged in the client. Interface, and the application program interface stored in the client computer, wherein in this embodiment, the special computer workstation or server with PACS module function is image acquisition gateway 11, PACS server 12 and image display workstation 13. Through the event message sending interface installed in each module machine, obtain the PACS running events that occur on the machine from the image acquisition gateway 11, PACS server 12, and image display workstation 13, or read the log recorded by each PACS module through a plug-in based on the DICOM communication standard file, and sent to the local client service agent 112, 122, 132, and then sent to the server 2 by the communication interface 113, 123, 133. In addition, considering that the image series in PACS will be reused by different users, on the client side 1, assign serial numbers to the image series entering it to track the state of the image series in PACS, such as whether to enter the database or to be transmitted Where to, when to extract, etc., to ensure that the image series in the PACS can still be monitored and tracked for each call instance when it is reused by different users.

The event message sending interface of the present embodiment adopts dynamic link library technology, and develops two sets of interfaces according to the client operating system platform, one is used in UNIX/LINUX environment, and the other is used in Windows 2000NT/XP. When the PACS application program wants to report an event to the PACS automatic monitoring system, it calls the unified event message sending interface, assembles the event data and sends it to the client service agent 112, 122, 132 of the machine. The workflow is shown in Figure 5, as shown in Figure 5. As shown, the event sending message interface program 30 is executed sequentially: step 301, the program starts; step 301, obtains client parameters (such as local information 111 ", 121 ", 131 "), step 302, fills the event message data packet, step 303 , added to the local event queue and step 304, the program ends.

The second part PACS automatically monitors the server side 2:

The PACS automatic monitoring server end 2 of the present embodiment takes the Intel (or AMD) framework CPU that contains communication interface 23 to be run quickly III700 as hardware platform, is usually referred to as PACS automatic monitoring server 21, software system is based on Windows 2000 (XP), adopts Visual C++6.0 development tool preparation. Its main function is to summarize the information received by the server-side service agent 22, and display five aspects of information such as event log, security log, host information, image workflow and image tracking through the front-end user graphical interface, and can automatically dial an alarm call for PACS management personnel keep abreast of the operation of PACS and provide corresponding technical support. The automatic monitoring server can also be developed using other operating systems, such as using the Java language to develop a cross-platform support system.

·Event log interface: record the current PACS operation events. The event types are divided into three types: common, warning and error. The event content includes event type, event ID number, event occurrence time, occurrence date, user name, computer name, and event source and event descriptions, etc. In addition, the event log interface can also store, delete, and refresh events generated during the current operation of PACS or view past event log records. In the event of an emergency, different alarm signals will be issued according to the error level of the event (event registration record, machine beeping, automatic alarm call or fax, etc.). Its work flow is shown in Fig. 6, and as shown in the figure, the working program 31 of event monitoring module 221 is carried out successively: step 310, program start; Step 311, read log file, step 312, interface display event and step 313, program ends.

·Security log interface: provide to view the user login status of each PACS module machine, to ensure that the images in the PACS are accessed safely. Security logs include security type, occurrence date, occurrence time, type, event ID, and login user name. Its workflow is shown in Fig. 7, and as shown in the figure, the work program 32 of security login monitoring module 224 is carried out successively: step 320, program starts; Step 321, read socket (Socket), obtain remote host security login information, step 322, the interface displays the security login information and step 323, the program ends.

Host information display interface: display the hard disk space usage of each PACS module machine, the current running program and status of PACS, and automatically or manually detect the network connection, and provide PACS administrators with the hardware status of each module machine and the running programs on it at all times software situation. Its workflow is shown in Fig. 8, and as shown in the figure, the work program 33 of remote host information monitoring module 223 is carried out successively: step 330, program starts; Step 331, reads socket (Socket), obtains remote host information, step 332 , the interface displays the remote host information and step 333, the program ends.

·Image workflow interface: animation shows the flow of images in PACS, which has a macroscopic and direct reflection of the entire PACS working status. The workflow is shown in Figure 9. When this module is working, it first establishes an event message pipeline with the client. In this way, the image flow messages of each client are sent to the server in real time through the pipeline, and are reflected in time. As shown in the figure, the working program 34 of the image flow monitoring module 222 is executed sequentially; step 340, start the program, step 341, open the event communication pipeline, step 342, read the event in the pipeline, step 343, judge the event type, and step 344 judge If it is a CT acquisition gateway, execute step 345 to change the CT acquisition gateway object state variable; if it is a PACS server, then execute step 346 to change the server object state variable; if it is an MR acquisition gateway, then execute step 347 to change the MR Collect the state variable of the gateway object; then, execute step 348 to close the event pipeline, and finally execute step 349 to end the program.

• Image tracking interface: use SQL (Structured Query Language) to query the database records stored in the remote PACS server 2 to obtain the usage of images. A route record for image storage, including patient ID number, Series UID, host name of sending image, image sending time, number of sending images, receiving destination host, image receiving time, number of receiving images, status and other information, through which information can be obtained The image acquisition gateway 11 stores the image in the PACS server database. The other is image query/extraction records, including patient ID number, Series UID, host name of sending QR request, AE Title of sending QR request, QR server, AE Title of server, time of sending request, number of requested images, receiving destination host name, Information such as the AE Title of the destination machine, receiving time, number of received images, and status, etc., provide information about the image being queried and extracted. Its workflow is shown in Fig. 10, and as shown in the figure, the work program 35 of image access monitoring module 225 is executed successively: step 350, start program, step 351, visit image storage database library, step 352, interface display image access information, finally, Step 353, the program ends.

Alarm: When an emergency event occurs, such as a major error in the PACS application program, a network failure or an unauthorized user intruding into the system, the PACS automatic monitoring application program can send out different alarm signals (event registration records, machine tweets) according to the event error level , Automatically call the police or send a fax, etc.). The automatic dialing of the alarm call is through the modem and telephone line in the communication interface of the PACS automatic monitoring server to call the management personnel's paging or phone call or send a fax to notify the PACS management personnel to rush to the scene quickly. This function adopts Telephony Application Programming Interface (TAPI) programming. Its work flow is shown in Figure 11, as shown in the figure, the work program 36 of the alarm module 226 is executed in sequence: step 360, start the program, step 361, receive pipeline events, step 362, determine whether it is an emergency? If it is not an emergency, then step 367 is executed, and the program ends; if it is an emergency, then step 363 is executed, and the standard function of making a call provided by Microsoft Corporation is called, step 364, the system calls dial, step 365, the phone reports to the police, and step 366 hangs up Telephone and step 367, the program ends.

The third part PACS automatic monitoring service agent 3:

The PACS automatic monitoring service agent 3 of the present embodiment comprises client service agent 112,122,132 and server end service agent 22 two parts, is positioned at client end 1 and server end 2 respectively, because it can act as an agent at both ends monitoring service, exchange Named for both information. PACS automatic monitoring service agents all adopt background operation mode, and can obtain relevant information in real time.

Customer service agents 112, 122, 132: According to the client 1 running Windows2000/NT and UNIX/LINUX, there are two versions, the background service is used under Windows 2000/NT, and the background daemon process is used under UNIX. Both passive and active modes can be used to provide real-time acquisition of local events, user information, disk information, and process information, and to package and send to the server end 2 and other functions. The workflow of client service agent program 14 is shown in Fig. 12, and as shown in the figure, client agent program 14 comprises main thread 140 and 3 sub-threads that generate simultaneously: host information query sub-thread 141, event receiving sub-thread 142, event sending The sub-thread 143 provides the functions of host information query and local event forwarding. As shown in the figure, the working steps of the main thread 140 in the client service agent program 14 are as follows: step 1401, program start, step 1402, initialization variable, step 1403, generate event receiving, event sending, and query service sub-threads, step 1404, wait for termination event, step 1405, release resources, and step 1406, end the program. After step 1403 is executed, host information query sub-thread 141, event receiving sub-thread 142 and event sending sub-thread 143 are simultaneously generated, and their working steps are respectively: the steps of sub-thread 141 are successively: step 1410, waiting for query request, step 1411, receiving the query request, step 1412, judging whether the request is legal? If not legal, execute step 1415, handle errors, and jump back to step 1410; The steps of the sub-thread 142 are as follows: step 1420, wait for the event, step 1421, receive the arrival event, step 1422, determine whether the event is legal? If not legal, then jump back to step 1420; if legal, then perform step 1423, to determine whether the queue is full? If it is full, execute step 1426, write the local log, then jump back to step 1420; if not full, then execute step 1424, put it into the event queue, step 1425 triggers the event ready message, then jump back to step 1420, wait for the event; child thread The steps in step 143 are as follows: step 1430, wait for the trigger event, step 1431, determine whether the queue is empty? If it is empty, jump back to step 1430; if not empty, then execute step 1432, take out the event, step 1433, connect to the server, step 1434, determine whether the connection is successful? If unsuccessful, execute step 1436, put it into the queue, and then jump back to step 1430; if the connection is successful, execute step 1435, send an event, then return to step 1430, and wait for a trigger event.

• Server-side service agent 22: responsible for receiving, recording and processing monitoring information from client-side service agents 112, 122, 132, and reporting to the local PACS automatic monitoring server 21. Because PACS automatic monitoring server 21 is based on Windows 2000, server-side service agent 22 uses background service to provide information in real time. The workflow of the service agent program 24 at the server end is shown in Fig. 13, and the main thread 240 generates an event receiving sub-thread 241 to continuously receive event messages from the client in the background. Start, step 2402, initialize variables, step 2403, generate event receiving subroutine step 2404, wait for termination event, step 2405, release resources, step 2406, program end. After step 2403 is executed, an event connection sub-thread 241 is generated, and its running steps are as follows: step 2410, wait for a network event, step 2411, receive an event, and step 2412, determine whether the event is legal? If not legal, return to step 2410; if legal, execute step 2413, write log file, step 2414, judge whether it is special legal? If not, return to step 2410; if it is special and legal, execute step 2415, send it to the event pipeline, and finally return to step 2410, waiting for network events.

Communication between the two: the transmission of information between the client service agent 112, 122, 132 and the server service agent 22 follows the TCP/IP and DICOM protocols, and the hardware uses the communication interfaces 113, 123 installed on the machines at both ends , 133, communication interface 23, the establishment of communication software adopts Winsock API and Unix socket.

Claims (18)

1, a kind of system that is used for automatic monitoring image management and communication, comprises a plurality of PACS automatic monitoring clients (1), it is characterized in that, also be provided with a PACS automatic monitoring server end (2), and it and this multiple The PACS automatic monitoring client (1) is connected with one pair of multiple PACS automatic monitoring service agents (3), and forms an automatic monitoring client (1) connected by two-way information flow in sequence Automated Monitoring Service Agent(3) Automatically monitor the three-layer working structure of the server side (2). 2. The system for automatic monitoring image management and communication according to claim 1, characterized in that, each PACS automatic monitoring client in said plurality of PACS automatic monitoring clients (1) includes a The client computer of the PACS module function, the communication interface set in the client computer, the event message sending interface stored in the client computer and the plug-in based on the DICOM communication standard. 3. The system for automatically monitoring image management and communication according to claim 2, characterized in that said PACS functional module is an image acquisition gateway (11) or a PACS server (12) or an image display workstation (13) . 4. The system for automatically monitoring image management and communication according to claim 3, characterized in that an image acquisition gateway application program (111) resides in the client computer containing the image acquisition gateway (11), which forms The information flow output of the event is further provided with a client service agent (112) receiving the event information flow and a communication interface (113) connected bidirectionally with it on the client computer. 5. The system for automatically monitoring image management and communication according to claim 3, characterized in that, in the client computer containing the PACS server (12), there is a PACS server process (121), which forms the information of the event Stream transmission, also be set as the client service agent (122) and communication interface (123) of two-way connection on this client computer, and accept the event output information of this PACS server process (121) by this client service agent (122) flow. 6. The system for automatic monitoring image management and communication according to claim 3, characterized in that, in the client computer containing the image display workstation (13), there resides an image display workstation application program (131), which forms The event information flow output is also set on the client computer as a client service agent (132) and a communication interface (133) of two-way connection, and the client service agent (122) accepts the image display workstation application program (131) The event output information flow. 7. The system for automatic monitoring image management and communication according to any one of claims 2-6, characterized in that said client computer is a dedicated computer workstation or server with PACS module functions. 8. The system for automatic monitoring image management and communication according to claim 1, characterized in that said PACS automatic monitoring server end (2) comprises a PACS automatic monitoring system application program module residing in An automatic monitoring server (21), and a server-side service agent (22) and a communication interface (23) which are arranged in the PACS automatic monitoring server (21) and are sequentially connected with the PACS automatic monitoring system application program module in two directions. 9. The system for automatic monitoring image management and communication according to claim 8, characterized in that said PACS automatic monitoring server (21) is a PC or a workstation. 10. The system for automatic monitoring image management and communication according to claim 1 or 2 or 3 or 4 or 5 or 6 or 8, characterized in that said 1 pair of multiple PACS automatic monitoring server agents (3 ) includes multiple client service agents (112, 122, 132) and communication interfaces (113, 123, 132) and communication interfaces (113, 123, 133), on each client computer, resides respectively corresponding client service agent program; On this PACS automatic monitoring server (21), the server end service agent (22) that resides PACS automatic monitoring server end service agent program is set ), and a communication interface (23) that forms a two-way connection with it; the plurality of communication interfaces (113, 123, 133) respectively pass through the corresponding communication network (11323, 12323, 13323) and the communication interface (23) to monitor Information flows into two-way links. 11. The system for automatic monitoring image management and communication according to claim 1, characterized in that said automatic monitoring client (1)

Automated Monitoring Service Agent(3) The three-layer working structure of the automatic monitoring server (2) refers to that the multiple automatic monitoring clients (1) send the monitoring information to the automatic monitoring service agent (3), and then the automatic monitoring service agent (3) transmits it to the server (2); In addition, automatic monitoring server end (2) also sends order, sends this multiple automatic monitoring client end (1) by automatic monitoring service agent (3), executes and returns result to automatic monitoring server end (2) ). 12. The system for automatic monitoring image management and communication according to claim 11, characterized in that, a plurality of PACS automatic monitoring clients (1), automatic monitoring service agents (3) in said three-layer working structure ) and the automatic monitoring server (2) use memory queues or file queues to realize asynchronous communication and transfer monitoring information, which is suitable for each component module of PACS based on different operating system platforms and the network forming PACS. 13. The system for automatic monitoring image management and communication according to claim 12, characterized in that said operating system platform includes Windows2000 NT/XP or UNIX/LINUX. 14. The system for automatic monitoring image management and communication according to claim 11 or 12, characterized in that the monitoring function of said multiple PACS automatic monitoring clients (1) is to collect local monitoring information, which includes Define PACS event messages and encode PACS events according to different client computers, programs and event categories: use API to embed client-side PACS applications to obtain PACS event messages or plug-ins based on DICOM communication standards to read PACS log files; through service agents (12 ) Periodically receive command inquiries from the PACS automatic monitoring server end (2), obtain local host information, network connectivity and user login information; use SQL-based database query statements to query and compare multiple information collection methods such as database records; In addition, by assigning serial numbers to the image series entering the client (1), the state of the image series in the PACS is tracked to ensure that the image series in the PACS can still be monitored and invoked for each instance when they are reused by different users. track. 15. The system for automatic monitoring image management and communication according to claim 14, characterized in that said sequence numbers are assigned to the image series entering the multiple PACS automatic monitoring clients (1), tracking The status of the image series in the PACS refers to whether it is entered into the database, where it is transmitted, and when it is extracted. 16. The system for automatic monitoring image management and communication according to claim 11 or 12, characterized in that said PACS automatic monitoring service agent (3) has a function of transmitting monitoring information, which includes said The PACS automatic monitoring server (21) actively sends an inquiry command to the PACS automatic monitoring client (1) to obtain the active acquisition mode of monitoring information through the service agent (3), and the PACS automatic monitoring client (1) automatically sends an event message to the client The service agent (112, 122, 132), and the passive mode of the message is captured by the server-side agent (22). 17. The system for automatic monitoring image management and communication according to claim 11 or 12, characterized in that said PACS automatic monitoring server end (2) is used for classification and processing of monitoring information, which includes normal PACS event message sending event log interface and image workflow interface display; user login/logout event sending security log interface; resource status event sending host information display interface of each module; image storage or query/extraction event sending image tracking interface for display; Error or warning events send out different alarm signals according to the error level of the event, and notify PACS maintenance personnel to rush to the scene in time. 18. The system for automatic monitoring image management and communication according to claim 17, characterized in that, said PACS automatic monitoring server end (2) sends different alarm signals to errors or warning events according to the event error level, Divided into event registration records, machine beeping, automatic dialing to the police or sending faxes.

Images