Patient monitor and device information management method thereof

Abstract

A patient monitor is connected to at least one medical device and a device management server for communication. The patient monitor includes: a parameter sensor attachment for real-time acquisition of physiological parameter signals of a monitored object; a processor for acquiring physiological parameter signals from the parameter sensor attachment and processing the physiological parameter signals to obtain corresponding physiological parameter data; and a communication interface for acquiring device management information of the medical device from the medical device and sending the device management information to the device management server. Automatic network collection of device management information centered on the patient monitor is realized.

Description

Technical Field

[0001] The present application relates to the technical field of medical equipment, and more specifically, to a patient monitor and a method for managing device information thereof. Background Art

[0002] In the medical field, equipment is needed to monitor and provide medical care to the monitored objects. Medical equipment includes but is not limited to bedside equipment, such as infusion pumps, ventilators, anesthesia machines, etc. In order to monitor the working status of medical equipment, equipment managers need to collect equipment information and manage medical equipment through equipment information.

[0003] However, in large medical facilities such as hospitals, medical equipment is usually deployed in multiple departments and wards, with large quantities and types, making management more complicated. The current management method mainly involves manual collection of equipment information, which has low management efficiency and consumes a lot of manpower costs. Summary of the invention

[0004] In view of this, the present application provides a patient monitor and a device information management method thereof, which replaces the manual collection of device information and realizes automated centralized management of device management information, so as to save manpower management costs and improve management efficiency.

[0005] In a first aspect, an embodiment of the present application provides a patient monitor, wherein the patient monitor is communicatively connected to at least one medical device and a device management server, and the patient monitor includes:

[0006] Parameter sensor accessories, used to collect physiological parameter signals of the monitored object in real time;

[0007] A processor, configured to obtain the physiological parameter signal from the parameter sensor attachment and process the physiological parameter signal to obtain corresponding physiological parameter data;

[0008] A communication interface is used to obtain device management information of the medical device from the medical device and send the device management information to the device management server.

[0009] In a second aspect, an embodiment of the present application provides a patient monitor, wherein the patient monitor is communicatively connected to at least one medical device and a device management server, and each of the medical devices establishes a data transmission channel with the patient monitor; the patient monitor comprises:

[0010] Parameter sensor accessories, used to collect physiological parameter signals of the monitored object in real time;

[0011] A processor, configured to obtain the physiological parameter signal from the parameter sensor attachment and process the physiological parameter signal to obtain corresponding physiological parameter data;

[0012] A communication interface is used to obtain the physiological parameter data collected by the medical device through the data transmission channel between the medical device; to obtain the device management information of the medical device through the data transmission channel between the medical device; and to send the device management information to the device management server.

[0013] In a third aspect, an embodiment of the present application provides a device management server that is communicatively connected to at least one patient monitor and a device management client provided in the first aspect, the device management server comprising:

[0014] A communication interface, used to obtain device management information of at least one medical device and send the device management information to a memory;

[0015] A memory, used to store the device management information;

[0016] A processor is used to receive a device management request sent by a device management client; use a data processing method corresponding to the device management request to process the device management information to obtain an information processing result, and return the information processing result to the device management client so that the device management client can display the information processing result.

[0017] In a fourth aspect, an embodiment of the present application provides a device management server, the device management server is communicatively connected to at least one patient monitor provided in the first aspect, and the device management server includes:

[0018] A communication interface, used to obtain device management information of at least one medical device and send the device management information to a memory;

[0019] A memory, used to store the device management information;

[0020] A processor, configured to determine a management service to be provided by the device management server; use a data processing method corresponding to the management service to process the device management information to obtain an information processing result, and send the information processing result to an output device;

[0021] An output device is used to output the information processing result.

[0022] In a fifth aspect, an embodiment of the present application provides a device information management method, which is applied to a patient monitor, wherein the patient monitor is communicatively connected with at least one medical device and a device management server, and the method includes:

[0023] Collect physiological parameter signals of the monitored object in real time;

[0024] identifying physiological parameter data from the physiological parameter signal;

[0025] obtaining device management information of at least one medical device communicatively connected to the patient monitor;

[0026] The device management information is sent to a device management server that is communicatively connected to the patient monitor.

[0027] In a sixth aspect, an embodiment of the present application provides a device information management method, which is applied to a device management server, wherein the device management server is communicatively connected with at least one patient monitor and a device management client provided in the first aspect, and the method comprises:

[0028] receiving device management information of at least one medical device and storing the device management information;

[0029] Receive a device management request sent by a device management client;

[0030] Using a data processing method corresponding to the device management request, processing the device management information to obtain an information processing result;

[0031] The information processing result is sent to the device management client.

[0032] In a seventh aspect, an embodiment of the present application provides a device information management method, which is applied to a device management server, wherein the device management server is communicatively connected with at least one patient monitor and a device management client provided in the first aspect, and the method comprises:

[0033] receiving device management information of at least one medical device and storing the device management information;

[0034] Determining the management service to be provided by the device management server;

[0035] Using a data processing method corresponding to the management service, the device management information is processed to obtain an information processing result;

[0036] The information processing result is outputted.

[0037] In an eighth aspect, an embodiment of the present application provides a readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the device information management method provided in any of the above aspects is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0039] Figure 1A-1B Schematic diagrams of two different networking of device management systems;

[0040] Figure 2 A flowchart of a device information management method is provided;

[0041] Figure 3 Another network diagram of the equipment management system;

[0042] Figure 4 is another flow chart of the device information management method;

[0043] Figures 5A-5D Schematic diagram of four application scenarios of the device management method;

[0044] Figure 6 A schematic diagram of the structure of a patient monitor. DETAILED DESCRIPTION

[0045] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0046] With the advancement of medical technology, the number of medical devices introduced in various medical facilities such as hospitals has gradually increased, and the medical services provided have become more and more comprehensive. There are many types of medical equipment and they are scattered in various departments and wards of hospitals. In order to facilitate the management of medical equipment, it is necessary to collect relevant information of medical equipment such as basic information of equipment hardware, equipment operating status, maintenance and upgrade information, etc. At present, the equipment information management solution for medical equipment usually adopts manual recording, that is, it is collected manually and stored separately. However, there are a large number of medical devices, and this traditional management method requires a lot of manpower costs, is prone to incomplete record information, and has low management efficiency.

