JP2023030720A - Remote monitoring system, and remote monitoring system control method - Google Patents

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

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.

In recent years, there are concerns about a labor shortage due to aging and population decline, and it is necessary to respond to the labor shortage in medical care. In addition, due to the outbreak of the new coronavirus, there is a need for a new medical care provision system aimed at reducing the risk of infection and reducing the burden on medical workers. In order to deal with these problems, large-scale remote monitoring systems with high installation costs are being researched.

For example, there are systems for remotely monitoring and managing patients with ECMO (Extracorporeal Membrane Oxygenation) using any mobile device. In addition, a project is underway in which medical-related information from intensive care units in multiple hospitals is connected via network communications, and intensive care specialists monitor patients from a support center.

However, what medical professionals want is a remote monitoring system that is easy to use, has low installation costs, and ensures security. And no such remote monitoring system exists.

A remote monitoring system according to one aspect of the present invention is a remote monitoring system that stores device information indicating the state of a medical device and provides the device information to a user terminal used by a user, wherein the medical device and a storage unit that stores the device information in association with facility identification information that identifies a facility that manages the medical device, and identifies the facility to which the user belongs from the user terminal. an acquisition unit for acquiring said facility identification information and user identification information for identifying said user; and transmitting a request for approval of said user identification information to a facility terminal of said facility and approval of said user identification information from said facility terminal. A registration unit for registering personal identification information identifying the user in association with the facility identification information of the facility to which the user belongs, on condition that a response is received.

A control method for a remote monitoring system according to an aspect of the present invention stores device information indicating the state of a medical device, and provides the device information to a user terminal used by a user. wherein the device information is linked to device identification information that identifies the medical device and facility identification information that identifies a facility that manages the medical device, and the user belongs to the medical device from the user terminal. acquiring the facility identification information that identifies the facility and the user identification information that identifies the user, transmits a request for approval of the user identification information to the facility terminal of the facility, and transmits the user identification information from the facility terminal personal identification information for identifying the user is registered in association with the facility identification information for the facility to which the user belongs, on condition that an approval response is received.

This enables remote monitoring of medical devices from inside and outside the hospital while ensuring security.

Further features of the invention will become apparent from the following description of an exemplary embodiment, given by way of example with reference to the accompanying drawings.

Schematic for explaining a remote monitoring system. Schematic block diagram of a remote monitoring system. Schematic diagram for explaining communication between user terminals. A flowchart of registration processing.

Exemplary embodiments for carrying out the present invention will now 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 according to the configuration of the apparatus to which the present invention is applied or various conditions. Also, unless otherwise stated, the scope of the invention is not limited to the embodiments specifically described below.

[First embodiment]
The remote monitoring system 100 shown in FIG. 1 stores device information D2 (FIG. 2) indicating the state of the ECMO, which is an example of the medical device 56, and provides the device information D2 to the user terminal 55 used by the user. The device information D2 may be provided 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. In addition, the remote monitoring system 100 is used not only for remote monitoring using the device information D2, but also for the purpose of reducing the burden and risk of medical staff. As a result, patient safety can be improved. The medical device 56 is configured to be connectable to a network, and may be, as another example, an artificial respirator or a suction device for sucking drainage from the patient's body.

The remote monitoring system 100 also has a cloud server 50 . The cloud server 50 is configured as one logical server by combining server units 51 as a plurality of computers. However, the cloud server 50 may be configured with a single server unit 51 . Alternatively, the cloud server 50 may be logically configured 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.

As an example, the network utilizes the TCP/IP protocol to implement network communications. Specifically, a LAN (Local Area Network) connects the server unit 51 and the Internet as a WAN (Wide Area Network). In Hospital A, Hospital B, and the ECMO center, a personal computer as an example of the facility terminal 54, a smart device as an example of the user terminal 55, and an ECMO as an example of the medical device 56 constitute an intra-hospital network. LAN is connected to the Internet via a router 53 . Furthermore, an ECMO (not shown) connected to the Internet is installed in the ambulance 57 . Each device transmits and receives data to and from each other by wireless communication such as mobile communication or wired communication. Also, each device may be interconnected by the Internet instead of or in addition to the LAN.

