JP2005334292A - Medical equipment data changing system and medical equipment - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce time for changing the contents of a configuration storage part for a logic circuit of FPGA etc. <P>SOLUTION: This system is provided with: the logic circuit for realizing at least one of the functions of medical equipment; a configuration storing means for storing data for deciding the constitution of the logic circuit; a processing means for reading and writing the data between it and the configuration storage means; a transmission and reception means connected to the processing means for transmitting and receiving the data; and a terminal connected with the transmission and reception means through a communication line to transmit data for changing at least a part of the data read by the processing means to the transmission and reception means as data to be written by the processing means. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a medical device data changing system for changing data stored in a medical device via a communication line, and a medical device used in the system.

  X-ray diagnostic apparatuses, X-ray CT apparatuses, magnetic resonance image diagnostic apparatuses, ultrasonic diagnostic apparatuses, and the like are known as medical equipment for taking medical images. The functions of these are realized by software and hardware configurations, and an FPGA (Field Programmable Gate Array) is being used as at least a part thereof. The FPGA is used as a set with a configuration ROM (Read Only Memory), and constitutes a logic circuit or the like based on the contents stored in the configuration ROM.

  In recent years, hardware constituting logic circuits in medical devices tends to be integrated into large-scale application ICs such as FPGAs and ASICs (Application Specific Integrated Circuits). Since the ASIC raises the mask and fixes the circuit, it is impossible to change the logic circuit once created. On the other hand, the FPGA is programmable, that is, it is possible to change (update) the configuration of a logic circuit or the like that realizes a predetermined function by changing the contents of the configuration ROM.

  As described above, the FPGA is programmable, and it is possible to configure different logic circuits or the like according to the contents of the configuration ROM. However, the configured logic circuit or the like itself is composed of hardware. Therefore, when a problem occurs, it is not possible to perform remote correspondence by software (for example, see Patent Document 1) that is generally performed by remote maintenance.

  Conventionally, when a problem occurs in the operation of a medical device, a service person (hereinafter referred to as a local service) who handles maintenance of the medical device in the local area (a certain area where a medical facility where a medical device is provided) exists. An error classification is determined using an error check circuit incorporated in the circuit board. As a result of this determination, when it is determined that the FPGA can be corrected, the solution is achieved by supporting the configuration ROM. In addition, when there is a specification change request or other reason by a doctor, a radiographer, or the like (hereinafter referred to as a user) who uses a medical device, it may be possible to solve the problem by responding to the configuration ROM. In these cases, the local service staff informs the factory that is the shipping source of the medical device and the organization that is in charge of the maintenance after the shipment of the determination / survey result about the above problem and the information on the change request of the user. In response, the factory or the like creates a new configuration ROM based on the information and sends it to the local service staff. The local service representative will replace the old and new configuration ROM. The local service representative may not only notify the factory with the above information but also send the target configuration ROM to the factory or the like. In this case, the factory or the like analyzes the contents of the sent configuration ROM with reference to the notified information, and changes the data to the contents deemed appropriate. The configuration ROM whose data has been changed is sent back to the local service staff.

  In either case, the local service person replaces the sent configuration ROM or reattaches it to the medical device to check the operation. It is good if the medical device operates as expected, but if the desired operation is not achieved, the above exchange is repeated with the factory or the like again.

  Actually, the error check circuit may be hardware, and even if the error classification can be determined, a detailed status cannot be obtained. Therefore, even if information is obtained from a local service person in a factory or the like, there is no guarantee that all necessary information can be obtained reliably, and the possibility of the above repetition cannot be denied. In addition, during the delivery period, neither the local service staff nor the staff at the factory can perform specific work using the configuration ROM, and the effect of the shipping time on the work efficiency due to the mailing of the configuration ROM itself, etc. Is big.

