Maintenance system, management device, and maintenance method

Abstract

Provided is a maintenance system wherein a management device manages a database, which stores solution information associated with the state of a medical device, and updates the database. The management device receives state information indicating the state of the medical device from the medical device, which is connected to a network of an organization, via a network outside of the organization. The management device determines solution information corresponding to the state of the medical device on the basis of the state information and the database and transmits the determined solution information to a terminal device having a display unit via the network outside of the organization.

Description

[Technical Field]

[0001] The present disclosure relates to a maintenance system, a management device, and a maintenance method for performing maintenance on a medical device. [Background technology]

[0002] Japanese Patent Laid-Open Publication No. 2003-126082 (Patent Document 1) discloses a medical diagnostic device that can identify the cause of an error or the unit that is the cause of the error. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2003-126082 Summary of the Invention [Problem to be solved by the invention]

[0004] According to the medical diagnostic device described in Patent Document 1, the location of a fault can be easily identified, improving diagnostic efficiency. As such, there is a demand for early resolution of errors and other problems in medical devices such as medical diagnostic devices.

[0005] When a problem occurs, users usually take out the manual and try to solve the problem. However, when using the manual, it takes time to search for the manual itself and to find the corresponding solution within the manual. Therefore, a method can be considered to shorten the time spent searching for a solution by presenting the solution to the problem that has occurred to the user.

[0006] However, if the solution information is stored in the medical device, updating the solution information requires a service technician to visit the location where the medical device is installed, which is time-consuming and requires a lot of work for the service technician. On the other hand, updating the solution information by externally accessing the network within the organization to which the medical device is connected is difficult due to the unique medical field in which the network within the organization to which the medical device is connected handles personal information of patients and others, making it difficult to access from outside. For these reasons, it has been difficult to provide appropriate solutions tailored to the status of the medical device when presenting solutions to users.

[0007] An object of the present disclosure is to provide an appropriate solution depending on the state of the medical device. [Means for solving the problem]

[0008] The maintenance system disclosed herein is a system for performing maintenance on a device. The maintenance system includes a medical device connected to an organization's network, a management device that receives information about the medical device via a network outside the organization and manages the status of the medical device, and a terminal device configured to be able to communicate with the management device via the network outside the organization and having a display. The management device updates a database that stores solution information associated with the status of the medical device. The management device receives status information indicating the status of the medical device from the medical device. The management device determines solution information corresponding to the status of the medical device based on the received status information and the database. The management device transmits the determined solution information to the terminal device. The terminal device displays the transmitted solution information on the display.

[0009] The management device disclosed herein manages the status of medical devices connected to an organization's network. The management device includes a processor, a memory storing a program to be executed by the processor, and a communication interface for communicating with other devices via a network outside the organization. The processor is configured to execute the program to update a database storing solution information associated with the status of the medical device, receive status information indicating the status of the medical device from the medical device via the network outside the organization, determine solution information corresponding to the status of the medical device based on the received status information and the database, and transmit the determined solution information to a terminal device having a display via the network outside the organization.

[0010] The maintenance method disclosed herein is a method for maintaining a medical device connected to an organization's network, and includes the steps of updating a database storing solution information associated with the status of the medical device, receiving status information indicating the status of the medical device from the medical device via a network outside the organization, determining solution information corresponding to the status of the medical device based on the received status information and the database, transmitting the determined solution information to a terminal device having a display via the network outside the organization, and displaying the transmitted solution information on the display by the terminal device. [Effects of the Invention]

[0011] According to the present disclosure, the database storing solution information can be accessed via a network outside the organization, making it possible to easily update the database, thereby providing appropriate solutions according to the condition of the medical device. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a schematic diagram for explaining the overall configuration of a maintenance system. [Figure 2] FIG. 2 illustrates an example of a hardware configuration of each device. [Figure 3] FIG. 2 is a diagram illustrating an example of a data structure of a solution database. [Figure 4] FIG. 10 is a diagram illustrating an example of state information. [Figure 5] FIG. 2 is a diagram for explaining the exchange of information between the devices. [Figure 6] 10 is a flowchart illustrating an example of a process performed when an error occurs. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are designated by the same reference numerals, and description thereof will not be repeated.