[0047] In this regard, the present application provides a medical equipment management solution, which realizes unified management of various medical equipment by networking medical equipment, so as to reduce manual management costs and improve the efficiency of equipment management. Specifically, the present application provides a system architecture of multi-device networking, which is centered on the patient monitor, connects the bedside medical equipment to the patient monitor, collects the equipment management information of the bedside medical equipment through the patient monitor, and sends it to the equipment management server in a unified manner.

[0048] A specific architecture of a device management system is as follows: Figure 1A As shown, bedside medical devices such as infusion pumps, anesthesia machines, ventilators, and telemetry monitors are respectively connected to the patient monitor in communication, forming a bedside network centered on the patient monitor. The communication connection of the bedside network can include wired and wireless such as Bluetooth, serial port, etc., which is not specifically limited in this application. In addition, the patient monitor is connected to the device management server in communication via wired, wireless or other means. The network for the patient monitor to communicate with the device management server can be various types such as a central monitoring network and an Internet of Things network, which is not specifically limited in this application.

[0049] In this system architecture, each patient monitor is directly connected to the device management server, so each patient monitor needs to develop a communication protocol independently for data communication with the device management server. Different patient monitors may use different communication protocols, which requires a lot of development work.

[0050] Another specific device management system architecture is as follows Figure 1B As shown, bedside medical devices such as infusion pumps, anesthesia machines, ventilators, and telemetry monitors are respectively connected to the patient monitor to form a bedside network centered on the patient monitor. The patient monitor is connected to the central monitoring server, and the central monitoring server is connected to the device management server. The central monitoring server may include: a central monitoring station, a server of a clinical information system (CIS), a server of a hospital information system (HIS), or a server of an electronic medical record system (EMR).

[0051] Different from the above system architecture, in this architecture, the patient monitor communicates with the device management server through the central monitoring server. It should be noted that the patient monitor and the central monitoring server may have been connected to each other through the central monitoring network. The central monitoring network mainly transmits medical data related to the patient, such as basic information of the patient, physiological parameters of the patient, etc. In order to make full use of existing resources and reduce the difficulty of development and networking, a device management server can be added on the basis of the existing system architecture (i.e., the network architecture between the patient monitor and the central monitoring server), specifically, the central monitoring server and the device management server are connected to each other. The patient monitor can use the existing central monitoring network to send the device management information to the central monitoring server, which is then forwarded to the device management server by the central monitoring server. In this way, it is only necessary to develop the communication protocol between the central monitoring server and the device management server, thereby reducing the workload of development and networking.

[0052] It should be noted that the device interconnection method is not limited to the above two methods, and can also be any other method that can realize the communication connection between the patient monitor and the medical device and the device management server that can be expected by those skilled in the art. For example, in addition to being set as an independent server, the device management server can also be integrated into the central monitoring system, such as a central monitoring server integrated into the central monitoring system, which uses the same server as the central monitoring server. It should be noted that the central monitoring server is a server that realizes the monitoring function. The monitoring function can be realized mainly because the central monitoring server can receive the physiological parameter data sent by the patient monitor and process it to obtain the parameter processing results.

[0053] Based on any device interconnection solution, the present application embodiment provides a device information management method. Figure 2 As shown, the device information management method may specifically include steps S201-S206.

[0054] S201: The patient monitor collects physiological parameter signals of the monitored object in real time and identifies physiological parameter data from the physiological parameter signals.

[0055] Specifically, as a monitoring device, a patient monitor has a parameter sensor accessory for collecting physiological parameter signals of patients. Physiological parameter signals can be parameter information related to any physiological sign condition such as blood pressure, blood oxygen, respiration, heart rate, etc., and the embodiments of the present application are not specifically limited. The patient monitor can process the physiological parameter signal to obtain the corresponding physiological parameter data. The physiological parameter data can be stored or displayed locally on the patient monitor, and can also be further sent to the central monitoring server for storage or other processing operations.

[0056] It should be noted that the patient monitor can perform the monitoring process according to the existing monitoring plan, and the embodiment of the present application does not limit the specific implementation method of the monitoring process. In the application scenario of the embodiment of the present application, the patient monitor expands the function of collecting device management information based on the existing monitoring function.

[0057] S202: The medical device obtains device management information.

[0058] Specifically, the medical device can obtain the device management information locally and then send the device management information to the patient monitor. The medical device can send the device management information in the following ways, but not limited to:

[0059] In one implementation, the medical device may obtain the device management information regularly according to a preset period and send the device management information to the patient monitor. The preset period may be set according to actual needs.

[0060] In another embodiment, the device operator can input an upload instruction to the medical device through the human-computer interaction interface, and the medical device obtains the device management information in response to the upload instruction and sends the device management information to the patient monitor.

[0061] In another embodiment, when the medical device detects a preset condition, the device management information is obtained and sent to the patient monitor. For example, the medical device is a pluggable medical accessory, such as a pluggable monitor (such as a transport monitor, a monitor parameter measurement module, etc.), which can be used as an independent bedside monitor or as a pluggable medical accessory connected to a patient monitor; when the medical device detects that it is connected to a patient monitor and / or unplugged from a patient monitor, the device management information of the pluggable medical accessory is obtained and sent to the patient monitor. For another example, when the medical device detects a device failure, the device management information is obtained and sent to the patient monitor.

[0062] In another embodiment, the medical device receives an information acquisition request sent by the patient monitor, obtains corresponding device management information according to the information acquisition request, and sends the obtained device management information to the patient monitor. The information acquisition request may be generated by the patient monitor, or may be generated by other devices such as a device management server and sent to the patient monitor, that is, the patient monitor may forward the information acquisition request to the medical device.

[0063] In summary, in the first three implementations, the medical device actively uploads device management information to the patient monitor, while in the fourth implementation, the medical device returns device management information based on the request of the patient monitor.

[0064] Equipment management information is used to describe the operation or maintenance status of the equipment, and may also be called equipment operation and maintenance information. It may specifically include: any one or more of equipment configuration information, equipment location information, equipment maintenance information, equipment usage information, equipment accessory information, and equipment alarm information.