In Hospital A and Hospital B, ECMOs are installed in ICUs (Intensive Care Units). Medical personnel outside the ICU can then use the user terminal 55 to monitor the ECMO. The user terminal 55 is, for example, a smart device such as a smart phone, and is a portable computer device. Also, in the ECMO center, a medical worker with a user terminal 55 stands by in an ER (Emergency Room). Then, the medical staff in the ER can see the data indicating the state of the ECMO installed in the ambulance 57 that is transporting the patient as the device information D2. As a result, the medical staff in the ER can grasp the condition of the patient during transportation and prepare for receiving the patient.

In addition, ECMO centers are staffed by medical personnel with ECMO expertise. A medical worker with specialized knowledge can collectively monitor the data indicating the status of the ECMOs installed in Hospital A and Hospital B using the facility terminal 54 . As a result, medical staff at multiple facilities can receive analysis, diagnosis, treatment instructions, and the like from medical staff with specialized knowledge.

A remote monitoring system 100 as an example shown in FIG. and a personal computer as an example. As a result, the remote monitoring system 100 that can be introduced inexpensively and easily can be provided to medical workers as users. Further, by using an application to be described later, the degree of freedom of the remote monitoring system 100 can be increased, and the user's operation can be simplified.

The communication module 56C is configured so that direct communication with the user terminal 55 and communication with the router 53 can be performed simultaneously while ensuring security. The communication module 56C is connected to the medical device 56 or built into the medical device 56. FIG. In addition, the terminal storage unit 55B of the user terminal 55 stores a smart phone application for monitoring the medical device 56 with a smart phone. The user can view the device information D2 of the medical device 56 from inside or outside the hospital and remotely monitor the medical device 56 by using the smartphone application while ensuring security.

In addition, users can exchange information with each other while ensuring security by using smartphone applications. For example, exchange of information between users includes chatting between users, transmission and reception of images with comments, and the like. Furthermore, the user can use the smartphone application to view images or videos taken by the camera that projects the medical device 56 or by the camera that the medical device 56 has. For example, the camera is a smart camera that can be operated by user terminal 55 . Then, when multiple medical devices 56 are registered, the user viewing the image or video can collectively monitor multiple medical devices 56 .

The management storage unit 54B of the facility terminal 54 stores a PC application for monitoring the medical device 56 with a personal computer. The user can view the device information D2 of the medical device 56 from inside or outside the hospital and remotely monitor the medical device 56 by using the PC application while ensuring security. In addition, the user can use the PC application to view images or videos taken by the camera that projects the medical device 56 or by the camera that the medical device 56 has. Then, when multiple medical devices 56 are registered, the user viewing the image or video can collectively monitor multiple medical devices 56 . Furthermore, the user can view or use the medical-related information D1 stored in the server storage unit 50B of the cloud server 50 using the PC application. As an example, the medical-related information D1 includes patient information, facility information, user information, etc., in addition to device information D2 and registration information D3.

The cloud server 50 accumulates data such as the device information D2 of the medical device 56 and stores it in the server storage section 50B. The server control unit 50A of the cloud server 50 manages users and accumulates data acquired from the medical devices 56. FIG. Also, the user can access the cloud server 50 using a smartphone application or a PC application. Then, the user can view or use the data accumulated in the cloud server 50 by designating the date and time associated with the data. Furthermore, the manufacturer of medical device 56 may be able to view device information D2 of medical device 56 . Note that the remote monitoring system 100 may further include other commercially available computer devices, routers 53, and smart cameras.

There is flexibility in the combination of each configuration when introducing the remote monitoring system 100 . As a result, the system can be easily introduced at a low cost and is easy to use for medical personnel. For example, the user may use the system only by installing either a PC application or a smartphone application. Furthermore, the user can use the system simply by installing an application on the existing facility terminal 54 or user terminal 55 . Therefore, the user can introduce the remote monitoring system 100 easily and inexpensively.

According to the remote monitoring system 100, as a countermeasure against viral infections, it is possible to minimize the number of visits by medical staff to ICUs with a high infection risk. That is, medical personnel can remotely monitor medical device 56 from outside the ICU, including at home and out of the hospital. For example, medical personnel can monitor medical device 56 while viewing images or videos captured by smart cameras. Moreover, according to the remote monitoring system 100, the burden on the medical staff can be reduced. That is, the number of medical staff waiting in the ICU can be reduced. Furthermore, since the medical staff can remotely monitor the medical device 56, it is possible to improve the situation in which it is difficult for the medical staff to return home. In addition, users can exchange information while ensuring security.