[0014] <Overall configuration of the maintenance system> 1 is a schematic diagram illustrating the overall configuration of a maintenance system. The maintenance system 1 includes a management server 100, a plurality of medical devices 200A and 200B, a plurality of terminal devices 300A and 300B, and a provider terminal device 400. In the following description, the medical devices 200A and 200B will be collectively referred to as "medical devices 200," and the terminal devices 300A and 300B will be collectively referred to as "terminal devices 300."

[0015] Communications between the management server 100 and each of the terminal devices 300A, 300B and the provider terminal device 400, as well as transmission of information from each of the medical devices 200A, 200B to the management server 100, are performed via an external network NW1. The external network NW1 is a network outside (outside) the organizations 20A, 20B (described later), such as the Internet or a public telephone network.

[0016] The management server 100 is managed by, for example, a maintenance company (Company C) such as a business that provides the medical device 200 or a business that specializes in maintaining the medical device 200. The management server 100 is a cloud server built on the cloud. By building the management server 100 on the cloud, the management server 100 can be accessed from each medical device 200 installed in various facilities.

[0017] The medical device 200 is used in organizations such as research facilities or hospitals. The medical device 200 may be any device or system including such device used in organizations such as training facilities or hospitals, including, for example, medical diagnostic devices such as X-ray devices, CT devices, near-infrared imaging devices, angiography devices, and PET (Positron Emission Tomography) devices, medical systems including such medical diagnostic devices, and analytical devices used for PCR (Polymerase Chain Reaction) tests, etc. The medical device 200 may also be a medical information system used for reception of consultations, guidance on consultations and accounting at hospitals, management of medical records, payment of medical fees, etc.

[0018] The medical devices 200A and 200B are used by organizations 20A and 20B, respectively, and are connected to separate organizational networks NW2A and NW2B. Each of the medical devices 200A and 200B is communicatively connected to a server 500A that stores personal information such as electronic medical records via the organizational network NW2A, and to a server 500B that stores personal information such as electronic medical records via the organizational network NW2B. Note that, hereinafter, the organizations 20A and 20B are collectively referred to as the "organization 20," the organizational networks NW2A and NW2B as the "organization network NW2," and the servers 500A and 500B as the "server 500."

[0019] The organization's network NW2 is an intranet used within the organization, and is connected to a server 500 that stores personal information. Therefore, access to the organization's network NW2 is restricted. The organization's network NW2 is constructed using, for example, Bluetooth (registered trademark), a wired LAN (Local Area Network), or a wireless LAN.

[0020] The terminal device 300 displays information related to the medical device 200. The terminal device 300A is assumed to be used within the organization 20A by an employee A working in the organization 20A. Similarly, the terminal device 300B is assumed to be used within the organization 20B by an employee B working in the organization 20B.

[0021] In this embodiment, it is assumed that the terminal device 300 is not connected to the organization's network NW2, although the terminal device 300 may be configured to be connectable to the organization's network NW2.

[0022] The contractor terminal device 400 is used, for example, by a maintenance contractor (Company C). For example, the maintenance contractor (Company C) uses the contractor terminal device 400 to manage the management server 100 and to remotely check the status of the medical device 200.

[0023] <Hardware configuration of each device> 2 is a diagram showing an example of the hardware configuration of each device. The hardware configuration of each device constituting the maintenance system 1 will be described with reference to FIG.

[0024] (Management Server) The management server 100 includes a processor 110, a communication interface 120, and a memory 130.

[0025] The processor 110 is a computing entity that executes various programs (for example, a control program 132 described below). The processor 110 includes, for example, at least one of a central processing unit (CPU), a field programmable gate array (FPGA), and a graphics processing unit (GPU). The processor 110 may be configured with processing circuitry.

[0026] The communication interface 120 transmits and receives data to and from other devices constituting the maintenance system 1 (for example, the medical device 200, the terminal device 300, the contractor terminal device 400, etc.) via the external network NW1.

[0027] The memory 130 includes volatile memory such as dynamic random access memory (DRAM) and static random access memory (SRAM), or non-volatile memory such as read only memory (ROM), solid state drive (SSD), and hard disk drive (HDD).

[0028] The memory 130 stores, for example, a control program 132, account information 134, and a solution database 140. The management server 100 executes various processes, which will be described later, by the processor 110 executing the control program 132. The account information 134 is information that links the medical device 200 with the terminal device 300 that displays information about the medical device 200. Specifically, the account information 134 is information that links the medical device 200A with the terminal device 300A, and the medical device 200B with the terminal device 300B.