[0065] Among them, the equipment configuration information is used to indicate the basic situation of the equipment's software and hardware, and may include basic equipment information, such as type, name, serial number, software version, hardware version, etc.; it may also include equipment board information, such as board serial number, production date, batch, software and hardware version, etc. The equipment location information is used to indicate the location of the equipment, and may specifically include: bed number, room number, department, floor, hospital name, etc. The equipment maintenance information is used to indicate the maintenance of the equipment, and may specifically include maintenance time, maintenance type, maintenance content, next maintenance time, maintenance reminder information, upgrade information, calibration information, etc. The equipment usage information is used to indicate the use of the equipment, and may specifically include power-on time, power-off time, running time, equipment status, processor usage rate, equipment failure rate, equipment borrowing information, etc. The equipment accessory information is used to indicate the basic situation of the accessories included in the equipment, and may specifically include accessory version, serial number, batch, usage time, status, number of replacements, battery information, etc. The equipment alarm information is used to indicate abnormal alarms that occur during the operation of the equipment, such as alarms when the display shows abnormalities, and alarms when the equipment is moved out of the preset use range such as a department. In order to distinguish it from the physiological alarm generated based on the abnormal condition of the patient, this type of alarm can be called a technical alarm, which may specifically include the alarm time, alarm content, alarm type, etc.

[0066] S203: The medical device sends device management information to the patient monitor.

[0067] Specifically, the medical device sends any one or more types of the above-mentioned device management information through a communication connection with the patient monitor.

[0068] S204: The patient monitor performs a preset processing operation on the device management information.

[0069] Specifically, the preset processing operations may include: adding a medical device identifier to the device management information to indicate which medical device the device management information comes from, and / or adding a time tag to the device management information to indicate the collection time of the device management information. The processing operation mainly adds some auxiliary information so that the device management server can clarify the basic situation of the device management information. Of course, the processing operation is not limited to the above two, and other operations that can be expected by technicians in this field can also be performed.

[0070] It should be noted that the processing operation of the patient monitor on the device management information is not limited to being performed after the physiological parameter data is obtained in step S201, and it can be performed simultaneously with the step of obtaining the physiological parameter data, separately or before it.

[0071] S205: The patient monitor sends the device management information after executing the preset processing operation to the device management server.

[0072] It should be noted that the patient monitor may not perform the above processing operation on the device management information, but directly forward the originally received device management information to the device management server.

[0073] The patient monitor may be connected to one or more medical devices. If there are multiple medical devices, after receiving the device management information of each medical device, the patient monitor may aggregate the device management information and send it together; or may send the device management information of each medical device separately.

[0074] In another embodiment, a step may be added: the patient monitor obtains its own device management information and sends its own device management information to the device management server. In this way, the patient monitor not only sends the collected device management information of the bedside medical device, but also sends its own device management information. It should be noted that in this case, the device management information received by the device management server includes not only the device management information of the bedside medical device, but also the device management information of the patient monitor. Since the patient monitor is also a medical device, these device management information can be collectively referred to as the device management information of the medical device.

[0075] S206: The device management server saves the device management information.

[0076] Specifically, the device management server stores the device management information locally on the server. On the one hand, the device management information can be stored in a memory unit so that the processor can provide device management services based on the device management information; or on the other hand, the device management information can be stored in a non-volatile storage unit and read from the non-volatile storage unit when the device management information is needed.

[0077] It can be seen from the above technical solution that an embodiment of the present application provides a device information management method, which is applied to a device information management system, wherein the device management system includes at least one medical device, a patient monitor connected to the medical device for communication, and a device management server connected to the patient monitor for communication; the patient monitor obtains the device management information of the medical device through the bedside network, and sends the device management information to the device management server, thereby realizing automatic online collection of device management information with the patient monitor as the core, saving the cost of manual recording and having high information management efficiency.

[0078] It should be noted that, based on the above description, the patient monitor can be connected to one or more medical devices for communication, and each medical device (including the case of one medical device) has a data transmission channel established with the patient monitor for mutual data transmission. Through this data transmission channel, the patient monitor can not only obtain the physiological parameter data collected by the medical device, but also obtain the device management information of the medical device. In other words, the data transmission channel between the patient monitor and the medical device can be reused. When the medical device needs to interact with the device management information, such as uploading the device management information to the device management server or obtaining the maintenance service information returned by the device management server, the data transmission channel for transmitting medical data can be directly used, and there is no need to set up an additional data transmission network between a single medical device and the device management server.

[0079] Furthermore, the central monitoring server can be reused with the device management server, that is, the two are integrated into one device or a service cluster composed of multiple devices. In this case, it can be considered that the device management server is the central monitoring server, and the physiological parameter data and device management information obtained by the patient monitor can be uploaded to the central monitoring server through the data transmission channel between the patient monitor and the central monitoring server, realizing the reuse of the data transmission channel between the patient monitor and the central monitoring server, thereby saving the cost of setting up the transmission network.

[0080] In another case, the central monitoring server and the device management server are separately deployed devices or device clusters. A data transmission channel is established between the patient monitor and the central monitoring server, which is mainly used to transmit physiological parameter data; a data transmission channel is also established between the patient monitor and the device management server, which is mainly used to transmit device management information. Therefore, the physiological parameter data obtained by the patient monitor and the collected device management information are sent to two different devices or device clusters through two data transmission channels.

[0081] Another situation is that the central monitoring server and the device management server are separately deployed devices or device clusters. The data transmission channel established between the patient monitor and the central monitoring server can be used to transmit physiological parameter data and can also be reused to transmit device management information. In this way, the patient monitor can send both physiological parameter data and device management information to the central monitoring server through the data transmission channel. A data transmission channel is established between the central monitoring server and the device management server. Since the device management server is the server that implements device information management, the central monitoring server then sends the device management information to the device management server through this data transmission channel. It can be seen that in this case, the existing data transmission channel between the patient monitoring device and the central monitoring server can be used as part of the transmission path for the device management information from the patient monitoring device to the device management server, thereby saving the network construction cost to a certain extent.