As a result, it takes a long time until the desired operation is obtained in the medical device, and in some cases, the use of the medical device must be stopped. Furthermore, problems such as a decrease in reliability from a medical facility having the medical device and an increase in cost for analyzing and solving the problem may occur.
JP 2002-236758 A (for example, paragraph [0023] and FIG. 1)

  The present invention has been made in view of the above problems, and provides a medical device data change system and a medical device that can shorten the time required to change the contents of a configuration storage unit for a logic circuit such as an FPGA. Objective.

  In order to achieve the above object, a medical device data changing system according to the first aspect of the present invention includes a logic circuit for realizing at least one function of a medical device and data for determining the configuration of the logic circuit. Configuration storage means for storing, processing means for reading and writing the data between the configuration storage means, transmission / reception means connected to the processing means for transmitting / receiving the data, and the transmission / reception means, A terminal that is connected via a communication line and transmits data that changes at least a part of the data read by the processing unit to the transmission / reception unit as data to be written by the processing unit. And

  In order to achieve the above object, a medical device according to the present invention described in claim 8 includes a logic circuit for realizing at least one function of the device and a configuration for storing data for determining the configuration of the logic circuit. And a processing unit for reading and writing the data between the storage unit and the configuration storage unit, and connected to the processing unit and transmitting the data read by the processing unit to an external terminal And transmitting / receiving means for receiving data for changing at least a part of the transmitted data from the external terminal as data to be written by the processing means.

  ADVANTAGE OF THE INVENTION According to this invention, it becomes possible to shorten the time required for the change of the content of the configuration memory | storage part for logic circuits, such as FPGA used for medical equipment.

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 is a diagram showing an example of an environment of a medical device data change system according to an embodiment of the present invention.

  A plurality of hospitals, for example, hospitals A, B, and C are connected to the service center 11 via the public network 10. Specifically, in hospital A, for example, medical equipment (X-ray diagnosis apparatus, X-ray CT apparatus, magnetic resonance image diagnosis apparatus, nuclear medicine image diagnosis apparatus, ultrasonic diagnosis apparatus, endoscope apparatus, and other medical facilities) One of the devices used for (medical) purposes. Hereinafter, the same applies to “medical equipment”.) 12 is provided and is connected to the public network 10 via the communication line 101. The hospital B is provided with, for example, a medical device a and a medical device b, and is connected to the public network 10 via a communication line 102. Further, for example, a medical device 13 is provided in the hospital C, and is connected to the public network 10 via a communication line 103. Each hospital may be in a nearby location or may be in a location remote from each other.

  Each medical device is realized by software or hardware configuration, and a logic circuit is being used as at least a part thereof. The logic circuit here refers to a programmable logic circuit, such as a programmable logic device (PLD), a field programmable gate array (FPGA), or a complex programmable logic. A device (Complex Programmable Logic Device: CPLD) is configured. In the following description, the case of FPGA will be described as an example.

  The service center 11 is provided with a personal computer (hereinafter referred to as a PC) 110, for example, and is connected to the public network 10 via a communication line 104. The service center 11 is, for example, a manufacturing (sales) company where development / design engineers (hereinafter referred to as engineers) of the medical devices 12, 13, a, and b are enrolled, and devices (development) in the same company. , Design, sales, or service), a department in charge or an organization outside the same company that can directly or indirectly support maintenance of the equipment.

  The service center 11 is not necessarily located in an area close to the hospitals A, B, and / or C. Therefore, the local service staff is responsible for dealing with the medical equipment of each hospital on a daily basis and for interacting with hospital personnel. In the case of FIG. 1, the local service staff 14 to which the local service staff belongs is at least in the area where the hospital B exists, and if a problem occurs in the medical equipment a and / or b provided in the hospital B, the hospital B informs the staff. If there is a response, solve the problem yourself. If the problem cannot be solved by itself or if a request is received from a doctor of the hospital, the service center 11 is notified to that effect.

  The public network 10 may be wired or wireless, including a general telephone line. It may be an optical communication network. A communication network using a dedicated line may be constructed instead of the public network. Further, the communication lines 101, 102, 103, and 104 may be, for example, LANs (Local Area Networks) in each hospital or service center 11 (or may be connected to the LAN).