[0029] The solution database 140 stores solution information 142 associated with the state of the medical device 200. The solution information 142 is information associated with the state of the medical device 200, and includes, for example, a manual showing the procedure for resolving an error, a tutorial video, and the like.

[0030] Fig. 3 is a diagram showing an example of the data structure of the solution database. As shown in Fig. 3, the solution database 140 stores solution information 142 for each state and each version of the medical device 200. Note that the version of the medical device 200 refers to at least one of the version of the control program 234 for driving the medical device 200 and the version of each hardware of one or more devices that make up the medical device 200.

[0031] In the example shown in Fig. 3, solution information 142 is stored for each version of the device's hardware and each version of the control program 234. Note that the data structure shown in Fig. 3 is an example. Note that if the solution information 142 is common even if the hardware versions are different, there is no need to store solution information 142 for each hardware version. Similarly, if the solution information 142 is common even if the software versions are different, there is no need to store solution information 142 for each software version.

[0032] In this way, by storing the solution information 142 for each version of the medical device 200, it is possible to provide the solution information 142 suitable for the version.

[0033] (Medical equipment) The medical device 200 includes a processor 210 , a communication interface 220 , and a memory 230 .

[0034] The processor 210 is a computing entity that executes various programs. The processor 210 includes, for example, at least one of a CPU, an FPGA, and a GPU. The processor 210 may be configured with an arithmetic circuit.

[0035] The communication interface 220 transmits information to the management server 100 via the external network NW1, and transmits and receives data to and from the server 500 within the organization 20 via the organization's network NW2.

[0036] The memory 230 includes volatile memory such as DRAM and SRAM, or non-volatile memory such as ROM, SSD, and HDD. The memory 230 stores, for example, status information 232 indicating the status of the medical device 200 and a control program 234 for driving the medical device 200.

[0037] 4 is a diagram showing an example of the status information 232. As shown in FIG. 4, the status information 232 includes an identification ID of the device, configuration information (for example, information about the devices that make up the medical device 200), operation information (for example, an operation log of the medical device 200), error information, version information, etc.

[0038] The control program 234 is a program provided by a maintenance company (Company C) that manages the management server 100. The maintenance company (Company C) provides an update program for updating the control program 234. The user of the medical device 200 acquires the update program himself or herself and updates the control program 234.

[0039] The version information may include information that can identify the version of software (e.g., control program 234) installed in medical device 200, or information that can identify the version of each hardware of one or more devices that make up medical device 200.

[0040] 2 shows an example in which the medical device 200 is composed of a single device, the medical device 200 may be composed of multiple devices connected to each other so that they can communicate with each other. In this case, each of the multiple devices includes at least a communication interface for transmitting and receiving data to and from the other devices, a processor, and a memory, and the memory stores status information 232 and a control program. Each of the multiple devices may be connected to the management server 100 so that they can communicate with each other. In this case, each of the multiple devices may be configured to be able to transmit status information 232 to the management server 100. Furthermore, one of the multiple devices constituting the medical device 200 may be the main device that manages communication with the management server 100.

[0041] (Terminal Device) The terminal device 300 includes a processor 310 , a communication interface 320 , a memory 330 , a display unit 340 , and an input unit 350 .

[0042] The processor 310 is a computing entity that executes various programs. The processor 310 includes, for example, at least one of a CPU, an FPGA, and a GPU. The processor 310 may be configured with an arithmetic circuit.

[0043] The communication interface 320 transmits and receives data to and from the management server 100 via the external network NW1.

[0044] The memory 330 includes volatile memory such as DRAM and SRAM, or non-volatile memory such as ROM, SSD, and HDD.

[0045] The display unit 340 is a display device that displays various information, and includes, for example, a liquid crystal display, etc. The input unit 350 accepts inputs including various instructions from the user, and includes, for example, a keyboard, a mouse, a touch panel, etc.

[0046] (vendor terminal device) The merchant terminal device 400 includes a processor 410 , a communication interface 420 , a memory 430 , a display unit 440 , and an input unit 450 .

[0047] The processor 410 is a computing entity that executes various programs. The processor 410 includes, for example, at least one of a CPU, an FPGA, and a GPU. The processor 410 may be configured with an arithmetic circuit.

[0048] The communication interface 420 transmits and receives data to and from the management server 100 via the external network NW1.

[0049] The memory 430 includes volatile memory such as DRAM and SRAM, or non-volatile memory such as ROM, SSD, and HDD.

