Remote monitoring system and control method for remote monitoring system

Abstract

To make it possible to remotely monitor medical instruments from inside and outside a hospital in a situation where security is ensured.SOLUTION: A remote monitoring system 100, which stores device information D2 indicative of a condition of a medical device 56, and provides a user terminal 55 a user uses with the device information, comprises: a storage unit 50B that stores the device information associated with device identification information identifying the medical device and facility identification information identifying a facility managing the medical device; an acquisition unit 11 that acquires facility identification information identifying a facility the user belongs to from the user terminal, and user determination information determining the user; and a registration unit 12 that transmits a request for approving the user determination information to a facility terminal of the facility, and registers individual identification information identifying the user in association with the facility identification information on the facility the user belongs to, providing that an approval response of the user determination information is received from the facility terminal.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a remote monitoring system that provides device information indicating the status of a medical device to a user terminal, and a control method thereof. [Background technology]

[0002] In recent years, there have been concerns about labor shortages due to aging and population decline, and it is becoming necessary to address this labor shortage in the medical field as well. Furthermore, the outbreak of COVID-19 has created a need for a new medical care system aimed at reducing the risk of infection and the burden on medical professionals. To address these issues, research is underway into large-scale remote monitoring systems, which are expensive to implement.

[0003] For example, there is a system that uses any mobile device to remotely monitor and manage patients on ECMO (Extracorporeal Membrane Oxygenation).In addition, there is a project underway that connects medical information from intensive care units in multiple hospitals via network communication, allowing intensive care specialists to monitor patients from a support center. Summary of the Invention [Problem to be solved by the invention]

[0004] However, what medical professionals want is a remote monitoring system that is easy to use, has low installation costs, and ensures security, but such a remote monitoring system does not exist. [Means for solving the problem]

[0005] A remote monitoring system according to one aspect of the present invention is a remote monitoring system that stores device information indicating the status of a medical device and provides the device information to a user terminal used by a user, and includes: a memory unit that stores the device information in association with device identification information that identifies the medical device and facility identification information that identifies the facility that manages the medical device; an acquisition unit that acquires from the user terminal the facility identification information that identifies the facility to which the user belongs and user identification information that identifies the user; and a registration unit that sends an approval request for the user identification information to a facility terminal of the facility and registers personal identification information that identifies the user in association with the facility identification information of the facility to which the user belongs, on the condition that an approval response for the user identification information is received from the facility terminal.

[0006] Furthermore, a control method for a remote monitoring system according to one aspect of the present invention is a control method for a remote monitoring system that stores device information indicating the status of a medical device and provides the device information to a user terminal used by a user, wherein the device information is stored in association with device identification information that identifies the medical device and facility identification information that identifies a facility that manages the medical device, the facility identification information that identifies the facility to which the user belongs and user identification information that identifies the user are obtained from the user terminal, and a request for approval of the user identification information is sent to a facility terminal of the facility, and personal identification information that identifies the user is registered in association with the facility identification information of the facility to which the user belongs, on the condition that an approval response for the user identification information is received from the facility terminal. [Effects of the Invention]

[0007] This will enable remote monitoring of medical equipment from both inside and outside the hospital while ensuring security.