Moreover, according to the remote monitoring system 100, medical safety can be improved. That is, even if a skilled medical worker is in a remote location, advice can be received from the medical worker. Device information D2 indicating an abnormality that has occurred in the medical device 56 can also be notified to the user terminal 55 . For example, the user terminal 55 can be notified via the cloud server 50 of information such as alarms output from the medical device 56 used for critically ill patients in the ICU. This reduces the risk of health care workers missing alarms.

Furthermore, according to the remote monitoring system 100, a new medical care provision system can be constructed. That is, the remote monitoring system 100 processes, in real time, information obtained from a plurality of facilities (for example, Hospital A and Hospital B) as well as information obtained from facilities (for example, the ECMO Center) that cooperate with the hospital. As a result, it is possible to change the medical care delivery system of each hospital to a new medical care delivery system using the network. Also, the big data accumulated in the cloud server 50 can be utilized for analysis and assistance by AI (Artificial Intelligence). Furthermore, advanced medical equipment 56 such as ECMO can be utilized even when medical personnel are at home. Furthermore, various medical-related information D1 can be shared between the transportation source and the transportation destination while the patient is being transported.

[System control system]
As shown in FIG. 2, the cloud server 50 has a server control section 50A and a server storage section 50B. The facility terminal 54 also has a management control section 54A and a management storage section 54B. The user terminal 55 also has a terminal control section 55A and a terminal storage section 55B. The medical device 56 also has a device control section 56A and a device storage section 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") all have processors (not shown). As an example, the processor of each control unit is a CPU (Central Processing Unit) or MPU (Micro-Processing Unit). also comprehensively control.

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-temporary recording media. Each storage unit stores a control program for each device. In addition, each storage unit includes RAM (Random Access Memory) which is a system work memory for the processor to operate, ROM (Read Only Memory) which stores programs and system software, HDD (Hard Disc Drive) and SSD (Solid State Drive) and other storage devices. In this embodiment, the CPU executes various processing operations such as calculation, control, and determination according to control programs stored in the ROM or HDD.

An operation unit including a touch panel, a keyboard, or various switches is wired or wirelessly connected to each control unit as an input device for inputting predetermined commands and data. A display unit for displaying the input state, setting state, measurement results, and various information of the apparatus is wired or wirelessly connected to the control unit. In addition, the control unit is a portable recording medium such as a CD (Compact Disc), a DVD (Digital Versatile Disc), a CF (Compact Flash) card, and a USB (Universal Serial Bus) memory, or an external storage such as a server on the Internet. Each action can also be controlled according to a program stored on the medium.

The server storage unit 50B of the cloud server 50 is an example of a storage unit that stores the device information D2. The server storage unit 50B stores medical-related information D1 including device information D2. Further, the medical-related information D1 includes registration information D3 including various kinds 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, multiple facilities such as hospitals each manage multiple medical devices 56 such as ECMOs. In addition, multiple users belong to each of the multiple facilities. Device identification information of each medical device 56 of each facility and personal identification information of each user are included in the registration information D3.

The facility identification information is information specific to each of a plurality of facilities, and is, for example, a facility ID. Further, the device identification information is information unique to each of the plurality of medical devices 56, and an example 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 . Furthermore, the personal identification information is information specific to each of a plurality of users, and is an individual ID as an example. 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.

Further, the server storage unit 50B stores device information D2 in association with device identification information that identifies the medical device 56 and facility identification information that identifies 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 the 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 a screen image or video output from the medical device 56 . Further, the device information D2 may be data indicating an abnormality of the medical device 56 or data indicating the operation status of the medical device 56 . Further, the device information D2 may be data detected by the medical device 56, such as the value of the inspiratory pressure and the value of the oxygen concentration during inhalation. The data detected by the medical device 56 may include data indicative of the patient's condition.

Furthermore, the server storage unit 50B stores a monitoring program PG. The monitoring program PG causes the server control unit 50A as a computer to function as the acquiring unit 11, the registering unit 12, and the authenticating unit 13. FIG. That is, the server control unit 50A has an acquisition unit 11, a registration unit 12, and an authentication unit 13 as logical devices realized by combining computer hardware and software.

