JP2014056545A - Medical device control system and medical device control server - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a medical device control system and a medical device control server which can smoothly provide required data and perform required operation.SOLUTION: A server comprises: a load reception unit which receives a device load state value from a medical device and acquires a network load state value from a network; and a server control unit which acquires a feasibility value corresponding to the device load state value by comparing the device load state value received by the load reception unit and a device load state value of device load information, and also performs determination processing which determines that it is possible to perform required processing and transmits an acquisition request to the medical device when the acquired feasibility value and a network feasibility value satisfy predetermined conditions, then acquires the required data. The medical device comprises: a device control unit which acquires its own device load state value on receiving the acquisition request from the server; and a device communication unit which transmits the device load state value to the server.

Description

  The present invention relates to a medical device control system and a medical device control server.

  As a background art of this technical field, Patent Document 1 discloses a technique for smoothly distributing software to a plurality of medical devices without increasing the system load when the software is updated remotely.

JP 2007-164371 A

  The patent document describes a smooth software download method for a plurality of medical devices and servers without increasing system load such as server capacity redundancy and network capacity expansion. However, in the above-mentioned patent document, only software download is effective, and it is not possible to cope with any operation on the medical device.

  In such a system, data is often transmitted and received between mobile communication terminals and medical devices that have been rapidly spreading in recent years, and an excessive load may be imposed on the medical device. Specifically, various image data and measurements from various medical devices such as MRI (Magnetic Resonance Imaging system) devices and CT (Computed Tomography) devices via lines from terminals such as notebook PCs (Personal Computers) and smartphones. When a value is acquired or a large number of operations are performed on these medical devices, a load associated with an excessive processing request for the medical devices and a load associated with an increase in traffic in the network increase.

  In general communication that does not use a medical device, due to such a load, even if the desired data cannot be acquired or cannot be operated due to a timeout or the like, another data acquisition request or operation request is issued. The acquisition and operation may be performed by performing. However, at medical sites where medical devices are used, it is often necessary to urgently acquire data or operate medical devices due to sudden illnesses due to accidents, etc. If the timing is missed, appropriate medical practices cannot be performed. Can be fatal to the patient. For this reason, the medical device or the server or system that manages the medical device has an environment that can promptly respond to data acquisition requests and operation requests and smoothly provide the requested data and operations even when such a situation occurs. It is necessary to arrange it.

  The present invention has been made in view of the above, and an object of the present invention is to provide a medical device control system and a medical device control server that can smoothly provide requested data and operations.

  In order to solve the above-described problems and achieve the object, a medical device control system according to the present invention transmits a data acquisition request to a medical device in response to the acquisition request from the terminal. And a medical device control system that is connected to the server via a network and receives the acquisition request from the server and provides the data, wherein the server receives the acquisition from the terminal. The server communication unit that receives the request is associated with an apparatus load state value that indicates a load ratio of the medical apparatus and an executable value that indicates the number of acquisition requests that can be executed by the medical apparatus in the state of the apparatus load state value. Device load information, a network load state value indicating a load ratio of the network, and the network load state value through the network. A storage unit that stores network load information that associates a network executable value indicating the number of requests that can be transmitted and received; receives the device load status value from the medical device; and receives the network load status value from the network The load receiving unit to obtain, and the device load state value received by the load receiving unit and the device load state value of the device load information are compared to obtain an executable value corresponding to the device load state value, and A network executable value is obtained by comparing the network load status value acquired by the load receiving unit with the network load status value of the network load information, and the acquired executable value and the network executable value satisfy a predetermined condition. If satisfied, it is determined that the requested processing is possible, and the acquisition request is transmitted to the medical device And a server control unit that acquires the data, and when the medical device receives the acquisition request from the server, the device control unit that acquires the device load state value of the device, A device communication unit that transmits a device load state value to the server.

  The medical device control server according to the present invention is a medical device control server that receives a data acquisition request from a terminal and transmits the acquisition request to a medical device that provides the data via a network. A server communication unit that receives the acquisition request from a requesting terminal, a device load state value that indicates a load ratio of the medical device, and the number of acquisition requests that the medical device can execute in the state of the device load state value Device load information associated with an executable value, a network load state value indicating a load ratio of the network, and a network executable state indicating the number of the acquisition requests that can be transmitted and received through the network in the network load state value A storage unit that stores network load information associated with a value; and the device load state value is received from the medical device; The load receiving unit that acquires the network load state value from the network, the device load state value received by the load receiving unit, and the device load state value of the device load information are compared to correspond to the device load state value Acquiring an executable value, comparing the network load state value acquired by the load receiving unit with the network load state value of the network load information to acquire a network executable value, and acquiring the executable value and the A server control unit that determines that the requested process is possible when the network executable value satisfies a predetermined condition, performs a determination process of transmitting the acquisition request to the medical device, and acquires the data And.

  ADVANTAGE OF THE INVENTION According to this invention, the medical device control system and medical device control server which can provide the required data and operation smoothly can be provided.