[0050] The display unit 440 is a display device that displays various information, and includes, for example, a liquid crystal display, etc. The input unit 450 receives inputs including various instructions from the user, and includes, for example, a keyboard, a mouse, a touch panel, etc.

[0051] <Information exchange between devices> 5 is a diagram for explaining the exchange of information between the devices. The management server 100 accepts input of account information 134 from the terminal device 300. The account information 134 is information that links the terminal device 300 and the medical device 200. For example, the account information 134 includes an identification ID that identifies each of the medical devices 200A and 200B, and an identification ID that identifies each of the terminal devices 300A and 300B. Note that the identification ID does not have to be a special number and may be, for example, the customer's email address.

[0052] For example, a maintenance company (Company C) issues an ID and a password for each facility or medical device 200. A user of the medical device 200 uses the ID and password to access the management server 100. When the user of the medical device 200 inputs the identification ID of the terminal device 300 and the identification ID of the medical device 200, the management server 100 stores the input information in the memory 130 as account information 134.

[0053] The account information 134 may be input from the medical device 200 if the medical device 200 has an input unit, or from the provider terminal device 400 .

[0054] The medical device 200 transmits status information 232 to the management server 100. For example, the medical device 200 transmits the status information 232 to the management server 100 when an error occurs in the medical device 200. The medical device 200 may transmit the status information 232 in response to a request from the management server 100. The medical device 200 may also transmit the status information 232 to the management server 100 at a predetermined timing, such as at a predetermined interval or upon startup. One or more devices constituting the medical device 200 may each transmit the status information 232 to the management server 100.

[0055] The management server 100 determines solution information 142 according to the state of the medical device 200 based on the state information 232 and the solution database 140. For example, the management server 100 identifies an occurring error based on the error information included in the state information 232, and determines solution information 142 as information necessary to resolve the error.

[0056] The management server 100 determines the destination of the determined solution information 142 based on the account information 134 and the status information 232. More specifically, the management server 100 identifies the identification ID of the terminal device 300 corresponding to the identification ID of the medical device 200 included in the status information 232 based on the account information 134, and determines the destination terminal device 300.

[0057] The management server 100 transmits the solution information 142 to the determined destination. That is, the management server 100 transmits the solution information 142 determined based on the status information 232 sent from the medical device 200A to the terminal device 300A, and transmits the solution information 142 determined based on the status information 232 sent from the medical device 200B to the terminal device 300B. The terminal device 300 displays the transmitted solution information 142 on the display unit 340.

[0058] In addition to the solution information 142, the management server 100 may also transmit to the terminal device 300 the date and time of the error occurrence, the error code, a message displayed on the medical device 200, or operation information of the medical device 200. For example, by transmitting this information in addition to the solution information 142 in response to the occurrence of an error, the user can investigate the cause of the error.

[0059] The management server 100 updates the solution database 140. When new solution information 142 is transmitted from the agent terminal device 400, the management server 100 updates the solution database 140. Note that the timing for updating the solution database 140 is not limited to this. For example, the management server 100 may store the solution information 142 and update the solution database 140 at a predetermined interval.

[0060] As an example, the contractor terminal device 400 transmits solution information 142 to the management server 100. The maintenance contractor (Company C) accesses the management server 100 from the contractor terminal device 400 and updates the solution database 140. For example, when updating the control program 234 of the medical device 200, the contractor terminal device 400 transmits solution information 142 corresponding to the version of the updated control program 234 to the management server 100 together with version information indicating the version. The management server 100 stores the transmitted solution information 142 in the solution database 140 and updates the solution database 140.

[0061] In addition, when a new device with an updated hardware version is manufactured, the vendor terminal device 400 may be configured to transmit solution information 142 corresponding to the updated version to the management server 100 together with version information indicating the updated version.

[0062] In this way, in this embodiment, the solution information 142 is stored in the memory 130 on the cloud, and by updating the solution database 140, the response methods can be updated and improved at any time without changing the configuration of the medical device 200 (for example, the data, software, functions, etc. stored in each device that makes up the medical device 200).

[0063] Furthermore, the memory 130 on the cloud has a sufficient storage capacity compared to the memory 230 of the medical device 200. Therefore, compared to the conventional case where the solution information 142 is stored in the medical device 200, by storing the solution information 142 on the management server 100 on the cloud, it is possible to store large amounts of content such as audio and video as the solution information 142, thereby increasing the variety of the solution information 142. As a result, it is possible to provide information not only in document format but also in other formats such as video and audio, and to support users in a variety of ways.