The acquisition unit 11 acquires facility identification information for identifying the facility to which the user belongs and user identification information for identifying the user from the user terminal 55 when the user is registered for use by the registration unit 12 . As an example, user identification information is information that can identify each user, such as the user's name, account name, telephone number, and employee number. A user accesses the cloud server 50 from a user terminal 55 in order to register himself/herself as a user of the system. Then, the user inputs a facility ID, a password set for each facility, and user identification information. The acquisition unit 11 then acquires these pieces of information input from the user terminal 55 .

Further, the acquisition unit 11 acquires facility identification information and personal identification information from the user terminal 55 when the user terminal 55 is authenticated by the authentication unit 13 . As an example, when the user accesses the cloud server 50, the user inputs a facility ID, a personal ID, and a password set for each facility. The acquisition unit 11 then acquires these pieces of information input from the user terminal 55 .

When a user who registers for use inputs the facility identification information and the user identification information from the user terminal 55, the registration unit 12 transmits an approval request for the user identification information to the facility terminal 54 of the facility. Then, the registration unit 12 registers the personal identification information identifying the user in association with the facility identification information of the facility to which the user belongs, on condition that the approval response of the user identification information is received from the facility terminal 54 . Furthermore, the registration unit 12 transmits the registered personal identification information to the user terminal 55 . When registering for use, a registration request may be sent from the user terminal 55 to the cloud server 50 together with the facility identification information and the user identification information. The registration unit 12 transmits an approval request to the facility terminal 54 in response to the registration request.

As an example, the registration unit 12 transmits the name of the user for whom usage registration has been applied to the facility terminal 54 linked to the facility identification information input by the user. Alternatively, the registration unit 12 transmits part or all of the user identification information received from the user terminal 55 to the facility terminal 54 . The manager of each facility confirms the user's name received at the facility terminal 54 and approves the usage 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. .

As a result, the user can remotely monitor medical devices from inside and outside the hospital while ensuring security. Further, the registration unit 12 may transmit an approval request to the facility terminal 54 each time the user terminal 55 accesses the facility terminal 55 or at regular timing such as every month. The facility terminal 54 may be a server device installed in the hospital, such as HIS (Hospital Information System), RIS (Radiology Information System), or PACS (Picture Archiving and Communication System). Also, the facility terminal 54 may be installed outside the hospital.

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 the device identification information of the medical device 56 and the facility identification information of the facility that manages the medical device 56 . Then, the registration unit 12 associates and registers the acquired device identification information with the facility identification information, and stores them in the server storage unit 50B. Further, the registration unit 12 may store information such as the manufacturing number and manufacturer name of the medical device 56 in the server storage unit 50B in association with the device identification information and the facility identification information.

The authentication unit 13 that authenticates the user terminal 55 authenticates the user terminal 55 using the facility identification information and the personal identification information acquired from the user terminal 55 by the acquisition unit 11 . Further, the authentication unit 13 transmits the 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 the hospital A is acquired from the user terminal 55 , the authentication unit 13 transmits the device information D2 of the medical device 56 managed by the hospital A to the user terminal 55 . That is, the authentication unit 13 transmits the device information D<b>2 linked to the facility identification information of the hospital A to the user terminal 55 . For example, the authentication unit 13 transmits the device information D<b>2 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 .

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.

In addition, the authentication unit 13 associates the same facility identification information as the facility identification information associated with the personal identification information acquired from the authenticated user terminal 55 with other personal identification information that identifies other users. If so, communication between the authenticated user terminal 55 and other user terminals used by the other user is permitted. More specifically, referring to FIG. 3, multiple users are registered in the remote monitoring system 100 . The personal identification information of multiple users who belong to the same facility (Hospital A in FIG. 3) is associated with the same facility identification information. Therefore, the authentication unit 13 permits communication between the user terminals 55 of multiple users identified by personal identification information linked to the same facility identification information. By way of example, communication between user terminals 55 may be by wireless or wired communication via mobile communication or access points. For example, in communication between users, exchange of medical-related information D1, chat, transmission and reception of images with comments, and the like are performed.

In communication within the facility, the medical device 56 identified by the device identification information linked to the same facility identification information as the facility identification information acquired from the authenticated user terminal 55 and the authenticated user terminal 55 communication with other user terminals 55 may be permitted. In the example of FIG. 3, communication between the user terminal 55 and the medical device 56 is performed by wireless communication using the Wifi standard or the like. For example, the medical device 56 is connected to the user terminal 55 via LAN, and performs predetermined processing according to instructions from the user terminal 55 . Alternatively, the medical device 56 outputs the device information D2 to the user terminal 55. FIG.