It is a figure which shows the structural example of the system which concerns on this embodiment. It is a figure which shows the structural example of the database for control. It is a figure which shows the structural example of medical apparatus information. It is a figure which shows the structural example of terminal information. It is a figure which shows the structural example of load information. It is a figure which shows the example of a network load setting screen. It is a figure which shows the example of an apparatus load setting screen. It is a flowchart which shows the process sequence of request content transmission judgment processing. It is a figure which shows the data structural example of an acquisition request. It is a figure which shows the example of the apparatus load information transmitted from the database monitoring part of a medical device. It is a figure which shows the example of the content of the acquisition request temporarily hold | maintained at a data queue (before rearrangement). It is a figure which shows the example of the content of the acquisition request temporarily hold | maintained at a data queue (after rearrangement).

  A system configuration and embodiments of a medical device control system and a medical device control server according to the present invention will be described below with reference to the accompanying drawings.

  FIG. 1 is a diagram illustrating a configuration example of a system according to the present embodiment. As shown in FIG. 1, this system has a plurality of terminals 100, a server 200 connected via a wide area network N1, and a plurality of medical devices 300 connected to the server 200 via a hospital network N2. Configured. First, the terminal 100 will be described.

  The terminal 100 is a terminal that accesses the present system to acquire desired data or operates the medical device 300. For example, a personal computer (PC) used by a medical practitioner such as a surgeon or physician, a portable terminal And the like. As illustrated in FIG. 1, the terminal 100 includes an input receiving unit 101, a display unit 102, a communication unit 103, and a control unit 104. In the description of the present embodiment, the case where the terminal 100 accesses the system and makes a data acquisition request has been described. However, the terminal 100 makes some operation request (for example, an X-ray diagnostic apparatus) to the medical apparatus 200. The same applies to the case where a request for imaging operation or the like in the X-ray CT apparatus or MRI apparatus is performed. Each terminal 100 has the same configuration.

  The input receiving unit 101 is, for example, a keyboard or a touch panel, and receives an operation from an operator. Specifically, the input receiving unit 101 receives a data acquisition request for the medical device from the operator. The specific contents of the acquisition request will be described later using a flowchart.

  The display unit 102 is, for example, an LCD (Liquid Crystal Display), and displays a screen for inputting various requests to the server 200 or a result processed by the server 2. Specifically, the display unit 102 displays the result for the acquisition request from the terminal 100 to the system.

  The communication unit 103 is, for example, a NIC (Network Interface Card), and manages various data communication with the server 200 via the wide area network N1. Specifically, the communication unit 103 transmits and receives various types of information related to the acquisition request described above to and from the server 200.

  The control unit 104 is a CPU (Central Processing Unit), for example, and controls the operation of each unit described above. Next, the server 200 will be described.

  The server 200 is a server that receives an acquisition request from the terminal 100 via the wide area network N1, acquires the requested data from the medical device 300 connected via the in-hospital network N2, and transmits the result to the terminal 100. . As shown in FIG. 1, the server 200 includes a receiving unit 201, a data queue 202, a control database 203, a control unit 204, a load receiving unit 205, and a transmitting unit 206. Yes.

  The receiving unit 201 receives an acquisition request from the terminal 100 and outputs the received acquisition request to the data queue 202. In addition, the reception unit 201 transmits data acquired in response to the received acquisition request to the terminal 100 that has made the acquisition request.

  The data queue 202 holds the acquisition request output from the reception unit 201 and outputs the held acquisition request to the transmission unit 206 in accordance with an instruction from the control unit 204.

  The control database 203 stores control information (generically referred to as medical device information, terminal information, and load information as described above) for controlling various processes for acquiring data according to the request indicated in the acquisition request. .

  FIG. 2 is a diagram illustrating a configuration example of the control database 203. As illustrated in FIG. 2, the control database 203 includes, as control information, medical device information 2031 that stores information related to the medical device 300, terminal information 2032 that stores information related to the terminal 100, and a load receiving unit 205 that includes a medical device. And load information 603 for storing numerical values for obtaining data to be transmitted from the data queue 202 based on device load information (described later) received from 300.

  The medical device information 2031 is information that identifies a medical device 300 that is requested to be acquired and indicates conditions under which the medical device 300 executes processing in parallel. FIG. 3 is a diagram illustrating a configuration example of the medical device information 2031. As illustrated in FIG. 3, the medical device information 2031 stores a medical device name, an IP address, a host name, and the number that can be simultaneously executed in association with each other. The medical device name stores an identifier for uniquely identifying the medical device 300. The IP address stores an IP address assigned to the medical device 300. The host name stores the host name assigned to the medical device 300. The number that can be executed simultaneously stores the number of processes that the medical device 300 can execute simultaneously. For example, in FIG. 3, the medical device A has an IP address of “100.204.11” and a host name of “device A”, and up to two processes can be executed simultaneously as conditions under which the processes can be executed simultaneously. Is shown.

  The terminal information 2032 is information that identifies the terminal 100 that has requested acquisition and indicates the priority of the acquisition request by the terminal 100. FIG. 4 is a diagram illustrating a configuration example of the terminal information 2032. As illustrated in FIG. 4, the terminal information 2032 stores a terminal ID, a host name, and a priority in association with each other. The terminal ID stores an identifier for uniquely identifying the terminal 100. The host name stores the host name assigned to the terminal 100. The priority stores the priority of processing indicated in the acquisition request. In FIG. 4, the acquisition request from the terminal A is processed with the highest priority divided into three levels, HIGH, MIDDLE, and LOW. However, the number and level setting method are not limited to this, and priority is given by numerical values. The degree may be determined.

  The load information 2033 is information indicating the number of processes that can be executed simultaneously according to the network load of the hospital network N2 and the load of the medical device 300. FIG. 5A is a diagram illustrating a configuration example of the load information 2033. As illustrated in FIG. 5A, the load information 2033 stores a load state, a network executable number, and a medical device executable rate in association with each other. The load state stores the load state of the database of the network and the medical device. The load state is defined as a ratio to the number of transactions that can be processed at one time. In both cases of the network load and the database load, the no load state is set to 0.0, and the load reaches the upper limit. .0. The network executable number stores the number of requests that can be sent to the hospital network with respect to the load state. The medical device executable rate stores a rate that the medical device can execute with respect to the load state. For example, if there is a medical device with the number of simultaneously executable medical devices 5 in the medical device information 2031 and the medical device executable rate is 0.6, [number of simultaneously executable] × [medical device executable rate] = 3.0. The current executable request of the medical device 300 is 3. In the example shown in FIG. 5A, the network executable number is set to 0 and the medical device executable rate is set to 0 even when the load is 0.9 in order to provide a margin for the load.

  In the example shown in FIG. 5A, the case where the load of the hospital network N2 and the load of the medical device 300 are stored in one table format is shown, but actually, as shown in FIG. 5B and FIG. 5C, The load on the in-hospital network N2 and the load on the medical device 300 are set in separate tables. In FIG. 5B, as an example of setting the load of the network N2, an example of a network load setting screen displayed on a display unit (not shown) included in the medical device 300, a display unit included in the terminal 100 or the medical device 300, or the like. Is shown. As shown in FIG. 5B, in the network load setting screen, when the load (load state) of the network N2 is 30% (0.3), the number of executable acquisition requests is set to 20. .

  In FIG. 5C, as an example of setting the load of the medical device 300, device load setting displayed on a display unit (not shown) included in the medical device 300, a display unit included in the terminal 100 or the medical device 300, or the like. An example of the screen is shown. As shown in FIG. 5C, in the apparatus load setting screen, when the load (load state) of the medical apparatus 300 is set to 30% (0.3), the executable acquisition request rate is set to 80%. ing.

  As described above, the system administrator or the like can freely set the number of acquisition requests to be processed from the screen according to the load state of the hospital network N2 and the medical device 300. . Accordingly, an appropriate load state can be set according to the line speed of the network N2, the specifications and environment of the medical device 300, and the characteristics of the hospital having the system, and the setting operation and setting contents can be easily confirmed. be able to.

  For example, when the line speed of the network is fast and the processing speed of the medical device 300 is fast, it is possible to set the load state high so that the network and the medical device can be used more effectively. Also, in hospitals where there is a high possibility of urgent medical practice, such as emergency medical centers, etc., an environment that can handle such urgent medical practice by setting a low load state and providing more room for the system On the other hand, in hospitals and the like that are unlikely to perform urgent medical activities such as private hospitals, it is possible to set the load state high and use the network and devices more effectively. . In the present embodiment, the description has been made on the assumption that the load state of the network is the load state of the in-hospital network N2, but the load state of the wide area network N1 may be set similarly.

  The control unit 204 controls the operation of each unit of the server 200, such as storing the control information described above in a control database. Specific operations of the control unit 204 will be described later with reference to flowcharts.

  The load receiving unit 205 receives device load information (described later) indicating the database load of the medical device 300 and stores it in a memory (not shown). In addition, the load receiving unit 205 acquires network load information indicating the network load of the hospital network N2 at a constant period and stores it in the above-described memory. In the present embodiment, the database load (database usage rate) is described as an example in which the medical device 300 is burdened. For example, the medical device 300 uses the CPU usage rate or memory usage rate of the medical device. Of course, it is possible to determine the processing of the acquisition request using an index representative of the specifications of the apparatus such as a database, a CPU, and a memory.

  The transmission unit 206 transmits the acquisition request transmitted from the data queue 202 to the hospital network N2, and transmits the acquisition request to the medical device 300 specified in the acquisition request.

  Note that the information stored in the medical device information 2031, terminal information 2032, and load information 2033 as the control information described above is appropriately controlled by the control unit 204 when the system starts operating or when the medical device 300 is added or deleted. Add to database 203. Next, the medical device 300 will be described.

  The medical device 300 is an arbitrary device used in the medical field, and is configured to operate according to control by predetermined software. Specific examples of the medical apparatus 300 include an electronic medical record management system, a medical image management system, a medical accounting management system, a medical image diagnostic apparatus (an X-ray diagnostic apparatus, an X-ray CT apparatus, an MRI apparatus, etc.), an imaging system, and an image interpretation system. There are systems. All of the medical devices 300 have the same configuration.

  As illustrated in FIG. 1, the medical device 300 includes a database monitoring unit 301, a database 302, and a control unit 303.

  The database monitoring unit 301 monitors the load on the database 302. The database monitoring unit 301 is operated by software corresponding to the type of the database 302 and transmits load information indicating the load on the database to the load receiving unit 205 of the server 200 at a fixed period. Specific contents of the load information transmitted by the database monitoring unit 301 will be described later using a flowchart.

  The database 302 stores various data processed by the medical apparatus 300 (for example, in the case of an X-ray image apparatus, image data at the time of X-ray diagnosis for each patient).

  The control unit 303 controls the operation of each unit of the medical device 303. Next, a description will be given of processing (request content transmission determination processing) in the case where data is requested in the present system and data is provided after determining the request content.

  FIG. 6 is a flowchart illustrating a processing procedure of request content transmission determination processing. As shown in FIG. 6, in the request content transmission determination process, first, the control unit 104 of the terminal 100 transmits a data acquisition request to the server 200 via the communication unit 103 and the wide area network N1 (S11). In the following, processing for a certain terminal 100 is described, but actually, a data acquisition request is transmitted from each of the terminals 100 at an arbitrary timing.

  Specifically, the control unit 104 of the terminal 100 issues an acquisition request such as finding report data for the doctor in charge of operating the terminal 100 to explain to the patient or CT scanned examination image data. Then, the data is transmitted to the server 200 via the communication unit 103 and the wide area network N1.

  FIG. 7 is a diagram illustrating a data configuration example of an acquisition request. As shown in FIG. 7, the acquisition request includes a terminal ID for identifying the terminal that requested acquisition, the priority of the data requested for acquisition, and a medical device for specifying the medical device 300 that holds the data requested for acquisition. The device name (requested medical device) is associated with the request content indicating the content of the data requested to the requested medical device. In FIG. 7, for example, the terminal 100 whose terminal ID is “terminal A” acquires an examination image of the patient A from the medical device 300 identified by the medical device A as the priority “HIGH” with respect to the server 200. This indicates that the request to be transmitted is transmitted as an acquisition request, and is more urgent than the acquisition requests from the terminals B and C. In FIG. 7, the acquisition requests are described in a table format that is combined into one, but in actuality, acquisition requests are transmitted from each terminal 100 for each record. Further, although the present embodiment has been described on the assumption that priority is set in both the acquisition request transmitted by the terminal 100 and the terminal information stored in the server 200, the priority of the terminal 100 requested to acquire is described. Can be stored in either one of them.

  When the acquisition request is transmitted from the terminal 100, the receiving unit 201 of the server 200 receives the acquisition request, and stores the acquisition request in the data queue 202 in descending order of priority included in the acquisition request (step S12). . As described above, by sorting and storing the data in the data queue 202 in descending order of priority, for example, it is possible to quickly determine whether to provide data according to a data acquisition request with high urgency.

  When the acquisition request is stored in the data queue 202, the control unit 204 selects the first acquisition request (that is, the acquisition request with the highest priority at that time) from the acquisition requests stored in the data queue 202. Then, the requested medical device and request content included in the acquisition request are read, and the name of the medical device described in the requested medical device is output to the load receiving unit 205 (step S13).

  The load receiving unit 205 specifies device load information indicating the current load state of the medical device 300 from the device load information received from the medical device 300 at that time using the name of the medical device as a key, and The load state value indicating the load of the database 302 of the medical device 300 described therein is read (step S14). The device load information is information indicating the current load state of each medical device 300.

  FIG. 8 is a diagram illustrating an example of device load information transmitted from the database monitoring unit 301 of the medical device 300. As illustrated in FIG. 8, the device load information is information in which a medical device name for specifying the medical device 300 and a load state value in the database 302 of the medical device 300 are associated with each other. In FIG. 8, for example, the load state for the medical device A at a certain point in time is “0.5”, and a 50% load factor is applied to the medical device.

  Then, the control unit 204 accesses the control database 203 using the load state value included in the device load information received by the load receiving unit 205 as a key, and records a record including the same load state value as the load state value. The medical device feasibility ratio of the identified record is acquired, and the number of acquisition requests executable by the medical device is obtained (step S15). For example, when the database load of the requested medical device is 0.5, the control unit 204 accesses the load information shown in FIG. 5A using the numerical value as a key, and the corresponding medical device executable ratio “0.7”. To get. Further, when the requested medical device read in step S13 is the medical device B, the control unit 204 accesses the medical device information shown in FIG. 3 using the name as a key, and the corresponding simultaneously executable number “3”. To get. The control unit 204 multiplies the medical device executable ratio “0.7” and the simultaneous executable number “3” to obtain the number of requests that can be executed by the requested medical device at the present time. Specifically, the control unit 204 obtains the number of acquisition requests that can be executed by the requesting medical apparatus as [simultaneous execution count] × [medical apparatus executable ratio] = 2.1.

  Subsequently, the control unit 204 acquires the network load information of the in-hospital network N2 received by the load receiving unit 205, and acquires the number of acquisition requests that can be executed by the in-hospital network N2 (step S16). For example, when the network load of the hospital network N2 is “0.5”, the control unit 204 accesses the load information shown in FIG. 5A using the value as a key, and acquires the corresponding network executable number “4”. To do.

  Then, the control unit 204 determines whether or not the acquisition request stored in the data queue 202 can be sent to the hospital network N2 (step S17). Specifically, the control unit 204 determines that the device load information acquired in step S14 is “1.0” or more and the network load information acquired in step S16 is “1.0” or more. In this case, it is determined that at least one acquisition request can be processed, and it is determined that the acquisition request stored in the data queue 202 can be sent to the hospital network N2.

  When the control unit 204 determines that the acquisition request can be transmitted from the data queue 202 (step S17; Yes), the data queue 402 transmits the acquisition request to the hospital network N2 (step S18). On the other hand, if the control unit 204 determines that the acquisition request cannot be sent from the data queue 202 (step S17; No), the process proceeds to step S19 without doing anything. When the processing in step S18 is completed, an acquisition request is transmitted to the target medical device 300 only when the loads on the medical device 300 and the in-hospital network N2 satisfy certain conditions, and various processes for data acquisition are performed. After being executed on the medical device 300 side, the requested data is provided to the terminal 100 via the hospital network N2, the server 200, and the wide area network N1.

  Then, the control unit 204 reads the next acquisition request from the data queue 202 (step S19), and determines whether or not the next acquisition request exists in the data queue 202 (step S20).

  When it is determined that the next acquisition request does not exist in the data queue 202 (step S20; No), the control unit 204 ends the request content transmission determination process illustrated in FIG. On the other hand, when it is determined that the next acquisition request exists in the data queue 202 (step S20; Yes), the control unit 204 returns to step S13 and repeatedly executes the subsequent processing.

  As described above, in the present system, the requested content transmission determination process shown in FIG. 6 is performed, so that requested data and operations can be smoothly provided. Specifically, smooth data transmission / reception between the plurality of terminals 100 and the plurality of medical devices 300 can be provided without imposing an excessive load on the medical device 300 and the in-hospital network N2.

  In the above-described embodiment, the case has been described in which data is smoothly provided to the terminal 100 requested for acquisition in consideration of the priority, but when the priority is the same, the received acquisition request, The acquisition request held in the data queue 20 is compared, and the order of storing in the data queue 202 is determined according to the request content.

  For example, the control unit 204 compares the request content of the acquisition request received by the receiving unit 201 with the request content of the acquisition request held in the data queue 202, and the acquisition request currently held in the data queue 202 is In the state illustrated in FIG. 9, when the receiving unit 201 newly receives an acquisition request from the terminal C having the priority HIGH, the priority of the received acquisition request is HIGH. The request contents held in 202 are inserted into the data queue 202 and rearranged so that the request contents are in the order before the MIDDLE acquisition request. As a result, the order of the acquisition requests is as shown in FIG. When the request content transmission determination process shown in FIG. 8 is executed, since it is transmitted to the in-hospital network N2 from the top acquisition request, even a newly received acquisition request has a low priority acquisition. It is held in the data queue 202 in the order before the request, and is sent out to the hospital network 7. Therefore, regardless of the time when the acquisition request is received, for example, a highly urgent acquisition request can be processed with priority.