[0082] In addition to storing device management information, the device management server can also display device management information, for example, the basic information of the device, such as the serial number, production date, software and hardware version of the device board, etc., is generated into an information list for display, and the alarm information of the device is generated into an alarm list for display, etc. Alternatively, the device management information is further used to execute the device management process to provide the required device management services to the user. The device management service may include but is not limited to: information query, maintenance reminder, upgrade reminder, location alarm, etc. Specifically, the device management server can process the device management information of one or more medical devices to obtain maintenance service information. It should be noted that the requirements for device management in different application scenarios are different, and the data processing methods are also different, so the maintenance service information obtained may also be different. The specific generation process of the maintenance service information can be referred to the detailed description below. The device management server returns the maintenance service information to the patient monitor, and the patient monitor further returns the maintenance service information to the one or more medical devices. It can be seen that the patient monitor, as a transit device, can not only upload the device management information of the medical device to the device management server, but also transmit the maintenance service information generated by the device management server back to the medical device.

[0083] In order to provide equipment management services, the present application embodiment provides a medical equipment management system, such as Figure 3 As shown, the system includes a device management server, a patient monitor, and a device management client. The patient monitor can be the patient monitor shown in any of the above embodiments, and the patient monitor establishes a communication connection with at least one bedside medical device and the device management server. It should be noted that other descriptions of the patient monitor can refer to the above description and are not repeated here.

[0084] exist Figure 1A and Figure 1B Based on the medical device management system shown, the embodiment of the present application adds a device management client that is connected to the device management server. The device management client can be in various forms such as a desktop computer, a laptop computer, a tablet computer, a mobile phone, a personal digital assistant (PDA), etc. The device management client realizes the communication connection with the device management server by installing an application specifically used to realize device management or other applications integrated with device management functions. For example, the device management client can install a monitoring application, and the device management module can be integrated in the application to realize the device management function.

[0085] Relying on the above-mentioned medical device management system, the present application embodiment provides another device information management method. Figure 4 As shown, the device information management method may specifically include steps S401-S406.

[0086] S401: The patient monitor sends device management information of at least one medical device to a device management server.

[0087] It should be noted that in addition to uploading the device management information of medical devices, the patient monitor can also upload its own device management information. The two types of device management information can be sent together or separately, and this application does not make specific restrictions. In addition, the patient monitor can directly send the device management information to the device management server, or the patient monitor can forward the device management information to the device management server through the central monitoring server.

[0088] S402: The device management server stores the device management information.

[0089] S403: The device management client sends a device management request to the device management server.

[0090] Specifically, the device management client can provide a human-computer interaction interface, through which the user inputs a trigger operation, and the device management server generates a device management request based on the trigger operation. This situation reflects the user's management needs for medical devices. Of course, in actual applications, if the device management client needs to manage the medical device during operation, it can also automatically generate a device management request.

[0091] S404: The device management server processes the device management information using a data processing method corresponding to the device management request to obtain an information processing result.

[0092] The device management request is to request the device management server to provide the required device management services. Device management services are roughly divided into several categories, such as information viewing services, alarm prompt services, upgrade and maintenance services, etc.

[0093] After receiving the device management request, the device management server uses the data processing method corresponding to the device management request to process the pre-stored device management information, thereby obtaining the information processing result corresponding to the device management request. It should be noted that the correspondence between the device management request and the data processing method can be pre-set, so that after receiving the device management request, the data processing method is determined according to the correspondence. The data processing method can be considered as a functional module written by program code. Different functional modules encapsulate different data processing methods represented by program codes. Running the program code can realize the device management service provided by the functional module.

[0094] The following describes the specific implementation process of the device management service in combination with different application scenarios.

[0095] Application scenario 1: The device management client requests to view device management information.

[0096] When a user wants to view device management information, the device management client can be triggered to generate a device management information viewing request. Figure 5A As shown, the device management client sends a device management information viewing request to the device management server. The device management information viewing request may include the identifier of the target device you want to view, such as the room number, bed number or name of the device. If the request does not include the identifier of the target device, it is assumed that the request is to view the device management information of all devices. After receiving the request, the device management server sets all devices as target devices by default. First, the device management server searches for the device management information corresponding to the device management information viewing request in the stored device management information. For example, the device management information has an association relationship with the device identifier. The device management server searches for the device management information associated with the target device identifier based on the target device identifier in the device management information viewing request. For the sake of description, the found device management information can be referred to as the target device management information. Then, the device management server sends the target device management information as the information processing result to the management client for display.

[0097] In one embodiment, the device management information viewing request includes a device location information viewing request. The process of the device management server searching for the target device management information specifically includes: determining the target medical device corresponding to the device location information viewing request, the target medical device may include a bedside medical device or a patient monitor; searching for the location information of the target medical device in the device management information, the location information includes a real-time location and / or a historical location. The same target medical device may have been used in multiple locations, such as a ventilator being transferred from a bedside to an operating room, so the historical location represents the location information of the target medical device when it was previously used.

[0098] It should be noted that when storing device management information, the device management server can generate an information item of the historical location. If the device management information uploaded by the patient monitor carries an information value related to the historical location, the information value is stored in the information item for preservation. For example, the device management information uploaded by the patient monitor may include a loan location, and the loan location can be saved in the information item of the historical location. Of course, the specific form of the information value can also be other forms that can be expected by those skilled in the art, and this application does not make any specific limitations.

[0099] In another embodiment, the device management information viewing request includes a device maintenance information viewing request. Then the process of the device management server searching for the target device management information specifically includes: determining the target medical device corresponding to the device maintenance information viewing request; searching for the maintenance information of the target medical device in the device management information, the maintenance information including any one or more of the maintenance time, maintenance type, maintenance content, next maintenance time, maintenance reminder information, upgrade information, and calibration information. The specific implementation method can refer to the previous implementation method and will not be repeated here. For easy viewing, the maintenance information can be included in the list. By viewing the maintenance information, the user can clearly understand the maintenance status of the target medical device.