[0064] The control program 234 may be stored for each version in the memory 130 of the management server 100. For example, the vendor terminal device 400 may transmit an updated control program 234 to the management server 100. The management server 100 may provide the control program 234 to the user of the medical device 200 by storing the transmitted control program 234 for each version in the memory 130.

[0065] Generally, in the medical field, the organization's network NW2 must ensure security because it handles personal information of patients. In this embodiment, the solution database 140, in which the solution information 142 is stored, can be accessed via the external network NW1, not the organization's network NW2. This allows the solution database 140 to be easily updated, and as a result, appropriate solutions can be provided according to the status of the medical device 200.

[0066] Furthermore, since the management server 100 can be accessed via the external network NW1, the maintenance company (Company C) can easily update the solution information 142 (solution database 140) and provide the latest version of the solution information 142 to the user of the medical device 200.

[0067] The management server 100 also receives input of account information 134 that links each of the medical devices 200A, 200B with the corresponding terminal devices 300A, 300B. The management server 100 determines a destination to which the solution information 142 is to be sent based on the account information 134. Therefore, the management server 100 can manage the correspondence between the medical devices 200 and the terminal devices 300.

[0068] In this embodiment, only status information 232 is transmitted from the medical device 200 to the management server 100. The status information 232 indicates the status of the medical device 200 and does not include personal information. Therefore, the medical device 200 can easily send the status information 232 to outside the organization 20 via the external network NW1.

[0069] In this embodiment, the terminal device 300 is not connected to the organization's network NW2. On the other hand, the medical device 200 is connected to the organization's network NW2. In this embodiment, the management server 100 transmits the solution information 142 to the terminal device 300, not to the medical device 200, so that the solution information 142 can be provided to the user using a transmission method with relatively loose access conditions.

[0070] <An example of what to do when an error occurs> 6 is a flowchart showing an example of processing performed when an error occurs. Assume that an error occurs in the medical device 200A. When an error occurs, the medical device 200A transmits status information 232 to the management server 100 (S1). Note that the determination of whether an error has occurred may be made by the management server 100. For example, the medical device 200 may transmit the status information 232 to the management server 100 at predetermined intervals, and the management server 100 may determine whether an error has occurred in the medical device 200 based on the received status information 232.

[0071] The management server 100 determines solution information 142 according to the state of the medical device 200A based on the state information 232 (S2).

[0072] The management server 100 determines a destination to which the solution information 142 is to be sent (S3). The management server 100 determines the destination terminal device 300 based on the account information 134. In the example shown in FIG. 6, the management server 100 determines to send the solution information 142 determined in S2 to the terminal device 300A. The management server 100 sends the solution information 142 to the terminal device 300A (S4). The terminal device 300A displays the sent solution information 142 on the display unit 340 (S5).

[0073] When the management server 100 transmits the solution information 142 for resolving the error, it requests the terminal device 300A to input whether or not the error has been resolved (S6). When the user inputs whether or not the error has been resolved via the input unit 350, the terminal device 300A notifies the management server 100 of the input result (S7).

[0074] If the error has not been resolved (NO in S8), the management server 100 requests (S9) the terminal device 300A to input whether or not it has taken action based on the solution information 142. When the user inputs via the input unit 350 whether or not it has taken action based on the solution information 142, the terminal device 300A notifies the management server 100 of the input result (S10).

[0075] If the management server 100 has taken action based on the solution information 142 (YES in S11), it notifies the agent terminal device 400 of information related to the error (S12). The agent terminal device 400 displays the sent information related to the error on the display unit 440 (S13).

[0076] The information about the error includes, for example, the identification ID of the medical device 200 in which the error has occurred, information indicating which of the devices constituting the medical device 200 has the error or which device has notified the error, information indicating the content of the error that has occurred (error code, alert level, etc.), the transmitted solution information 142, information indicating the response status by the user (information indicating that a response has been made based on the solution information 142, information indicating that the error has not been resolved, response record, etc.), etc. In addition to the information about the error, the management server 100 may also transmit the status information 232 sent from the medical device 200A.

[0077] If an error occurs in the medical device 200B, the same process is performed among the management server 100, the medical device 200B, the terminal device 300B, and the provider terminal device 400 (S14 to S26).