Also, the communication module 56C may have an access point function. In a 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. FIG. 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.

According to the remote monitoring system 100 described above, in order to prevent third parties from accessing the medical-related information D1, access control is performed by combining access management using a personal ID and password and registration authentication based on an approval response from the facility terminal 54. and registration restrictions. That is, based on the addition of facility IDs that identify each facility and the approval of the administrator of each facility, the facility ID is associated with the device ID that identifies each medical device 56 . Then, it is managed which medical device 56 in which facility the data accumulated in the remote monitoring system 100 belong to. In addition, the facility ID and the personal ID of the user are also associated with the medical staff, and the registration of the personal ID is approved by the administrator of each facility. This facility ID serves as identification information for identifying groups with which data can be shared. In addition, since a two-step authentication is performed by authentication by personal ID and approval at the time of user registration, a third party cannot access data in the group, and security can be enhanced.

[registration process]
User registration processing in the remote monitoring system 100 will be described with reference to FIG. First, a user who wishes to register for use of the system inputs facility identification information identifying the facility to which he/she belongs and user identification information identifying himself/herself from the user terminal 55 and transmits the information to the cloud server 50 . Then, the acquisition unit 11 acquires facility identification information and user identification information from the user terminal 55 (S101). Subsequently, 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).

When the registration unit 12 receives an approval response of the user identification information from the facility terminal 54 (YES in S103), the registration unit 12 registers the user's personal identification information in association with the facility identification information (S104). Further, the registration unit 12 transmits the registered personal identification information to the user terminal 55 (S105), and the registration process ends. 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 not to approve user registration. conduct.

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

According to the remote monitoring system 100 described above, the user can remotely monitor the medical device 56 from inside and outside the hospital while ensuring security. Although the present invention has been described with reference to each embodiment, the present invention is not limited to the above embodiments. Inventions modified within the scope of the present invention and inventions equivalent to the present invention are also included in the present invention. Further, each embodiment and each modification can be appropriately combined within a range not contrary to the present invention.

For example, a storage unit that stores the device information D2 may be provided separately from the cloud server 50 . At least one of the registration unit 12 and the authentication unit 13 may be provided in the server or facility terminal 54 of each facility. As an example, when 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 the device information D2 from the cloud server 50 using the authentication token. Further, when the registration unit 12 is provided in the facility terminal 54, the registration unit 12 transmits the user's personal identification information and the facility identification information to the cloud server 50 together with the registration request. Then, the server storage unit 50B stores the personal identification information in association with the facility identification information.

11: Acquisition unit 12: Registration unit 13: Authentication unit 50B: Server storage unit (storage unit)
55: user terminal 56: medical device,
100: Remote monitoring system D2: Equipment information

Claims (5)

A remote monitoring system that stores device information indicating the state 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 the user identification information that identifies the user;
On the condition that a request for approval of the user identification information is transmitted to the facility terminal of the facility and an approval response of the user identification information is received from the facility terminal, the personal identification information that identifies the user is sent to the facility terminal to which the user belongs. A remote monitoring system, comprising: a registration unit that registers the facility identification information of the facility in association with the facility identification information. 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 authentication unit authenticates the user terminal using the acquired facility identification information and the personal identification information, and transmits the device information linked to the acquired facility identification information to the user terminal. 2. The remote monitoring system of claim 1, wherein: The storage unit stores image information related to the medical device in association with the device identification information and the facility identification information,
3. The remote monitoring system according to claim 2, wherein said authentication unit provides said user terminal with said image information linked to said acquired facility 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 authentication unit associates the same facility identification information as the facility identification information associated with the personal identification information acquired from the authenticated user terminal with other personal identification information that identifies other users. 4. The remote monitoring system according to claim 2 or 3, wherein communication between the authenticated user terminal and the other user terminal used by the other user is allowed if the user terminal is authenticated. A remote monitoring system control method for storing device information indicating the state of a medical device and providing the device information to a user terminal used by a user, comprising:
storing 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;
obtaining from the user terminal the facility identification information identifying the facility to which the user belongs and the user identification information identifying the user;
On the condition that a request for approval of the user identification information is transmitted to the facility terminal of the facility and an approval response of the user identification information is received from the facility terminal, the personal identification information that identifies the user is sent to the facility terminal to which the user belongs. A control method for a remote monitoring system, wherein the facility identification information of the facility is linked and registered.

Images