[0008] Further features of the invention will become apparent from the following description of an embodiment thereof, given by way of example only and with reference to the accompanying drawings, in which: [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a schematic diagram illustrating a remote monitoring system. [Figure 2] FIG. 1 is a schematic block diagram of a remote monitoring system. [Figure 3] FIG. 1 is a schematic diagram illustrating communication between user terminals. [Figure 4] 10 is a flowchart of a registration process. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, exemplary embodiments for carrying out the present invention will be described in detail with reference to the drawings. However, the dimensions, materials, shapes, and relative positions of components described in the following embodiments can be arbitrarily set and can be changed depending on the configuration of the device to which the present invention is applied or various conditions. Furthermore, unless otherwise specified, the scope of the present invention is not limited to the embodiments specifically described below.

[0011] [First embodiment] The remote monitoring system 100 shown in FIG. 1 stores device information D2 (FIG. 2) indicating the status of an ECMO, which is an example of a medical device 56, and provides the device information D2 to a user terminal 55 used by a user. The provision of the device information D2 may be achieved by transmitting the device information D2 to the user terminal 55, or by viewing the device information D2 via a web page or the like. The remote monitoring system 100 is used not only for remote monitoring using the device information D2, but also for reducing the burden and risk on medical professionals, thereby improving patient safety. The medical device 56 is configured to be connectable to a network, and may also be, for example, an artificial respirator or a suction device that suctions drainage fluid from the patient's body.

[0012] The remote monitoring system 100 also includes a cloud server 50. The cloud server 50 is configured as a single logical server by combining multiple server units 51 as computers. However, the cloud server 50 may also be configured with a single server unit 51. Alternatively, the cloud server 50 may be configured logically using cloud computing. The cloud server 50 is configured to be connectable to a network, and is configured to realize network communication with Hospital A, Hospital B, and an ECMO center, which are examples of facilities.

[0013] As an example, the network realizes network communication using the TCP / IP protocol. Specifically, a local area network (LAN) connects a server unit 51 to the Internet as a wide area network (WAN). In Hospital A, Hospital B, and the ECMO center, personal computers as an example of facility terminals 54, smart devices as an example of user terminals 55, and ECMOs as an example of medical devices 56, and the LAN constituting the hospital network, are connected to the Internet via a router 53. Furthermore, an ambulance 57 is equipped with an ECMO (not shown) connected to the Internet. Note that each device transmits and receives data to and from each other via wireless communication such as mobile communication or wired communication. Furthermore, each device may be connected to each other via the Internet instead of or in addition to the LAN.

[0014] In Hospital A and Hospital B, an ECMO is installed in the ICU (Intensive Care Unit). Medical personnel outside the ICU can monitor the ECMO using a user terminal 55. The user terminal 55 is, for example, a smart device such as a smartphone, and is a portable computer device. In the ECMO center, medical personnel carrying the user terminal 55 are on standby in the ER (Emergency Room). The medical personnel in the ER can view data indicating the status of the ECMO device as device information D2 installed in an ambulance 57 transporting a patient. This allows the medical personnel in the ER to understand the condition of the patient being transported and prepare to accept the patient.

[0015] Furthermore, the ECMO center is staffed with medical professionals with specialized knowledge of ECMO. These medical professionals can collectively monitor data showing the status of the ECMOs installed in Hospital A and Hospital B using the facility terminal 54. This allows medical professionals at multiple facilities to receive analysis, diagnosis, treatment instructions, etc. from medical professionals with specialized knowledge.

[0016] An example of a remote monitoring system 100 shown in Figure 2 includes a cloud server 50, a communication module 56C (Figure 2) that wirelessly outputs data from a medical device 56, a smartphone as an example of a user terminal 55, and a personal computer as an example of a facility terminal 54. This allows a remote monitoring system 100 that can be introduced inexpensively and easily to be provided to medical professionals as users. Furthermore, by using an app described below, the flexibility of the remote monitoring system 100 can be increased and user operation can be simplified.

[0017] The communication module 56C is configured to be able to simultaneously communicate directly with the user terminal 55 and with the router 53 while ensuring security. The communication module 56C is connected to the medical device 56 or is built into the medical device 56. The terminal storage unit 55B of the user terminal 55 stores a smartphone app for monitoring the medical device 56 with a smartphone. Using the smartphone app, the user can view device information D2 of the medical device 56 from inside or outside the hospital while ensuring security, and remotely monitor the medical device 56.

[0018] Furthermore, users can use the smartphone app to exchange information with each other while ensuring security. For example, users can exchange information by chatting with each other or sending and receiving images with comments. Furthermore, users can use the smartphone app to view images or videos captured by a camera capturing the medical device 56 or a camera equipped in the medical device 56. For example, the camera is a smart camera that can be operated by the user terminal 55. If multiple medical devices 56 are registered, a user viewing the images or videos can monitor multiple medical devices 56 at once.

[0019] The management memory unit 54B of the facility terminal 54 stores a PC application for monitoring the medical devices 56 using a personal computer. Using the PC application, users can view device information D2 of the medical devices 56 from inside or outside the hospital while ensuring security, and remotely monitor the medical devices 56. Furthermore, users can use the PC application to view images or videos captured by a camera capturing the medical devices 56 or a camera equipped in the medical devices 56. If multiple medical devices 56 are registered, users viewing the images or videos can monitor multiple medical devices 56 collectively. Furthermore, users can view or use medical-related information D1 stored in the server memory unit 50B of the cloud server 50 using the PC application. For example, the medical-related information D1 includes patient information, facility information, user information, and the like in addition to device information D2 and registration information D3.

[0020] The cloud server 50 accumulates data such as device information D2 of the medical device 56 and stores it in a server storage unit 50B. A server control unit 50A of the cloud server 50 manages users and accumulates data acquired from the medical device 56. Users can access the cloud server 50 using a smartphone app or a PC app. Users can view or use the data accumulated in the cloud server 50 by specifying the date and time associated with the data. Furthermore, the manufacturer of the medical device 56 may be able to view the device information D2 of the medical device 56. The remote monitoring system 100 may further include other commercially available computer devices, a router 53, and a smart camera.

[0021] There is a degree of freedom in the combination of components when introducing the remote monitoring system 100. This makes it easy for medical professionals to use and allows the system to be introduced inexpensively and easily. For example, a user may use the system by simply installing either a PC app or a smartphone app. Furthermore, a user can use the system simply by installing the app on an existing facility terminal 54 or user terminal 55. This allows the user to introduce the remote monitoring system 100 inexpensively and easily.

[0022] The remote monitoring system 100 can minimize the number of times medical personnel enter an ICU, which has a high risk of infection, as a countermeasure against viral infections. In other words, medical personnel can remotely monitor the medical device 56 from outside the ICU, including from their own homes or outside the hospital. For example, medical personnel can monitor the medical device 56 while viewing images or videos captured by a smart camera. Furthermore, the remote monitoring system 100 can reduce the burden on medical personnel. In other words, the number of medical personnel waiting in the ICU can be reduced. Furthermore, since medical personnel can remotely monitor the medical device 56, it can alleviate the situation where medical personnel have difficulty returning home. Furthermore, users can exchange information with each other while ensuring security.

[0023] Furthermore, the remote monitoring system 100 can improve medical safety. That is, even if a skilled medical professional is in a remote location, the medical professional can provide advice. Furthermore, device information D2 indicating an abnormality that has occurred in the medical device 56 can be notified to the user terminal 55. For example, information such as an alarm output from the medical device 56 used for critically ill patients in the ICU can be notified to the user terminal 55 via the cloud server 50. This reduces the risk that the medical professional will miss an alarm.

[0024] Furthermore, the remote monitoring system 100 enables the establishment of a new medical care delivery system. That is, the remote monitoring system 100 processes information obtained from multiple facilities (e.g., Hospital A and Hospital B) as well as information obtained from facilities that cooperate with the hospital (e.g., ECMO centers) in real time. This makes it possible to transform the medical care delivery system at each hospital into a new medical care delivery system that utilizes a network. Also, big data accumulated in the cloud server 50 can be used for analysis and assistance using AI (artificial intelligence). Furthermore, advanced medical devices 56 such as ECMO can be used even when medical personnel are at home. Furthermore, various medical-related information D1 can be shared between the origin and destination of the patient during transport.

[0025] [System control] As shown in FIG. 2, the cloud server 50 has a server control unit 50A and a server storage unit 50B. The facility terminal 54 has a management control unit 54A and a management storage unit 54B. The user terminal 55 has a terminal control unit 55A and a terminal storage unit 55B. The medical device 56 has a device control unit 56A and a device storage unit 56B. The server control unit 50A, the management control unit 54A, the terminal control unit 55A, and the device control unit 56A (hereinafter also referred to as "each control unit") each have a processor (not shown). As an example, the processor of each control unit is a CPU (Central Processing Unit) or an MPU (Micro-Processing Unit), which controls the entire device and also comprehensively controls various processes based on programs stored in memory.

[0026] The server storage unit 50B, management storage unit 54B, terminal storage unit 55B, and device storage unit 56B (hereinafter also referred to as "each storage unit") are computer-readable non-transitory recording media. Each storage unit stores a control program for each device. Each storage unit includes a random access memory (RAM), which is a system work memory for the processor to operate, as well as a read-only memory (ROM) for storing programs and system software, a hard disk drive (HDD), a solid state drive (SSD), or other storage device. In this embodiment, the CPU executes various processing operations, such as calculations, controls, and determinations, in accordance with the control program stored in the ROM or HDD.

[0027] Each control unit is connected, either wired or wirelessly, to an operation unit including a touch panel, keyboard, or various switches as an input device for inputting predetermined commands and data. A display unit is also connected, either wired or wirelessly, to the control unit, which displays the input status, setting status, measurement results, and various information of the device. The control unit can also control each function according to a program stored on a portable recording medium such as a CD (Compact Disc), DVD (Digital Versatile Disc), CF (Compact Flash) card, or USB (Universal Serial Bus) memory, or on an external storage medium such as a server on the Internet.

[0028] The server storage unit 50B of the cloud server 50 is an example of a storage unit that stores device information D2. The server storage unit 50B stores medical-related information D1 including the device information D2. The medical-related information D1 also includes registration information D3 including various types of identification information. Specifically, the registration information D3 includes device identification information that identifies each medical device 56, facility identification information that identifies each facility that manages the medical device 56, and personal identification information that identifies each user. For example, each of multiple facilities, such as a hospital, manages multiple medical devices 56, such as ECMO. Each of the multiple facilities has multiple users. The device identification information of each medical device 56 at each facility and the personal identification information of each user are included in the registration information D3.

[0029] The facility identification information is information unique to each of the multiple facilities, and an example of such information is a facility ID. The device identification information is information unique to each of the multiple medical devices 56, and an example of such information is a device ID. The server storage unit 50B stores the device identification information of the medical device 56 in association with the facility identification information of the facility that manages the medical device 56. The personal identification information is information unique to each of the multiple users, and an example of such information is a personal ID. The server storage unit 50B stores the personal identification information of the user in association with the facility identification information of the facility to which the user belongs.

[0030] The server storage unit 50B also stores device information D2 in association with device identification information for identifying the medical device 56 and facility identification information for identifying the facility that manages the medical device 56. For example, the server storage unit 50B stores image information related to the medical device 56 in association with the device identification information and facility identification information as the device information D2. The image information is, for example, an image or video of the screen of the medical device 56 captured by a camera. The image information may also be an image or video of a screen output from the medical device 56. The device information D2 may also be data indicating an abnormality in the medical device 56 or data indicating the operating status of the medical device 56. The device information D2 may also be data detected by the medical device 56, such as the value of the inhalation pressure and the value of the oxygen concentration during inhalation. The data detected by the medical device 56 may include data indicating the patient's condition.

[0031] Furthermore, the server storage unit 50B stores a monitoring program PG. The monitoring program PG causes the server control unit 50A, which is a computer, to function as an acquisition unit 11, a registration unit 12, and an authentication unit 13. In other words, the server control unit 50A has the acquisition unit 11, the registration unit 12, and the authentication unit 13 as logical devices realized by a combination of computer hardware and software.

[0032] When the registration unit 12 registers a user for use, the acquisition unit 11 acquires facility identification information that identifies the facility to which the user belongs and user identification information that identifies the user from the user terminal 55. As an example, the user identification information is information that can identify each user, such as the user's name, account name, telephone number, and employee number. To register themselves as a system user, the user accesses the cloud server 50 from the user terminal 55. Then, the user inputs the facility ID, the password set for each facility, and the user identification information. The acquisition unit 11 then acquires this information input from the user terminal 55.

[0033] Furthermore, the acquisition unit 11 acquires facility identification information and personal identification information from the user terminal 55 when the authentication unit 13 authenticates the user terminal 55. As an example, when a user accesses the cloud server 50, the user inputs a facility ID, a personal ID, and a password set for each facility. Then, the acquisition unit 11 acquires this information input from the user terminal 55.

[0034] When a user who registers for use inputs facility identification information and user identification information from user terminal 55, registration unit 12 transmits an approval request for the user identification information to facility terminal 54 of the facility. Then, on the condition that an approval response for the user identification information is received from facility terminal 54, registration unit 12 registers personal identification information that identifies the user, linking it with facility identification information of the facility to which the user belongs. Furthermore, registration unit 12 transmits the registered personal identification information to user terminal 55. Note that when registering for use, a registration request may be transmitted from user terminal 55 to cloud server 50 together with the facility identification information and user identification information. Registration unit 12 transmits an approval request to facility terminal 54 in response to the registration request.

[0035] As an example, the registration unit 12 transmits the name of the user who has applied for user registration to the facility terminal 54 linked to the facility identification information entered by the user. Alternatively, the registration unit 12 transmits some or all of the user identification information received from the user terminal 55 to the facility terminal 54. The administrator of each facility checks the user name received at the facility terminal 54 and approves the user registration. The administrator then transmits an approval response from the facility terminal 54 to the cloud server 50. Note that the approval response may be automatically sent by the management control unit 54A on the condition that the user identification information transmitted by the registration unit 12 matches the user identification information stored in the management storage unit 54B.

[0036] This allows users to remotely monitor medical devices from inside and outside the hospital while ensuring security. The registration unit 12 may also transmit an approval request to the facility terminal 54 every time it is accessed from the user terminal 55, or periodically, such as monthly. The facility terminal 54 may be a server device installed in the hospital, such as a Hospital Information System (HIS), a Radiology Information System (RIS), or a Picture Archiving and Communication System (PACS). The facility terminal 54 may also be installed outside the hospital.

[0037] Furthermore, the registration unit 12 registers device identification information in response to a request from the facility terminal 54 or the medical device 56. As an example, the acquisition unit 11 acquires device identification information of the medical device 56 and facility identification information of the facility that manages the medical device 56. Then, the registration unit 12 associates the acquired device identification information with the facility identification information, registers it, and stores it in the server storage unit 50B. The registration unit 12 may also associate information such as the serial number and manufacturer name of the medical device 56 with the device identification information and facility identification information, and store it in the server storage unit 50B.

[0038] The authentication unit 13, which authenticates the user terminal 55, authenticates the user terminal 55 using the facility identification information and personal identification information acquired from the user terminal 55 by the acquisition unit 11. The authentication unit 13 also transmits device information D2 linked to the facility identification information acquired from the user terminal 55 by the acquisition unit 11 to the authenticated user terminal 55. Specifically, when the facility identification information of Hospital A is acquired from the user terminal 55, the authentication unit 13 transmits device information D2 of the medical device 56 managed by Hospital A to the user terminal 55. That is, the authentication unit 13 transmits the device information D2 linked to the facility identification information of Hospital A to the user terminal 55. For example, the authentication unit 13 transmits the device information D2 to the user terminal 55 in response to an acquisition request from the user terminal 55. Alternatively, the authentication unit 13 may automatically transmit the device information D2 to the user terminal 55 when the user terminal 55 accesses the cloud server 50.

[0039] Furthermore, the authentication unit 13 may transmit image information linked to the acquired facility identification information to the authenticated user terminal 55. This image information is an image related to the medical device 56, and is stored in the server storage unit 50B in association with the device identification information and the facility identification information.

[0040] Furthermore, if the facility identification information associated with the personal identification information acquired from the authenticated user terminal 55 is the same as the facility identification information associated with the personal identification information acquired from the authenticated user terminal 55, the authentication unit 13 allows communication between the authenticated user terminal 55 and another user terminal used by the other user. Specifically, referring to FIG. 3, multiple users are registered in the remote monitoring system 100. The personal identification information of multiple users belonging to the same facility (Hospital A in FIG. 3) is associated with the same facility identification information. Therefore, the authentication unit 13 allows communication between the user terminals 55 of multiple users identified by the personal identification information associated with the same facility identification information. For example, communication between the user terminals 55 is performed via mobile communication or wireless or wired communication via an access point. For example, communication between users may involve exchanging medical-related information D1, chatting, or sending and receiving images with comments.

[0041] Furthermore, in communication within a facility, communication may be permitted between the authenticated user terminal 55 and a medical device 56 identified by device identification information linked to the same facility identification information as the facility identification information acquired from the authenticated user terminal 55. In the example of FIG. 3, communication between the user terminal 55 and the medical device 56 is performed by wireless communication using the Wi-Fi standard or the like. For example, the medical device 56 is connected to the user terminal 55 via a LAN and performs a predetermined process in accordance with an instruction from the user terminal 55. Alternatively, the medical device 56 outputs device information D2 to the user terminal 55.

[0042] The communication module 56C may also have an access point function. In the hospital A shown in Fig. 3, a server unit 51, a facility terminal 54, a user terminal 55, and a medical device 56 installed in the hospital are connected to the Internet via a router 53. Furthermore, when the communication module 56C functions as an access point, multiple user terminals 55 can communicate with each other via the communication module 56C.

[0043] According to the remote monitoring system 100 described above, access and registration restrictions are implemented to prevent third parties from accessing the medical-related information D1 by combining access management using a personal ID and password with registration authentication using an approval response from the facility terminal 54. That is, a facility ID identifying each facility is assigned to a device ID identifying each medical device 56 based on the addition of a facility ID identifying each facility and approval by an administrator at each facility. Then, the data stored in the remote monitoring system 100 is managed to identify which medical device 56 in which facility it belongs. Furthermore, for medical personnel, the facility ID is associated with the user's personal ID, and registration of the personal ID is approved by an administrator at each facility. This facility ID serves as identification information for identifying a group with which data can be shared. Furthermore, two-step authentication, consisting of authentication using a personal ID and approval at the time of user registration, prevents third parties from accessing data within the group, thereby enhancing security.

[0044] [Registration process] The user registration process in the remote monitoring system 100 will be described with reference to Fig. 4. First, a user who wishes to register to use the system inputs facility identification information that identifies the facility to which the user belongs and user identification information that identifies the user, from the user terminal 55, and transmits these to the cloud server 50. Then, the acquisition unit 11 acquires the facility identification information and the user identification information from the user terminal 55 (S101). Next, the registration unit 12 transmits an approval request for the user identification information to the facility terminal 54 of the facility identified by the facility identification information acquired by the acquisition unit 11 (S102).

[0045] When the registration unit 12 receives an approval response for the user identification information from the facility terminal 54 (YES in S103), it registers the user's personal identification information in association with the facility identification information (S104). The registration unit 12 also transmits the registered personal identification information to the user terminal 55 (S105), completing the registration process. This allows the user to obtain the registered personal identification information and use the remote monitoring system 100. On the other hand, if the user should not be registered (NO in S103), for example, if the user identified by the user identification information does not belong to a facility managed by the administrator, the administrator performs an operation to not approve the user registration.

[0046] Then, information indicating non-approval is transmitted from facility terminal 54 to cloud server 50 (S105). As an example, when the administrator selects the non-approval button, a non-approval signal is transmitted to cloud server 50. When registration unit 12 receives the non-approval information, it transmits information indicating that registration is not possible to user terminal 55. Then, the registration process ends.

[0047] The remote monitoring system 100 described above allows a user to remotely monitor a medical device 56 from inside or outside a hospital while ensuring security. While the present invention has been described with reference to the above-described embodiments, the present invention is not limited to these embodiments. The present invention also includes inventions that are modified without departing from the scope of the present invention, and inventions equivalent to the present invention. Furthermore, the embodiments and variations can be combined as appropriate without departing from the scope of the present invention.

[0048] For example, a storage unit that stores device information D2 may be provided separately from the cloud server 50. Furthermore, at least one of the registration unit 12 and the authentication unit 13 may be provided in a server or facility terminal 54 of each facility. As an example, if the authentication unit 13 is provided in the facility terminal 54, the authentication unit 13 transmits an authentication token to the authenticated user terminal 55. Then, the user terminal 55 acquires device information D2 from the cloud server 50 using the authentication token. Furthermore, if the registration unit 12 is provided in the facility terminal 54, the registration unit 12 transmits the user's personal identification information and facility identification information together with a registration request to the cloud server 50. Then, the server storage unit 50B stores the personal identification information in association with the facility identification information. [Explanation of symbols]

[0049] 11: Acquisition part 12: Registration section 13: Authentication section 50B: Server memory unit (memory unit) 55: User terminal 56: Medical devices, 100: Remote monitoring system D2:Device information

Claims

1. 1. A remote monitoring system that stores device information indicating the status of a medical device and provides the device information to a user terminal used by a user, a storage unit that stores the device information in association with device identification information that identifies the medical device and facility identification information that identifies a facility that manages the medical device; an acquisition unit that acquires, from the user terminal, the facility identification information that identifies the facility to which the user belongs and user identification information that identifies the user; A remote monitoring system comprising: a registration unit that sends an approval request for the user identification information to a facility terminal of the facility identified by the facility identification information, and, on the condition that an approval response for the user identification information is received from the facility terminal of the facility that manages the medical device, registers personal identification information that identifies the user in association with the facility identification information of the facility to which the user belongs.

2. further comprising an authentication unit that authenticates the user terminal; the acquisition unit acquires the facility identification information and the personal identification information from the user terminal; The remote monitoring system of claim 1, wherein the authentication unit authenticates the user terminal using the acquired facility identification information and the personal identification information, and provides the device information linked to the acquired facility identification information to the user terminal.

3. the storage unit stores image information related to the medical device in association with the device identification information and the facility identification information; The remote monitoring system according to claim 2 , wherein the authentication unit provides the image information linked to the acquired facility identification information to the user terminal.

4. An authentication unit that authenticates the user terminal using the facility identification information and the personal identification information, the storage unit stores the personal identification information of the user in association with the facility identification information of the facility to which the user belongs; The remote monitoring system of claim 1, wherein the authentication unit allows communication between the authenticated user terminal and another user terminal used by the other user when other personal identification information identifying another user is linked to facility identification information that is the same as the facility identification information linked to the personal identification information obtained from the authenticated user terminal.

5. 1. A method for controlling a remote monitoring system, performed by a computer, which stores device information indicating the status of a medical device and provides the device information to a user terminal used by a user, comprising: storing the device information in association with device identification information for identifying the medical device and facility identification information for identifying a facility that manages the medical device; acquiring, from the user terminal, the facility identification information that identifies the facility to which the user belongs and user identification information that identifies the user; A control method for a remote monitoring system, which sends an approval request for the user identification information to a facility terminal of the facility identified by the facility identification information, and, on the condition that an approval response for the user identification information is received from the facility terminal of the facility that manages the medical device, registers personal identification information that identifies the user in association with the facility identification information of the facility to which the user belongs.

Images