Hereinafter, embodiments of the present invention under such environmental conditions will be specifically described.
(Example 1)
FIG. 2 is a diagram illustrating a configuration example of the medical device a according to the first embodiment of the present invention.

  The medical device a connected to the communication line 102 includes a transmission / reception circuit 20, an FPGA 21, and a configuration ROM 22. In addition to these, it goes without saying that various units required for collecting medical images and the like are included. The transmission / reception circuit 20 transmits data to the PC 110 in the service center 11 via the communication line 102, the public network 10, and the communication line 104. The data transmitted from the PC 110 is received by the transmission / reception circuit 20 via the communication line 104, the public network 10, and the communication line 102. The transmission / reception circuit 20 may be shared with transmission / reception of other information in the medical device a, or may be used exclusively for the FPGA 21.

  The FPGA 21 includes a CPU (Central Processing Unit) 210. In addition to the CPU 210, the FPGA 21 is configured by a hardware such as a logic circuit that realizes at least one function of the medical device a. As such a function, for example, an image filter that requires real-time property, a decoder that separates a software address space, a lookup table, and the like can be considered.

  When the doctor needs to determine the detection data immediately, it is necessary to display a moving image in real time. For example, an X-ray circulator is required to have real-time properties for guidance when inserting a catheter into a blood vessel and direct treatment to an affected area. In the case of an ultrasonic diagnostic apparatus, it is required for Doppler measurement or searching for an optimal organ image. In these displays, since the original image may be quite coarse, a filtering process is required, and in order not to delay the moving image (to avoid frame delay), it is necessary to process with hardware. There is a case where the filter function is finely adjusted depending on the hospital, and it is necessary to realize it with an FPGA or the like (FPGA / CPLD) having hardware and a programmable function.

  Hardware for realizing such a function is configured based on data stored in the configuration ROM 22. Specifically, the configuration ROM 22 stores a net list (design information) for specifying the internal configuration of the FPGA 21. On the FPGA 21, specific logic is configured based on this netlist. The configuration of the FPGA 21 can be changed by rewriting the net list in the configuration ROM 22. As the configuration ROM 22, for example, a fresh memory ROM or an EEPROM (Electrically Erasable Programmable ROM) can be used.

  Further, the FPGA 21 is composed of, for example, an SRAM (Static Random Access Memory), and the logic circuit or the like configured on the FPGA 21 disappears when power supply to the FPGA 21 is cut off. When power is supplied again, a logic circuit or the like is configured based on the data in the configuration ROM 22. Therefore, by changing the data in the configuration ROM 22, it is possible to update, change, modify, etc. (hereinafter simply referred to as “change”) (repeated change) the logic circuit or the like configured on the FPGA 21. ing.

  As described above, the configuration ROM 22 stores data for determining a logic circuit and the like configured on the FPGA 21. The configuration ROM 22 may be composed of other applicable configuration storage devices.

  The above-described CPU 210 configured based on the data stored in the configuration ROM 22 has a function of reading the data stored in the configuration ROM 22 and supplying the read data to the transmission / reception circuit 20. Also, it has a function of receiving data from the transmission / reception circuit 20 and writing the data as changed data in the configuration ROM 22. Therefore, the transmission / reception circuit 20 can transmit the data in the configuration ROM 22 read by the CPU 210 to the PC 110 in the service center 11 via the communication line 102, the public network 10, and the communication line 104. Further, when new data for changing the data in the configuration ROM 22 transmitted from the PC 110 is received by the transmission / reception circuit 20 via the communication line 104, the public network 10, and the communication line 102, the CPU 210 causes the data in the configuration ROM 22 to be changed. Can be written to.

  As described above, according to the first embodiment, mail for the data change in the configuration ROM 22 in the service center 11 is not necessary, so the entire time for the data change work is equivalent to the time required for the sending. Can only be shortened. In addition, the person in charge of the hospital B, the local service staff 14 and the service center 11 can be freed from mental stress that the configuration ROM 22 being sent cannot be directly operated during the sending period. Further, since it is not necessary for the local service person in charge of the local service person 14 to replace or re-install the configuration ROM 22 as in the prior art, the load on the local service person is also reduced.

  When the data in the configuration ROM 22 is changed, an engineer or the like in the service center 11 can directly acquire the data in the configuration ROM 22 via the PC 110 and analyze it at the logic level. Therefore, even when a problem occurs in the medical device a, it is possible to make a determination based on the acquired data, that is, accurate information indicating the current state, as to whether or not it is a hardware defect in the FPGA 21. Further, even when it is determined that the defect is a hardware defect, the correction work can be performed based on the acquired data, so that more preferable change data can be created (prepared) compared to the conventional case. As a result, in the confirmation of the post-update operation of the medical device a performed by the local service person after the change data is transmitted, the possibility that the change needs to be made again may be reduced. Further, even if the data in the configuration ROM 22 needs to be changed again because the medical device a does not perform a desired operation, it is possible to react immediately through communication. Therefore, time is not wasted due to re-mailing or the like.

  As described above, according to the first embodiment of the present invention, as the frequency of data change until the medical device a performs a desired operation is generated, the time can be significantly reduced as compared with the conventional case. Since the analysis work prior to the data change can be performed more accurately, the change frequency can actually be reduced as compared with the conventional case.