[0100] In another embodiment, the device management information viewing request includes a device configuration information viewing request. Then the process of the device management server searching for the target device management information specifically includes: determining the target medical device corresponding to the device configuration information viewing request; searching for the configuration information of the target medical device in the device management information, the configuration information including any one or more of the type, name, serial number, board information, software version, and hardware version. The specific implementation method can refer to the first embodiment and will not be repeated here. For easy viewing, maintenance information can be included in the list. By viewing the configuration information, the user can clearly understand the configuration of the target medical device.

[0101] In another embodiment, the device management information viewing request includes a device usage information viewing request. Then the process of the device management server searching for the target device management information specifically includes: determining the target medical device corresponding to the device usage information viewing request; searching for the usage information of the target medical device in the device management information, and the usage information includes any one or more of the boot time, shutdown time, usage status, processor usage rate, failure rate, and borrowing information. The specific implementation method can refer to the first embodiment and is not repeated here. For easy viewing, the usage information can be included in the list. By viewing the usage information, the user can clearly understand the usage of the target medical device.

[0102] In another embodiment, the device management information viewing request includes a device attachment information viewing request. The process of the device management server searching for the target device management information specifically includes: determining the target medical device corresponding to the device attachment information viewing request; searching for the attachment information of the target medical device in the device management information, the attachment information including any one or more of the version, serial number, batch, usage time, status, number of replacements, and battery information. The specific implementation method can refer to the first embodiment and will not be repeated here. For easy viewing, the attachment information can be included in the list. By viewing the attachment information, the user can clarify the basic situation of each medical attachment.

[0103] In another embodiment, the device management information viewing request includes a device alarm information viewing request. Then the process of the device management server searching for the target device management information specifically includes: determining the target medical device corresponding to the device attachment information viewing request; searching for the alarm information of the target medical device in the device management information. The specific implementation method can refer to the first embodiment, which is not repeated here. For easy viewing, the alarm information can be included in the list. By viewing the alarm information, the user can clearly understand the alarm conditions of each medical device due to abnormal operation.

[0104] In another embodiment, the device management information viewing request includes a device usage viewing request. The process of the device management server searching for the target device management information specifically includes: determining the target medical device corresponding to the device usage viewing request; obtaining the device usage of the target medical device in the device management information, and marking the target device usage that exceeds the preset usage threshold to obtain the information processing result. The specific implementation method can refer to the first embodiment and is not described here. For easy viewing, the device usage rate can be included in the list. By viewing the device usage rate, the user can clearly know whether each medical device is frequently used.

[0105] Exemplarily, the device usage rate indicates the number of times the device is used within a certain period of time. The device usage rate can be calculated by the device management server after receiving the device management information uploaded by the patient monitor, and the device usage rate is stored as an information item. Alternatively, it can be calculated based on the read device management information after the device management server receives the request to view the device usage information. If multiple target medical devices are determined, the target medical devices whose device usage rate reaches a certain threshold can also be marked to remind relevant personnel that the usage rate of such medical devices is high.

[0106] It should be noted that the device management information viewing request may also be in other forms, which are not specifically limited in this application. As long as the information is obtainable based on the device management information stored in the device management server, it is within the protection scope of the embodiments of this application.

[0107] Application scenario 2: The device management server sends a device maintenance reminder message to the device management client to remind relevant personnel to perform regular maintenance on the device.

[0108] like Figure 5B As shown, the device management information uploaded by the patient monitor may include device maintenance information. The device management client may send a maintenance information viewing request to the device management server, and the device management server determines the maintenance plan of the medical device based on the device maintenance information, and the maintenance plan includes the next maintenance time. Exemplarily, the device maintenance information includes the time point of the most recent maintenance. The device management server can calculate the next maintenance time based on the time point of the most recent maintenance and the preset device maintenance cycle. Furthermore, the device management server generates a maintenance reminder message for the next maintenance time and sends it to the device management client to remind relevant personnel to maintain the medical device.

[0109] It should be noted that the maintenance reminder message may be sent at a certain time point before the next maintenance time arrives. For example, the maintenance reminder message is sent to the device management client of the maintenance personnel one day before the next maintenance time arrives.

[0110] If there are multiple medical devices that need maintenance, the device management server can count the medical devices whose next maintenance time is within the same time range according to the maintenance plan of each medical device, such as the medical devices whose next maintenance time is on the same day, and mark these medical devices for prompting.

[0111] Application scenario three: The device management server sends upgrade reminder messages to medical devices to achieve automatic upgrade of medical devices.

[0112] like Figure 5CAs shown, the device management information uploaded by the patient monitor may include device upgrade information. The device management client may send a request to view the upgrade information to the device management server, and the device management server determines the next upgrade time of the medical device based on the device upgrade information. Exemplarily, the device upgrade information includes the time point of the most recent upgrade, and the device management server can calculate the next upgrade time based on the time point of the most recent upgrade and the preset device upgrade cycle; or, the device upgrade information includes the current version information of the medical device, and the device management server can determine the latest version information developed for the medical device. If the two version information are inconsistent, it means that the medical device needs to be upgraded, thereby determining that the next upgrade time of the medical device is the current time point or a time point after a preset time length. Furthermore, the device management server generates an upgrade reminder message for the next upgrade time and sends it to the medical device to remind the medical device to automatically upgrade.

[0113] Application scenario 4: The device management server sends an alarm message to the device management client to prompt that the location of the medical device has changed.

[0114] like Figure 5D As shown, the device management information uploaded by the patient monitor may include location information. The device management server obtains the location restriction alarm condition of the medical device, and generates an alarm message when the location information of the medical device meets the location restriction alarm condition. The location restriction alarm condition refers to the preset use range for the medical device. If the location information of the medical device exceeds the location use range, an alarm is required. For example, if a patient monitor is only allowed to be used in a specific ward, the ward can be set as the preset use range in the location restriction alarm condition. When the location information uploaded by the patient monitor, i.e. the current location, exceeds the ward, an alarm message is generated. The device management server sends the alarm message to the device management client to prompt relevant personnel of the abnormal location of the medical device.

[0115] S405: The device management server sends the information processing result to the device management client.

[0116] Wherein, no matter which of the above data processing methods is used, after obtaining the information processing result, the device management server sends the information processing result to the device management client for display by the device management client. It should be noted that the information processing result can also be called maintenance service information.

[0117] S406: The device management client displays the information processing result.