[0078] As described above, in this embodiment, the management server 100 transmits the solution information 142 determined based on the status information 232 received from the medical device 200A to the terminal device 300A, and transmits the solution information 142 determined based on the status information 232 received from the medical device 200B to the terminal device 300B.

[0079] This allows the user to be provided with solution information 142 tailored to the status of each medical device 200A, 200B, regardless of the device configuration of each medical device 200A, 200B. In organizations 20 (sites) such as research facilities or hospitals where the medical devices 200 are used, the medical devices 200 are individually designed for each organization 20. Therefore, depending on the organization 20, the medical devices 200 may not have a display unit such as a display. In this embodiment, the solution information 142 is transmitted to the terminal device 300 having the display unit 340. Therefore, even if the medical device 200 does not have a display unit such as a display, the solution information 142 can be presented to the user. Therefore, the user can take action tailored to the status of the medical device 200 by checking the solution information 142, without having to search for a manual for the medical device 200, and as a result, the downtime of the medical device 200 can be shortened.

[0080] Furthermore, in this embodiment, if an error is not resolved despite having taken action based on the solution information 142, information about the error is sent to the maintenance contractor terminal device 400. Therefore, the user of the medical device 200 can receive support from the maintenance contractor if an error is not resolved despite having taken action based on the solution information 142. Furthermore, the maintenance contractor (company C) can only handle necessary errors because information about the error is sent to the maintenance contractor terminal device 400 only when the maintenance contractor has taken action based on the solution information 142.

[0081] <Modification: Trigger for the Management Server to Send Information to the Terminal Device> In the above embodiment, information is transmitted from the management server 100 to the terminal device 300 in response to an error occurring in the medical device 200. However, the trigger for transmitting information from the management server 100 to the terminal device 300 is not limited to this.

[0082] For example, the terminal device 300 may request the management server 100 to transmit the status information 232. In this case, the management server 100 may request the medical device 200 to transmit the status information 232 in response to the request from the terminal device 300. Furthermore, when the medical device 200 transmits the status information 232 to the management server 100 at predetermined intervals, the management server 100 may transmit the latest status information 232 in response to the request from the terminal device 300.

[0083] In this way, the management server 100 transmits the status information 232 in response to a request from the terminal device 300, so that the user of the medical device 200 can check the status of the medical device 200 as needed.

[0084] In addition, the management server 100 may determine whether or not a part of the medical device 200 needs to be replaced based on the operation information, and if the part needs to be replaced, may request the terminal device 300 to replace the part, and may also send solution information 142 indicating how to replace the part.

[0085] According to this configuration, a part replacement instruction is automatically notified according to the operating status of the medical device 200, which makes it easier for the user to manage the medical device 200. Furthermore, by notifying the user of the part replacement before an error occurs in the medical device 200, the risk of interrupting use of the medical device 200 can be reduced.

[0086] <Variation: Method for determining destination of solution information> In the above embodiment, the destination of the solution information 142 is determined based on the account information 134. However, the method of determining the destination of the solution information 142 is not limited to using the account information 134.

[0087] For example, the medical device 200 may transmit to the management server 100, in addition to the status information 232, information that can identify the destination of the solution information 142. Furthermore, when a terminal device 300 requests the management server 100 to transmit the solution information 142, the terminal device 300 may specify the medical device 200. The management server 100 may transmit the solution information 142 determined based on the status information 232 transmitted from the specified medical device 200 to the requesting terminal device 300.

[0088] <Variation: Processing when an error occurs> In the above embodiment, when an error occurs, the management server 100 requests input as to whether the error has been resolved (S6, S19), and if the error has not been resolved, requests input as to whether an action has been taken based on the solution information 142 (S9, S22). Note that the method for determining whether the error has been resolved and whether an action has been taken based on the solution information 142 and the order in which these are checked are not limited.

[0089] For example, the management server 100 may determine at least one of whether the error has been resolved and whether an action has been taken based on the solution information 142, based on the status information 232 transmitted from the medical device 200. In this case, the medical device 200 may transmit the status information 232 at predetermined intervals. The medical device 200 may also transmit the status information 232 based on, for example, the receipt of an operation on the medical device 200 or the resolution of an error.

[0090] Furthermore, when the management server 100 determines that a response based on the solution information 142 has been taken, it may request the terminal device 300, to which the solution information 142 was sent, to input whether or not the error has been resolved.