Since the CPU 210 is hardware configured on the FPGA 21 based on the data stored in the configuration ROM 22, the first embodiment of the present invention can be realized without the need for a physically new CPU.
(Example 2)
FIG. 3 is a diagram illustrating a configuration example of the medical device a ′ according to the second embodiment of the present invention.

  The second embodiment is different from the first embodiment in that the CPU 30 is provided independently of the FPGA 31. Since other configurations are the same as those in the first embodiment, the same reference numerals as those in FIG. Further, the basic functions and roles of the CPU 30 and the FPGA 31 are not substantially different from those of the CPU 210 and the FPGA 21 of the first embodiment, and thus detailed description thereof is omitted.

  The CPU 30 is connected to the transmission / reception circuit 20 and the configuration ROM 22 via the FPGA 31. The CPU 30 is basically dedicated to the FPGA 31, but may include processing for other circuits in the medical device a ′. Unlike the case of the first embodiment, the CPU 30 is not a hardware configuration realized in the FPGA 31, and therefore does not disappear due to the interruption of the power supply to the FPGA 31.

  The CPU 30 has a function of reading data stored in the configuration ROM 22 via the FPGA 31 and providing the read data to the transmission / reception circuit 20 via the FPGA 31. In addition, it has a function of receiving data received by the transmission / reception circuit 20 via the FPGA 31 and writing the data as change data in the configuration ROM 22 via the FPGA 31. Actually, in order to realize the above function, data for configuring a circuit for realizing data transfer between the CPU 30 and the configuration ROM 22 and between the CPU 30 and the transmission / reception circuit 20 in the FPGA 31 is stored in the configuration ROM 22. A circuit that is stored and based on the data needs to be configured on the FPGA 31 in accordance with power supply.