[0118] It can be seen from the above technical solutions that the embodiment of the present application provides a device information management method. The device management server can generate data processing results based on the device management information in accordance with the preset data processing method. The data processing results can be considered as the device management services provided by the device management server, such as device information viewing, device maintenance reminders, device upgrade reminders, device location alarms, etc. It can be seen that the embodiment of the present application can not only realize the unified collection of device management information, but also use the collected device management information to provide users with various device management services to meet users' various management needs for devices.

[0119] In actual applications, medical care sites may have already managed all or part of the medical equipment through the Internet of Things and other solutions. The device information management solution provided in the embodiment of the present application can be used as a supplement to the Internet of Things solution. In order to save the cost of all equipment for Internet of Things transformation, the device management server can be connected to the third-party Internet of Things device management system through the Simple Network Management Protocol (SNMP) and MQTT (Message Queuing Telemetry Transport) to collect the device management information of medical equipment. Alternatively, the device management server sends the device management information to the server in the Internet of Things device management system so that the server stores the device management information.

[0120] It should be noted that application scenarios 2, 3 and 4 are not limited to processing device management information based on device management requests from device management clients, but can also be automatically processed by the device management server according to management requirements.

[0121] Specifically, the device management server receives device management information of at least one medical device and stores the device management information; determines the management service to be provided by the device management server, such as device upgrade reminder service, device maintenance reminder service, device location alarm service, etc.; uses the data processing method corresponding to the management service to process the device management information to obtain the information processing result; and outputs the information processing result. The specific implementation method of each management service can refer to the above description and is not repeated here.

[0122] A specific example of a patient monitoring device is Figure 6 shown. Figure 6 A system framework diagram of a parameter processing module in a multi-parameter monitor is provided.

[0123] The multi-parameter monitor has an independent shell, and a sensor interface area is provided on the shell panel, in which a plurality of sensor interfaces are integrated, which are used to connect with external physiological sign parameter sensor accessories 611. The shell panel also includes a small LCD display area, a display 618, an input interface circuit 620 and an alarm circuit 619 (such as an LED alarm area), etc. The parameter processing module is used for external communication and power supply interfaces for communicating with the host and taking power from the host. The parameter processing module also supports an external parameter module, and a plug-in monitor host can be formed by inserting the parameter module. As a part of the monitor, it can also be connected to the host through a cable, and the external parameter module is an external accessory of the monitor. In addition, the multi-parameter monitor includes a memory 617, which is used to store computer programs and various data generated during the related monitoring process.

[0124] The internal circuit of the parameter processing module is placed in the housing, such as Figure 6 As shown, it includes a signal acquisition circuit 612 corresponding to at least two physiological sign parameters, a front-end signal processing circuit 613 and a main processor 615.

[0125] The main processor 615 can implement each of the processing-related steps in the above-mentioned apnea event monitoring methods.

[0126] The signal acquisition circuit 612 can be selected from an electrocardiogram circuit, a respiratory circuit, a body temperature circuit, a blood oxygen circuit, a non-invasive blood pressure circuit, an invasive blood pressure circuit, etc. These signal acquisition circuits 612 are electrically connected to corresponding sensor interfaces, respectively, and are used to be electrically connected to sensor accessories 611 corresponding to different physiological sign parameters. The output end is coupled to the front-end signal processor, and the communication port of the front-end signal processor is coupled to the main processor, and the main processor is electrically connected to the external communication and power supply interface.

[0127] Various physiological sign parameter measurement circuits can adopt general circuits in the existing technology. The front-end signal processor completes the sampling and analog-to-digital conversion of the output signal of the signal acquisition circuit, and outputs a control signal to control the measurement process of the physiological signal. These parameters include but are not limited to: electrocardiogram, respiration, body temperature, blood oxygen, non-invasive blood pressure and invasive blood pressure parameters.

[0128] The front-end signal processor can be implemented by a single-chip microcomputer or other semiconductor devices, or by an ASIC or FPGA. The front-end signal processor can be powered by an isolated power supply, and the sampled data is simply processed and packaged, and then sent to the main processor through the isolated communication interface. For example, the front-end signal processor circuit can be coupled to the main processor 615 through the isolated power supply and the communication interface 614.

[0129] The reason why the front-end signal processor is powered by an isolated power supply is that the DC / DC power supply isolated by a transformer plays the role of isolating the patient from the power supply equipment. The main purposes are: 1. Isolate the patient. Through the isolation transformer, the application part is floated to make the patient leakage current small enough; 2. Prevent the voltage or energy during the application of defibrillation or electric knife from affecting the boards and devices of the intermediate circuit such as the main control board (guaranteed by creepage distance and electrical clearance).

[0130] The main processor completes the calculation of the physiological sign parameters, and sends the calculation results and waveforms of the parameters to the host (such as a host with a display, a PC, a central station, etc.) through the external communication and power supply interface. The external communication and power supply interface 616 can be one or a combination of the local area network interfaces composed of Ethernet, Token Ring, Token Bus, and the fiber distributed data interface (FDDI) as the backbone network of these three networks. It can also be one or a combination of wireless interfaces such as infrared, Bluetooth, wifi, WMTS communication, etc., or it can also be one or a combination of wired data connection interfaces such as RS232 and USB.

[0131] The external communication and power interface 616 can also be one or a combination of a wireless data transmission interface and a wired data transmission interface. The host can be any computer device such as the host of a monitor, an electrocardiograph, an ultrasonic diagnostic instrument, a computer, etc., and a monitoring device can be formed by installing the corresponding software. The host can also be a communication device, such as a mobile phone. The parameter processing module sends data to a mobile phone that supports Bluetooth communication through a Bluetooth interface to realize remote transmission of data.

[0132] In addition, the present application provides a readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the various device information management methods described above are implemented.

[0133] It should be noted that the various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0134] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "including one..." do not exclude the presence of other identical elements in the process, method, article or device including the above elements.