In addition, this invention is not limited to an above-described Example, Various modifications are included. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described. Further, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. Further, it is possible to add, delete, and replace other configurations for a part of the configuration of each embodiment.
Each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit. Each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor. Information such as programs and tables for realizing each function can be stored in a memory, a hard disk, a recording device such as an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD. Note that the control lines and information lines are those that are considered necessary for the explanation, and not all control lines and information lines on the product are necessarily shown. Actually, it may be considered that almost all the components are connected to each other.

100 Terminal 101 Input Accepting Unit 102 Display Unit 103 Communication Unit 104 Control Unit (Terminal)
200 Server 201 Receiving Unit 202 Data Queue 203 Control Database 204 Control Unit (Server)
205 Load receiving unit 206 Transmitting unit 300 Medical device 301 Database monitoring unit 302 Database 303 Control unit (medical device).

Claims (7)

A terminal that makes a data acquisition request, a server that receives the acquisition request from the terminal and transmits the acquisition request to a medical device, and is connected to the server via a network, and receives the acquisition request from the server A medical device control system having the medical device to be provided,
The server
A server communication unit that receives the acquisition request from the terminal;
Apparatus load information that associates an apparatus load state value indicating a load ratio of the medical apparatus with an executable value indicating the number of acquisition requests that can be executed by the medical apparatus in the state of the apparatus load state value; and A storage unit that stores network load information that associates a network load state value that indicates a load ratio with a network executable value that indicates the number of acquisition requests that can be transmitted and received via the network in the network load state value; ,
A load receiving unit that receives the device load state value from the medical device and obtains the network load state value from the network;
A network obtained by comparing the device load state value received by the load receiving unit with the device load state value of the device load information to obtain an executable value corresponding to the device load state value, and the network obtained by the load receiving unit Requested when the network executable value is obtained by comparing the load status value with the network load status value of the network load information, and the acquired executable value and the network executable value satisfy a predetermined condition. A server control unit that determines that the process is possible, performs a determination process of transmitting the acquisition request to the medical device, and acquires the data;
The medical device comprises:
When receiving the acquisition request from the server, a device control unit that acquires the device load state value of itself,
A device communication unit for transmitting the device load state value to the server;
A medical device control system comprising: The server further includes a data queue that holds the acquisition request received by the server communication unit,
The server communication unit receives the acquisition request including a priority for acquiring the data from the terminal;
The server control unit sorts the acquisition requests in the descending order of the priority and holds them in the data queue, and performs the determination processing on the acquisition requests held in the data queue in the sorted order.
The medical device control system according to claim 1. The server control unit compares the priority included in the acquisition request held in the data queue with the priority included in the acquisition request newly received by the server communication unit, and the server communication unit If it is determined that the acquisition request received is higher in priority, the server communication unit inserts and reorders the newly received acquisition request before the acquisition request held in the data queue,
The medical device control system according to claim 2. The server control unit receives an input of a network load state value and a network executable value of the network load information to be stored in the storage unit from a display unit included in any of the terminal, the server, and the medical device, Memorize in memory
The medical device control system according to claim 1, wherein the medical device control system is a medical device control system. The server control unit receives an input of a device load state value and a device executable value of the device load information stored in the storage unit from a display unit included in any of the terminal, the server, and the medical device, Memorize in memory
The medical device control system according to any one of claims 1 to 4, wherein The load receiving unit receives, as the device load state value, a database usage rate, a CPU usage rate, and a memory usage rate that the medical device has, from the medical device,
The medical device control system according to claim 1, wherein the medical device control system is a medical device control system. A medical device control server that receives a data acquisition request from a terminal and transmits the acquisition request to a medical device that provides the data via a network,
A server communication unit that receives the acquisition request from a terminal that requests acquisition of data;
Apparatus load information that associates an apparatus load state value indicating a load ratio of the medical apparatus with an executable value indicating the number of acquisition requests that can be executed by the medical apparatus in the state of the apparatus load state value; and A storage unit that stores network load information that associates a network load state value that indicates a load ratio with a network executable value that indicates the number of acquisition requests that can be transmitted and received via the network in the network load state value; ,
A load receiving unit that receives the device load state value from the medical device and obtains the network load state value from the network;
A network obtained by comparing the device load state value received by the load receiving unit with the device load state value of the device load information to obtain an executable value corresponding to the device load state value, and the network obtained by the load receiving unit Requested when the network executable value is obtained by comparing the load status value with the network load status value of the network load information, and the acquired executable value and the network executable value satisfy a predetermined condition. A server control unit that determines that the process is possible, performs a determination process of transmitting the acquisition request to the medical device, and acquires the data;
A medical device control server comprising:

Images