In the second embodiment of the present invention as described above, substantially the same effect as the first embodiment can be obtained with respect to the data change.
(Example 3)
FIG. 4 is a diagram illustrating a configuration example of the medical device b according to the third embodiment of the present invention.

  The third embodiment differs from the first embodiment in that the medical device b has two sets (pairs) of FPGA and configuration ROM. Note that the same applies when the number of FPGA and configuration ROM sets is three or more.

  The medical device b connected to the communication line 102 includes a transmission / reception circuit 40, an in-device data line 41, a functional circuit 42, and a functional circuit 43. In addition to these, it is the same as in the first embodiment that various units necessary for collecting medical images and the like are included. The functional circuit 42 includes an FPGA 420 and a configuration ROM 421. Similarly, the functional circuit 43 includes an FPGA 430 and a configuration ROM 431. Further, the FPGA 420 includes a CPU 4200, and the FPGA 430 includes a CPU 4300. The CPUs 4200 and 4300 are connected to the transmission / reception circuit 40 via the in-device data line 41, respectively. The transmission / reception circuit 40 transmits data to the PC 110 in the service center 11 via the communication line 102, the public network 10, and the communication line 104. The data transmitted from the PC 110 is received by the transmission / reception circuit 40 via the communication line 104, the public network 10, and the communication line 102. The transmission / reception circuit 40 may be shared with transmission / reception of other information in the medical device b, or may be used exclusively for the FPGAs 420 and 430.

  The FPGAs 420 and 430 may each realize a plurality of functions as in the case of the first embodiment. However, when one medical device includes a plurality of FPGAs as in this embodiment, for example, one or more specific functions of the medical device b are realized by combining the functions realized by the FPGAs 420 and 430, for example. It may be.

  The configurations and main functions of the FPGAs 420 and 430, the configuration ROMs 421 and 431, and the CPUs 4200 and 4300 are basically the same as those of the FPGA 21, the configuration ROM 22, and the CPU 210 in FIG. However, the configuration ROMs 421 and 431 each have information for identifying themselves as identification information data. The identifying information is not about the configuration ROM itself, but information for identifying the FPGAs 420 and 430, information for identifying the functional circuits 42 and 43, information for identifying the functions realized by the functional circuits 42 and 43, etc. Any configuration ROM may be used as long as it can identify which configuration ROM is targeted. The identification information data stored in the configuration ROM 421 is read from the CPU 4200, and the CPU 4200 determines whether or not the access from the PC 110 is addressed to the configuration ROM 421. Similarly, the identification information data stored in the configuration ROM 431 is read from the CPU 4300 and the CPU 4300 determines whether access from the PC 110 is addressed to the configuration ROM 431.

  Further, the CPU 4200 has a function of reading all or a part of the data constituting the FPGA 420 stored in the configuration ROM 421 and supplying the data to the transmission / reception circuit 40 via the in-device data line 41. Similarly, the CPU 4300 has a function of reading all or part of the data constituting the FPGA 430 stored in the configuration ROM 431 and supplying the data to the transmission / reception circuit 40 via the in-device data line 41. Therefore, data in the configuration ROM 421 or 431 can be transmitted to the PC 110 in the service center 11 via the communication line 102, the public network 10, and the communication line 104.

  Further, the CPU 4200 receives the data transmitted from the PC 110 from the transmission / reception circuit 40, determines the identification information included in the data based on the above-described identification information data, and if it is determined that the data is addressed to the configuration ROM 421, the data is configured. A function to write the data as change data in the operation ROM 421 is also provided. Similarly, the CPU 4300 receives the data transmitted from the PC 110 from the transmission / reception circuit 40, determines the identification information included in the data based on the above-described identification information data, and determines that the data is addressed to the configuration ROM 431. It also has a function of writing change data to the configuration ROM 431. Therefore, new data that changes the data in the configuration ROM 421 or 431 transmitted from the PC 110 can be written into the configuration ROM 421 or 431 via the communication line 104, the public network 10, and the communication line 102.

  As described above, even when one medical device has a plurality of sets of FPGAs and configuration ROMs, the same effects as in the first embodiment can be obtained by making these identifiable.