[0135] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A patient monitor, characterized in that: The patient monitor is communicatively connected with at least one medical device to form a bedside network centered on the patient monitor, and the patient monitor is communicatively connected with a device management server, and the patient monitor includes: Parameter sensor accessories, used to collect physiological parameter signals of the monitored object in real time; A processor, configured to obtain the physiological parameter signal from the parameter sensor attachment and process the physiological parameter signal to obtain corresponding physiological parameter data; A communication interface is used to obtain device management information of the medical device from the medical device, wherein the device management information includes any one or more of device configuration information, device location information, device maintenance information, device usage information, device accessory information, and device technical alarm information, and send the device management information to the device management server.

2. The patient monitor according to claim 1, characterized in that: When sending the device management information to the device management server, the communication interface is specifically used to: Based on the communication protocol corresponding to the patient monitor and the device management server, the device management information is sent to the device management server which is in communication connection with the patient monitor; different patient monitors have different communication protocols with the device management servers.

3. The patient monitor according to claim 1, characterized in that: The patient monitor is also connected to a central monitoring server through the communication interface, and the central monitoring server is connected to the device management server based on a specific communication protocol; when sending the device management information to the device management server, the communication interface is specifically used to: The device management information is sent to the central monitoring server, so that the central monitoring server sends the device management information to the device management server based on a communication protocol corresponding to the device management server.

4. The patient monitor according to claim 1, characterized in that: When acquiring the device management information of the medical device from the medical device, the communication interface is specifically used for: receiving device management information uploaded by at least one medical device in communication connection with the patient monitor; and / or, An information acquisition request is sent to at least one medical device that is communicatively connected to the patient monitor, and device management information corresponding to the information acquisition request is received and returned by the medical device.

5. The patient monitor according to claim 1, characterized in that: The medical device includes a pluggable medical accessory, and when obtaining device management information of the medical device from the medical device, the communication interface is specifically used to: When a pluggable medical accessory is connected to and / or unplugged from the patient monitor, device management information of the pluggable medical accessory is obtained.

6. The patient monitor according to claim 1, characterized in that: The device configuration information includes at least one of device type, device name, software version, hardware version, and device board information; the device location information includes at least one of bed number, room number, department, floor, and hospital name; the device maintenance information includes at least one of maintenance time, maintenance type, maintenance content, next maintenance time, maintenance reminder information, upgrade information, and calibration information; the device usage information includes at least one of power-on time, power-off time, running time, device status, processor usage rate, device failure rate, and device borrowing information; the device accessory information includes at least one of accessory version, serial number, batch, usage time, status, number of replacements, and battery information; the device technical alarm information includes any one or more of display abnormality and device being moved out of the preset range of use.

7. The patient monitor according to claim 1, characterized in that: The communication interface is also used to send the device management information of the patient monitor itself to the device management server.

8. The patient monitor according to claim 1, characterized in that: The device management server is a central monitoring server, wherein the central monitoring server receives the physiological parameter data sent by the patient monitor and processes it to obtain parameter processing results, and receives the device management information of the medical device sent by the patient monitor and stores it.

9. The patient monitor according to claim 1, characterized in that: The processor is further configured to: Receive maintenance service information returned by the device management server, where the maintenance service information is obtained after processing device management information of one or more medical devices; and return the maintenance service information to the corresponding medical device.

10. A patient monitor, characterized in that: The patient monitor is communicatively connected with at least one medical device to form a bedside network centered on the patient monitor, and the patient monitor is communicatively connected with a device management server, and each of the medical devices establishes a data transmission channel with the patient monitor respectively; The patient monitor comprises: Parameter sensor accessories, used to collect physiological parameter signals of the monitored object in real time; A processor, configured to obtain the physiological parameter signal from the parameter sensor attachment and process the physiological parameter signal to obtain corresponding physiological parameter data; A communication interface, used to obtain the physiological parameter data collected by the medical device through the data transmission channel between the medical device; obtain the equipment management information of the medical device through the data transmission channel between the medical device, the equipment management information including any one or more of equipment configuration information, equipment location information, equipment maintenance information, equipment usage information, equipment accessory information, and equipment technical alarm information; and send the equipment management information to the equipment management server.

11. The patient monitor according to claim 10, characterized in that: The processor is further configured to: Sending the physiological parameter data to a central monitoring server via a data transmission channel between the patient monitor and the central monitoring server; and In the case where the device management server is a central monitoring server, the device management information is sent to the central monitoring server through a data transmission channel between the device management server and the central monitoring server.

12. The patient monitor according to claim 10, characterized in that: The processor is further configured to: Sending the physiological parameter data to a central monitoring server via a data transmission channel between the patient monitor and the central monitoring server; and In the case that the device management server is not a central monitoring server, the device management information is sent to the device management server through a data transmission channel between the patient monitor and the device management server.

13. The patient monitor according to claim 10, characterized in that: The processor is further configured to: Sending the physiological parameter data to a central monitoring server via a data transmission channel between the patient monitor and the central monitoring server; and In the case that the device management server is not a central monitoring server, the device management information is sent to the central monitoring server through the data transmission channel between the patient monitor and the central monitoring server, so that the central monitoring server sends the device management information to the device management server through the data transmission channel between the central monitoring server and the device management server.

14. A device management server, characterized in that: The device management server is communicatively connected with at least one patient monitor and a device management client according to any one of claims 1 to 13, and the device management server comprises: A communication interface, used to obtain device management information of at least one medical device, the device management information including any one or more of device configuration information, device location information, device maintenance information, device usage information, device accessory information, and device technical alarm information, and send the device management information to a memory; A memory, used to store the device management information; A processor is used to receive a device management request sent by a device management client; use a data processing method corresponding to the device management request to process the device management information to obtain an information processing result, and return the information processing result to the device management client so that the device management client can display the information processing result.

15. The device management server according to claim 14, characterized in that: The device management request includes a device management information viewing request; When the device management information is processed using a data processing method corresponding to the device management request to obtain an information processing result, the processor is specifically configured to: In the device management information, the target device management information corresponding to the device management information viewing request is searched, and the target device management information is sent as an information processing result to the management client for display.

16. The device management server according to claim 15, characterized in that: The device management information viewing request includes a device location information viewing request; When searching the device management information for target device management information corresponding to the device management information viewing request, the processor is specifically configured to: Determine a target medical device corresponding to the device location information viewing request; The location information of the target medical device is searched in the device management information, where the location information includes a real-time location and / or a historical location.