[0091] In the above embodiment, the timing at which the management server 100 notifies the agent terminal device 400 of information related to an error is when the terminal device 300 has taken action based on the solution information 142. Note that the timing at which the management server 100 notifies the agent terminal device 400 of information related to an error may be when the management server 100 determines that an error has occurred in the terminal device 300, or may be when a predetermined period of time has elapsed since the error occurred, regardless of whether or not an action based on the solution information 142 has been taken.

[0092] [Aspect] It will be understood by those skilled in the art that the above-described embodiments are specific examples of the following aspects.

[0093] (Item 1) A maintenance system according to one aspect is a system for performing maintenance on a device. The maintenance system includes a medical device connected to an organization's network, a management device that receives information about the medical device via a network outside the organization and manages the status of the medical device, and a terminal device configured to be able to communicate with the management device via the network outside the organization and having a display. The management device updates a database in which solution information associated with the status of the medical device is stored. The management device receives status information indicating the status of the medical device from the medical device. The management device determines solution information corresponding to the status of the medical device based on the received status information and the database. The management device transmits the determined solution information to the terminal device. The terminal device displays the transmitted solution information on the display.

[0094] According to the maintenance system described in paragraph 1, the database in which solution information is stored can be accessed via a network outside the organization, making it easy to update the database and, as a result, providing appropriate solutions according to the condition of the medical device.

[0095] (Item 2) In the maintenance system described in item 1, the status information transmitted by the medical device includes version information of the medical device. The database stores solution information associated with the version of the medical device. The management device determines solution information according to the version of the corresponding medical device based on the received status information.

[0096] The maintenance system described in paragraph 2 can provide a solution suited to the version of the medical device.

[0097] (Item 3) The maintenance system described in items 1 or 2 further includes a contractor terminal device of a maintenance contractor different from the terminal device, configured to be able to communicate with the management device via a network outside the organization. The contractor terminal device transmits solution information to the management device. The management device updates the database based on the solution information received from the contractor terminal device.

[0098] According to the maintenance system described in paragraph 3, the maintenance company can provide the latest solution information to the user of the medical device.

[0099] (4) In the maintenance system described in any one of paragraphs 1 to 3, when the management device transmits solution information for an error that has occurred in a medical device to a terminal device, if the error is not resolved even though action has been taken based on the transmitted solution information, the management device sends information about the error to a contractor terminal device of a maintenance contractor different from the terminal device.

[0100] According to the maintenance system described in Section 4, if a medical device user takes action based on the solution information but the error remains unresolved, the user can receive support from the maintenance company. Furthermore, since information about the error is sent to the maintenance company terminal device only when action is taken based on the solution information, the maintenance company can handle only the necessary errors.

[0101] (Item 5) In the maintenance system described in any one of Items 1 to 4, the medical devices include a first medical device connected to a network of a first organization and a second medical device connected to a network of a second organization. The terminal devices include a first display terminal device and a second display terminal device. The management device transmits solution information determined based on status information received from the first device to the first display terminal device, and transmits solution information determined based on status information received from the second device to the second display terminal device.

[0102] According to the maintenance system described in paragraph 5, solution information is determined according to the status of each medical device, and the determined solution information is sent to the terminal device corresponding to the medical device. Therefore, solution information according to the status of each medical device can be provided to the user regardless of the device configuration of each medical device.

[0103] (Item 6) In the maintenance system described in any one of Items 5, the management device accepts input of account information linking each medical device with a corresponding display terminal device, and determines the destination of the determined solution information based on the input account information.

[0104] According to the maintenance system described in paragraph 6, the management device can manage the correspondence between the medical devices and the terminal devices.

[0105] (Item 7) In the maintenance system according to any one of items 1 to 6, the management device is constructed on a cloud.

[0106] According to the maintenance system described in paragraph 7, the management device is constructed on the cloud, so that the management device can be accessed from each medical device installed in various facilities.

[0107] (Item 8) A management device according to one embodiment manages the status of medical devices connected to an organization's network. The management device includes a processor, a memory storing a program to be executed by the processor, and a communication interface for communicating with other devices via a network outside the organization. The processor is configured to execute the program to update a database storing solution information associated with the status of the medical device, receive status information indicating the status of the medical device from the medical device via the network outside the organization, determine solution information corresponding to the status of the medical device based on the received status information and the database, and transmit the determined solution information to a terminal device having a display unit via the network outside the organization.