In the present embodiment, the CPU may be provided independently of the FPGA as in the second embodiment.
(Change work flow)
One embodiment of the flow of change work in the medical device data change system of the present invention including the cases of the first to third embodiments will be described below with reference to FIGS. The case of Example 1 (FIG. 2) will be described below as an example.

  FIG. 5 is a flowchart showing an example of the flow of data changing work in the configuration ROM using the medical device data changing system of the present invention.

  When power is supplied to the medical device a provided in the hospital B, power is also supplied to the FPGA 21 and the like, and a hardware circuit that realizes a predetermined function based on data stored in the configuration ROM 22 in the FPGA 21; A CPU 210 is configured. The medical device a is to be used for a subject such as a patient, but the medical device a is abnormal or undesired with respect to the operation or state of the medical device a or as a result of the use. When recognized by the function of the device a itself or by the user (step 500), the fact is notified to the local service staff 14 by online, e-mail, telephone or the like (step 501). In the case of an emergency, the notification may be made directly to the service center 11 under other predetermined conditions.

  Even if the above-mentioned abnormality does not occur, the user may desire to change the operating conditions and other specifications of the medical device a (step 502). Even in such a case, there may be a case where an e-mail, a telephone call, or a local service representative is directly informed. Also in this case, it may be transmitted directly from the hospital B to the service center 11.

  Upon receiving such notification or the like, the local service staff 14 investigates and confirms the operation and state of the medical device a particularly when an abnormality or the like occurs (step 510). When certain information is obtained by investigation or confirmation, the service person in charge 14 informs the service center 11 of the obtained information together with the notification contents from the hospital B described above.

  The engineer of the service center 11 grasps the general condition of the medical device a based on the notification from the local service staff 14 or the direct notification from the hospital B (step 520). In order to obtain more detailed and accurate information after grasping the general situation, engineers and the like operate the PC 110 to operate the medical device a provided in the hospital B via the communication line 104, the public network 10, and the communication line 102. Are established (steps 521 and 503), and the CPU 210 of the medical device a is accessed. This access will be described later with reference to FIG.

  When the CPU 210 receives an access from the PC 110 via the transmission / reception circuit 20, the CPU 210 acquires all or a part of predetermined data (ROM information) stored in the configuration ROM 22 according to the access, and transmits / receives the acquired data. This is applied to the circuit 20. The CPU 210 may give the data in the configuration ROM 22 acquired in advance to the transmission / reception circuit 20 in response to the access. Further, the CPU 210 may acquire the data in the configuration ROM 22 and give it to the transmission / reception circuit 20 every predetermined period (regularly) regardless of the access from the PC 110.

  In either case, when data is given from the CPU 20 to the transmission / reception circuit 20, this data is transmitted to the PC 110 of the service center 11 (step 504). The transmitted data is received by the PC 110 via the communication line 102, the public circuit 10, and the communication line 104, and a technician of the service center 11 acquires the received data via the PC 110 (step 522).

  The engineer confirms and analyzes the logic level of the acquired data (step 523). In particular, in the case of notification based on the occurrence of an abnormality in step 501, whether or not the abnormality is based on a hardware defect of the FPGA 21 is analyzed. If it is determined that the abnormality is based on a hardware defect, the defect is corrected. Therefore, change data (change information) for changing the data in the configuration ROM is created. If the user request is in step 502, change data (change information) for changing the data in the configuration ROM to create a specification that satisfies the request is generated (step 524). .

  The created change data is transmitted from the PC 110 to the medical device a (step 525). The transmitted change data is received by the transmission / reception circuit 20 of the medical device a provided in the hospital B via the communication line 104, the public network 10, and the communication line 102 (step 505).

  The change data received by the transmission / reception circuit 20 is given to the CPU 210 configured in the FPGA 21. The CPU 210 writes the change data in the configuration ROM 22 to update the data by adding to the existing data in the configuration ROM 22 or changing (rewriting) the existing data (step 506). Thus, the data change in the configuration ROM 22 is completed. The line established between the PC 110 of the service center 11 and the medical device a is temporarily disconnected here (steps 526 and 507).

  When the data update is completed, the service center 11 notifies the local service staff 14 (step 527). Upon receiving this notification, the local service staff 14 actually goes to the hospital B to check the operation of the medical device a (step 512). Actually, it is not efficient for the local service person to go to the hospital in response to the communication in step 527, so that it is not efficient between the engineer of the service center 11 and the local service person in advance. In consideration of the circumstances of hospital B, the date and time for the above data change work should be determined after consultation, and the local service representative will contact you at step 527 where the medical device a of hospital B is located. You may make it wait.

  The local service person turns on the power of the medical device a so that the FPGA 21 updates the hardware configuration based on the updated data in the configuration ROM 22. As the configuration of the FPGA 21 is updated, the functions and specifications of the medical device a based on the configuration are updated (step 508). The person in charge of the local service confirms whether or not the operation of the medical device a after the update is desired (step 509).

  If the medical device a does not perform a desired operation, the local service person notifies the service center 11 together with the specific operation status (step 513). In the service center 11, the engineer or the like repeats the above steps 521 to 527 so as to perform the change work again (step 528). Hereinafter, the above operation is repeated until the medical device a performs a desired operation.

  When the local service person confirms that the medical device a performs a desired operation, the service center 11 is notified of this (step 514), and the data change operation at the service center 11 is completed (step 529). ).