17. The device management server according to claim 15, characterized in that: The device management information viewing request includes a device maintenance information viewing request; When searching the device management information for the target device management information corresponding to the device management information viewing request, the processor is specifically configured to: Determine the target medical device corresponding to the device maintenance information viewing request; The maintenance information of the target medical device is searched in the device management information, wherein the maintenance information includes any one or more of maintenance time, maintenance type, maintenance content, next maintenance time, maintenance reminder information, upgrade information, and calibration information.

18. The device management server according to claim 15, characterized in that: The device management information viewing request includes a device configuration information viewing request; When searching the device management information for the target device management information corresponding to the device management information viewing request, the processor is specifically configured to: Determine the target medical device corresponding to the device configuration information viewing request; The configuration information of the target medical device is searched in the device management information, where the configuration information includes any one or more of the type, name, serial number, board information, software version, and hardware version.

19. The device management server according to claim 15, characterized in that: The device management information viewing request includes a device usage information viewing request; When searching the device management information for the target device management information corresponding to the device management information viewing request, the processor is specifically configured to: Determine a target medical device corresponding to the device usage information viewing request; The usage information of the target medical device is searched in the device management information, where the usage information includes any one or more of the startup time, shutdown time, usage status, processor usage rate, failure rate, and borrowing information.

20. The device management server according to claim 15, characterized in that: The device management information viewing request includes a device attachment information viewing request; When searching the device management information for the target device management information corresponding to the device management information viewing request, the processor is specifically configured to: Determine the target medical device corresponding to the device attachment information viewing request; Search the device management information for the attachment information of the target medical device, where the attachment information includes any one or more of version, serial number, batch, usage time, status, number of replacements, and battery information.

21. The device management server according to claim 15, characterized in that: The device management information viewing request includes a device alarm information viewing request; When searching the device management information for the target device management information corresponding to the device management information viewing request, the processor is specifically configured to: Determine the target medical device corresponding to the device attachment information viewing request; Search the device management information for alarm information of the target medical device.

22. The device management server according to claim 15, characterized in that: The device management request includes a device usage rate viewing request; When the device management information is processed using a data processing method corresponding to the device management request to obtain an information processing result, the processor is specifically configured to: Determine a target medical device corresponding to the device usage viewing request; The device usage rate of the target medical device is obtained from the device management information, and the target device usage rate that exceeds a preset usage rate threshold is marked to obtain an information processing result.

23. The device management server according to claim 14, characterized in that: The device management information includes device maintenance information; The processor is also used to determine the maintenance plan of the medical device based on the equipment maintenance information of the medical device, and the maintenance plan includes the next maintenance time; and generate a maintenance reminder message based on the next maintenance time, and send the maintenance reminder message to the equipment management client through the communication interface.

24. The device management server according to claim 14, characterized in that: The device management information includes device upgrade information; The processor is also used to determine the next upgrade time of the medical device based on the device upgrade information of the medical device; generate an upgrade reminder message based on the next upgrade time, and send the upgrade reminder message to the medical device through the communication interface.

25. The device management server according to claim 14, characterized in that: The device management information includes location information; The processor is also used to generate alarm information when the location information of the medical device meets the location restriction alarm condition of the medical device, and send the alarm information to the device management client through the communication interface.

26. The device management server according to claim 14, characterized in that: The device management server is in communication connection with the patient monitor, and when receiving device management information of at least one medical device, the communication interface is specifically used to: receive device management information of at least one medical device sent by the patient monitor; or The device management server is communicatively connected to the patient monitor via a central monitoring server. When receiving device management information of at least one medical device, the communication interface is specifically used to: receive the device management information sent by the central monitoring server, wherein the device management information of the central monitoring server is the device management information of at least one medical device sent by the patient monitor.

27. The device management server according to claim 14, characterized in that: The communication interface is also used to send device management information of at least one medical device to a server in the Internet of Things device management system, so that the server in the Internet of Things device management system stores the device management information.

28. A device management server, characterized in that: The device management server is communicatively connected to at least one patient monitor according to claims 1-13, and the device management server comprises: A communication interface, used to obtain device management information of at least one medical device, the device management information including any one or more of device configuration information, device location information, device maintenance information, device usage information, device accessory information, and device technical alarm information, and send the device management information to a memory; A memory, used to store the device management information; A processor, configured to determine a management service to be provided by the device management server; use a data processing method corresponding to the management service to process the device management information to obtain an information processing result, and send the information processing result to an output device; An output device is used to output the information processing result.

29. A device information management method, characterized in that: Applied to a patient monitor, the patient monitor is communicatively connected with at least one medical device to form a bedside network centered on the patient monitor, and the patient monitor is communicatively connected with a device management server, the method comprising: Collect physiological parameter signals of the monitored object in real time; identifying physiological parameter data from the physiological parameter signal; Obtaining device management information of at least one medical device communicatively connected to the patient monitor, the device management information including any one or more of device configuration information, device location information, device maintenance information, device usage information, device accessory information, and device technical alarm information; The device management information is sent to a device management server that is communicatively connected to the patient monitor.

30. A device information management method, characterized in that: Applied to a device management server, the device management server is in communication with at least one patient monitor and a device management client according to claims 1-13, the method comprising: Receiving device management information of at least one medical device and storing the device management information, wherein the device management information includes any one or more of device configuration information, device location information, device maintenance information, device usage information, device accessory information, and device technical alarm information; Receive a device management request sent by a device management client; Using a data processing method corresponding to the device management request, processing the device management information to obtain an information processing result; The information processing result is sent to the device management client.

31. A device information management method, characterized in that: Applied to a device management server, the device management server is in communication with at least one patient monitor and a device management client according to claims 1-13, the method comprising: Receiving device management information of at least one medical device, the device management information including any one or more of device configuration information, device location information, device maintenance information, device usage information, device accessory information, and device technical alarm information, and storing the device management information; Determining the management service to be provided by the device management server; Using a data processing method corresponding to the management service, the device management information is processed to obtain an information processing result; The information processing result is outputted.

32. A readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the device information management method according to any one of claims 29 to 31 is implemented.

Images