[0108] (Item 9) A maintenance method according to one aspect is a method for maintaining a medical device connected to an organization's network. The maintenance method includes the steps of updating a database in which solution information associated with the state of the medical device is stored, receiving status information indicating the state of the medical device from the medical device via a network outside the organization, determining solution information corresponding to the state of the medical device based on the received status information and the database, transmitting the determined solution information to a terminal device having a display unit via the network outside the organization, and displaying the transmitted solution information on the display unit of the terminal device.

[0109] According to the management device described in paragraph 8 and the method described in paragraph 9, the database in which solution information is stored can be accessed via a network outside the organization, making it possible to easily update the database, and as a result, appropriate solutions can be provided according to the status of the medical device.

[0110] The embodiments disclosed herein are intended to be combined as appropriate within the scope of any technical inconsistency. The embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The scope of the present invention is defined by the claims, not by the description of the above-mentioned embodiments, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0111] 1 Maintenance system, 20, 20A, 20B Organization, 100 Management server, 110, 210, 310, 410 Processor, 120, 220, 320, 420 Communication interface, 130, 230, 330, 430 Memory, 132, 234 Control program, 134 Account information, 140 Solution database, 142 Solution information, 200, 200A, 200B Medical device, 232 Status information, 300, 300A, 300B Terminal device, 340, 440 Display unit, 350, 450 Input unit, 400 Contractor terminal device, 500, 500A, 500B Server, NW1 External network, NW2, NW2A, NW2B Organization network.

Claims

1. A maintenance system for performing maintenance on an apparatus, comprising: a medical device connected to an organization's network; a management device that receives information about the medical device via a network outside the organization and manages the status of the medical device; a terminal device configured to be able to communicate with the management device via a network outside the organization and having a display unit; The management device storing a database in which solution information associated with the condition of the medical device is stored; updating the database; receiving status information from the medical device indicative of a status of the medical device; determining solution information according to the state of the medical device based on the received state information and the database, and transmitting the determined solution information to the terminal device; The terminal device displays the transmitted solution information on the display unit.

2. the status information transmitted by the medical device includes version information of the medical device; The database stores solution information in association with the version of the medical device, The maintenance system according to claim 1 , wherein the management device determines solution information according to the version of the corresponding medical device based on the received status information.

3. The system further includes a contractor terminal device of a maintenance contractor different from the terminal device, the contractor terminal device being configured to be able to communicate with the management device via a network outside the organization, the vendor terminal device transmits solution information to the management device; 2. The maintenance system according to claim 1, wherein said management device updates said database based on the solution information received from said contractor terminal device.

4. 2. The maintenance system of claim 1, wherein when the management device transmits solution information for an error that has occurred in the medical device to the terminal device, if the error is not resolved despite actions being taken based on the transmitted solution information, the management device sends information about the error to a maintenance company terminal device of a maintenance company different from the terminal device.

5. The medical devices include a first medical device connected to a network of a first organization and a second medical device connected to a network of a second organization; the terminal device includes a first display terminal device and a second display terminal device, The management device transmitting solution information determined based on the status information received from the first device to the first display terminal device; 2. The maintenance system according to claim 1, wherein solution information determined based on the status information received from said second device is transmitted to said second display terminal device.

6. The management device Accepts input of account information linking each medical device with a corresponding display terminal device; 6. The maintenance system according to claim 5, wherein a destination of the determined solution information is determined based on input account information.

7. The maintenance system according to claim 1 , wherein the management device is constructed on a cloud.

8. A management device that manages the status of medical devices connected to an organization's network, a processor; a memory storing a program to be executed by the processor; a communication interface for communicating with other devices via a network outside the organization; the memory stores a database in which solution information associated with the status of the medical device is stored; The processor executes the program, updating the database; receiving status information indicating a status of the medical device from the medical device via a network outside the organization; determining solution information according to the status of the medical device based on the received status information and the database; The management device is configured to transmit the determined solution information to a terminal device having a display unit via a network outside the organization.

9. A maintenance method executed by a management device that performs maintenance on a medical device connected to a network of an organization via a network outside the organization, the management device storing a database in which solution information associated with a state of the medical device is stored; updating the database; receiving status information indicating a status of the medical device from the medical device via a network outside the organization; determining solution information according to the status of the medical device based on the received status information and the database; transmitting the determined solution information to a terminal device having a display unit via a network outside the organization; and a step of displaying the transmitted solution information on the display unit by the terminal device.

Images