As described above, since the data in the configuration ROM 22 is analyzed and changed through the line, the accuracy of the change work is improved as compared with the conventional case, and the desired operation of the medical device a is finally obtained. It is possible to shorten the time required for the process. In addition, the burden on local service personnel can be reduced.
(Access to FPGA from service center)
FIG. 1 shows an access from a PC 110 of a service center 11 to a predetermined FPGA of a predetermined medical device provided in a predetermined hospital, particularly an access when one medical device has a plurality of FPGAs as in the third embodiment. This will be described below with reference to FIGS.

  FIG. 6 is a flowchart showing an example of a flow until the service center 11 accesses a predetermined FPGA in the medical device data change system of the present invention.

  The transmission / reception circuit 40 of the medical device b is in a standby state for access from the PC 110 of the service center 11 (step 60). The PC 110 issues a connection request to the medical device 12 provided in the hospital A and the medical device 13 provided in the hospital C as necessary, and changes the data stored in the configuration ROM for these devices. In some cases. Now, when the PC 110 makes a connection request to the hospital B via the communication line 104, the public network 10, and the communication line 102, access via the LAN in the hospital B or the like is addressed to the own machine based on this connection request. That is, it is determined whether or not it is addressed to the medical device b instead of the medical device a (step 61). For example, the determination may be performed by the transmission / reception circuit 40 or may be performed by the control circuit in the medical device b (not shown). If it is not addressed to the medical device b, the process returns to the standby state in step 60.

  When it is determined that it is addressed to the medical device b, the CPU 4200 and 4300 are respectively determined as to which of the configuration ROMs 421 and 431 the configuration ROM that is the access destination from the PC 110, that is, the data acquisition target here. An inquiry is made (step 62). The access from the PC 110 includes identification information corresponding to the above-described identification information data, and this identification information is included in the inquiry at step 62. This inquiry may be performed directly from the transmission / reception circuit 40, for example, or may be performed by a control circuit in the medical device b (not shown).

  In response to the inquiry, the CPU 4200 compares the identification information included in the inquiry with the identification information data read from the configuration ROM 421. Similarly, the CPU 4300 compares the identification information included in the inquiry with the identification information data read from the configuration ROM 431 (step 63). For example, when access from the PC 110 is directed to the configuration ROM 421, the CPU 4300 determines that the identification information does not match the identification information data because the identification information does not match the identification information data, and discards the information related to the inquiry (step 64).

  On the other hand, the CPU 4200 determines that the identification information and identification information data match and is addressed to its own configuration ROM, and the predetermined data (ROM information) among the data stored in the configuration ROM 421 in response to access from the PC 110. Reading is performed (step 65). The read data is given to the transmission / reception circuit 40 via the in-device data line 41. The transmission / reception circuit 40 transmits this data via the communication line 102 (step 66). The transmitted data is received and displayed on the PC 110 via the public network 10 and the communication line 104.

  As described above, the case of FIG. 4 has been described as an example. However, even in the case of the examples of FIGS. 2 and 3, the steps 62 to 64 of FIG. 6 can be omitted and applied.

  As described above, even when one medical device has a plurality of sets of FPGA and configuration ROM, the service center can acquire data in a desired configuration ROM, and similarly, a desired configuration can be obtained. Data in the ROM can be changed.

  In the above description of the embodiment of the present invention, the case where the terminal for changing the data stored in the configuration ROM is the PC 110 provided in the service center 11 as shown in FIG. Such a terminal may be used outside the service center as long as certain conditions such as restrictions are satisfied. For example, it may be in a hospital provided with a medical device having a configuration ROM where the technician or the like, the local service staff 14, or the target configuration ROM in some cases.

  The embodiment of the present invention described above is merely an example described for facilitating the understanding of the present invention, and is not a description for limiting the present invention. Accordingly, each of the constituent elements and other elements disclosed in the above-described embodiment of the present invention can be changed in design or modified to equivalents thereof without departing from the gist of the present invention. Furthermore, any possible combination of the same components and other elements is included in the scope of the present invention as long as the same effects as those obtained in the embodiment of the present invention described above can be obtained.

The figure which shows the example of 1 environment of the medical device data change system which concerns on the Example of this invention. 1 is a diagram illustrating a configuration example of a medical device according to a first embodiment of the present invention. The figure which shows the example of 1 structure of the medical device which concerns on Example 2 of this invention. The figure which shows the example of 1 structure of the medical device which concerns on Example 3 of this invention. The flowchart which shows the example of the flow of the data change operation | work in the configuration ROM using the medical device data change system of this invention. The flowchart which shows the example of the flow until it accesses a predetermined FPGA from a service center in the medical device data change system of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 ... Public network 11 ... Service center 12, 13, a, a ', b ... Medical device 20, 40 ... Transmission / reception circuit 21, 31, 420, 430 ... FPGA
22, 421, 431 ... Configuration ROM
30, 210, 4200, 4300 ... CPU
42, 43 ... functional circuit 110 ... PC
101, 102, 103, 104 ... communication line

Claims (8)

A logic circuit for realizing at least one function of the medical device;
Configuration storage means for storing data for determining the configuration of the logic circuit;
Processing means for reading and writing the data to and from the configuration storage means;
A transmitting / receiving means connected to the processing means for transmitting / receiving the data;
A terminal connected to the transmission / reception means via a communication line and transmitting data that changes at least a part of the data read by the processing means to the transmission / reception means as data written by the processing means; A medical device data change system characterized by: When there are a plurality of pairs of the logic circuit and the configuration storage means, each configuration storage means has identification information for identifying the paired logic circuits, and this identification information can be read by the processing means. The medical device data change system according to claim 1. The medical device data change system according to claim 1, wherein the processing means is provided in the logic circuit. The medical device data change system according to claim 1, wherein the processing unit is provided independently of the logic circuit. The medical device data change system according to claim 1, wherein the configuration storage means is a configuration ROM. The medical device data change system according to claim 1, wherein the configuration determined by the data realizes a function that requires real-time performance. 7. The medical device data changing system according to claim 6, wherein the function requiring real-time property is an image filter. A logic circuit for realizing at least one function of the device;
Configuration storage means for storing data for determining the configuration of the logic circuit;
Processing means for reading and writing the data to and from the configuration storage means;
Data connected to the processing means and read by the processing means is transmitted to an external terminal, and data for changing at least a part of the transmitted data is written as data to be written by the processing means. A medical device comprising: transmission / reception means for receiving from an external terminal.

Images