CN116157053B

CN116157053B - Patient monitor and device information management method thereof

Info

Publication number: CN116157053B
Application number: CN202080100575.4A
Authority: CN
Inventors: 刘彦; 陶青林; 陈后全; 代巍巍; 邵珊鸣; 何昆仑; 曹德森; 张政波; 王璨; 梁洪
Original assignee: Shenzhen Mindray Bio Medical Electronics Co Ltd; Chinese PLA General Hospital
Current assignee: Shenzhen Mindray Bio Medical Electronics Co Ltd; Chinese PLA General Hospital
Priority date: 2020-05-15
Filing date: 2020-05-15
Publication date: 2025-05-09
Anticipated expiration: 2040-05-15
Also published as: CN116157053A; WO2021227053A1

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

Patient monitor and equipment information management method thereof

Technical Field

The present application relates to the technical field of medical devices, and more particularly, to a patient monitor and a device information management method thereof.

Background

In the medical field, it is necessary to use equipment to monitor a subject, and perform operations such as medical care. Medical devices include, but are not limited to, bedside devices such as infusion pumps, ventilators, anesthetics, and the like. In order to monitor the working operation of the medical device, a device manager needs to collect device information, and manage the medical device through the device information.

However, in a large care place such as a hospital, medical equipment is often deployed in a plurality of departments and a plurality of wards, and the management work is complicated. The existing management mode mainly collects equipment information manually, management efficiency is low, and more labor cost is consumed.

Disclosure of Invention

In view of this, the present application provides a patient monitor and a device information management method thereof, which replace a manual device information collection manner, and implement automatic centralized management of device management information, so as to save labor management cost and improve management efficiency.

In a first aspect, an embodiment of the present application provides a patient monitor communicatively coupled to at least one medical device and a device management server, the patient monitor comprising:

the parameter sensor accessory is used for collecting physiological parameter signals of a monitored object in real time;

the processor is used for acquiring the physiological parameter signals from the parameter sensor accessory and processing the physiological parameter signals to obtain corresponding physiological parameter data;

And the communication interface is used for acquiring the equipment management information of the medical equipment from the medical equipment and sending the equipment management information to the equipment management server.

In a second aspect, an embodiment of the present application provides a patient monitor communicatively connected to at least one medical device and a device management server, each of the medical devices establishing a data transmission channel with the patient monitor, the patient monitor comprising:

The device comprises a communication interface, a device management server and a device management server, wherein the communication interface is used for acquiring physiological parameter data acquired by the medical device through the data transmission channel between the communication interface and the medical device, acquiring device management information of the medical device through the data transmission channel between the communication interface and the medical device, and transmitting the device management information to the device management server.

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

the communication interface is used for acquiring equipment management information of at least one medical equipment and sending the equipment management information to the memory;

A memory for storing the device management information;

And the processor is used for receiving the equipment management request sent by the equipment management client, processing the equipment management information by using a data processing mode corresponding to the equipment management request to obtain an information processing result, and returning the information processing result to the equipment management client so as to be used for displaying the information processing result by the equipment management client.

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

A memory for storing the device management information;

the processor is used for determining the management service to be provided by the equipment management server, processing the equipment management information by using a data processing mode corresponding to the management service to obtain an information processing result, and sending the information processing result to the output equipment;

and the output device is used for outputting the information processing result.

In a fifth aspect, an embodiment of the present application provides a device information management method applied to a patient monitor communicatively connected to at least one medical device and a device management server, the method comprising:

Collecting physiological parameter signals of a monitored object in real time;

Identifying physiological parameter data from the physiological parameter signal;

obtaining device management information for at least one medical device communicatively coupled to the patient monitor;

And sending the device management information to a device management server in communication with the patient monitor.

In a sixth aspect, an embodiment of the present application provides a device information management method, applied to a device management server, where the device management server is communicatively connected to at least one patient monitor and a device management client provided in the first aspect, and the method includes:

Receiving device management information of at least one medical device and storing the device management information;

receiving an equipment management request sent by an equipment management client;

Processing the equipment management information by using a data processing mode corresponding to the equipment management request to obtain an information processing result;

and sending the information processing result to the equipment management client.

In a seventh aspect, an embodiment of the present application provides a device information management method, applied to a device management server, where the device management server is communicatively connected to at least one patient monitor and a device management client provided in the first aspect, and the method includes:

determining a management service to be provided by the equipment management server;

processing the equipment management information by using a data processing mode corresponding to the management service to obtain an information processing result;

And outputting the information processing result.

In an eighth aspect, an embodiment of the present application provides a readable storage medium having stored thereon a computer program which, when executed by a processor, implements the device information management method provided in any one of the above aspects.

Drawings

In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIGS. 1A-1B are schematic diagrams of two different networking of a device management system;

FIG. 2 is a flow chart of a device information management method;

FIG. 3 is another networking schematic of a device management system;

FIG. 4 is another flow chart of a device information management method;

FIGS. 5A-5D are schematic diagrams of four application scenarios of a device management method;

fig. 6 is a schematic diagram of a patient monitor.

Detailed Description

The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

With the progress of medical technology, medical equipment introduced in various medical care places such as hospitals is gradually increased, and medical services provided are also more and more comprehensive. Medical devices are of a wide variety and are scattered in various wards of various departments such as hospitals, and in order to facilitate management of the medical devices, it is necessary to collect information about the medical devices, such as device hardware basic information, device operating conditions, maintenance upgrade information, and the like. Currently, a device information management scheme of a medical device generally adopts a manual recording mode, namely, the device information is collected by a person and is put in storage respectively. However, the number of medical devices is large, and the traditional management method needs to consume a great deal of labor cost, is easy to have incomplete recorded information, and has lower management efficiency.

In this regard, the present application provides a medical device management scheme, which implements unified management of various medical devices by networking the medical devices, so as to reduce the cost of manual management and improve the efficiency of device management. Specifically, the application provides a system architecture of multi-equipment networking, which takes a patient monitor as a center, connects bedside medical equipment with the patient monitor, collects equipment management information of the bedside medical equipment through the patient monitor, and uniformly sends the equipment management information to an equipment management server.

A specific device management system architecture is shown in FIG. 1A, and the bedside medical devices such as an infusion pump, an anesthesia machine, a breathing machine, a telemetering monitor and the like are respectively in communication connection with the patient monitor to form a bedside network centering on the patient monitor. The communication connection of the bedside network may include wired, wireless, such as bluetooth, serial, etc., and the present application is not particularly limited. In addition, the patient monitor is communicatively coupled to the device management server via a wired, wireless or other means. The network in which the patient monitor communicates with the device management server may be a central monitoring network, an internet of things network, or the like, which is not particularly limited in this regard.

In the system architecture, each patient monitor is directly connected to the device management server in a communication manner, so that each patient monitor needs to independently develop a communication protocol for data communication with the device management server. The communication protocols used by different patient monitors may be different and development effort is significant.

Another specific device management system architecture is shown in FIG. 1B, where bedside medical devices such as infusion pumps, anesthesia machines, ventilators, and telemetry monitors are communicatively connected to patient monitors, respectively, to form a patient monitor-centric bedside network. The patient monitor is in communication connection with a central monitoring server, which is in communication connection with an equipment management server. The central monitoring server may include a central monitoring station, a server of a clinical information system (Clinical Information System, CIS), a server of a hospital information system (Hospital Information System, HIS), or a server of an electronic medical record system (Electronic Medical Record, EMR).

Unlike the system architecture described above, the patient monitor in this architecture is communicatively coupled to the device management server via a central monitoring server. It should be noted that the patient monitor and the central monitoring server may already be in communication connection through the central monitoring network. The central monitoring network primarily transmits patient-related medical data such as patient basic information, patient physiological physical parameters, etc. In order to fully utilize the existing resources and reduce the difficulty of development and networking, the device management server can be added on the basis of the existing system architecture (namely, the network architecture between the patient monitor and the central monitoring server), and particularly, the central monitoring server is in communication connection with the device management server. The patient monitor may use an existing central monitoring network to send device management information to a central monitoring server, which then forwards the device management information to the device management server. Therefore, only a communication protocol between the central monitoring server and the equipment management server is required to be developed, so that development and networking workload is reduced.

It should be noted that the manner of interconnection of the devices is not limited to the above two, but may be any other manner that would be expected by a person skilled in the art to enable the patient monitor to be communicatively connected to the medical device and the device management server. For example, the device management server may be integrated in the central monitoring system, for example, the central monitoring server integrated in the central monitoring system, and the same server as the central monitoring server may be used, in addition to the device management server. It should be noted that, the central monitoring server is a server for implementing the monitoring function, and is capable of implementing the monitoring function mainly because the central monitoring server can receive and process the physiological parameter data sent by the patient monitor to obtain a parameter processing result.

Based on any equipment interconnection scheme, the embodiment of the application provides an equipment information management method. As shown in fig. 2, the device information management method may specifically include steps S201 to S206.

S201, the patient monitor collects physiological parameter signals of a monitored object in real time and identifies physiological parameter data from the physiological parameter signals.

In particular, a patient monitor is provided as a monitoring device having a parameter sensor attachment for acquiring physiological parameter signals of a patient. The physiological parameter signal may be any parameter information that reflects physiological conditions such as blood pressure, blood oxygen, respiration, and heart rate, and the embodiment of the application is not limited in particular. The patient monitor may process the physiological parameter signals to obtain corresponding physiological parameter data. The physiological parameter data may be stored or displayed locally at the patient monitor, and may be further sent to a central monitoring server for storage or other processing operations.

It should be noted that, the patient monitor may perform the monitoring procedure according to the existing monitoring scheme, and the embodiment of the present application is not limited to the specific implementation of the monitoring procedure. In the application scenario of the embodiment of the application, the patient monitor expands the function of collecting the device management information on the basis of the existing monitoring function.

S202, the medical equipment obtains equipment management information.

In particular, the medical device may obtain device management information locally and then send the device management information to the patient monitor. The manner in which the medical device transmits the device management information may include, but is not limited to, the following:

in one embodiment, the medical device may periodically obtain device management information at a preset period and send the device management information to the patient monitor. The preset period can be set according to actual requirements.

In another embodiment, the device operator may input an upload instruction to the medical device via the human-machine interface, the medical device obtains device management information in response to the upload instruction, and transmits the device management information to the patient monitor.

In yet another embodiment, the medical device obtains device management information and transmits the device management information to the patient monitor when a preset condition is monitored by the medical device. For example, the medical device is a pluggable medical accessory, such as a pluggable monitor (e.g., a transfer monitor, a monitor parameter measurement module, etc.), which can be used as a bedside independent monitor or as a pluggable medical accessory to be connected to a patient monitor, and when the medical device monitors that the medical device is connected to and/or disconnected from the patient monitor, device management information of the pluggable medical accessory is obtained and sent to the patient monitor. As another example, when the medical device monitors a device failure, device management information is obtained and sent to the patient monitor.

In yet another embodiment, the medical device receives an information acquisition request sent by the patient monitor, obtains corresponding device management information based on 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 another device, 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.

To summarize, in the first three embodiments, the medical device actively uploads device management information to the patient monitor, while in the fourth embodiment, the medical device returns device management information based on the patient monitor's request.

The device management information is used for describing operation or maintenance conditions of the device, and can also be called device operation and maintenance information, and specifically can comprise any one or more of device configuration information, device position information, device maintenance information, device use information, device accessory information and device alarm information.

The device configuration information is used for representing the basic conditions of software and hardware of the device, and can comprise basic information of the device, such as type, name, serial number, software version, hardware version and the like, and device board card information, such as board card serial number, production date, batch, software and hardware version and the like. The device location information is used to indicate the setting location of the device, and may specifically include a bed number, a room number, a department, a floor, a hospital name, and the like. The equipment maintenance information is used for indicating the maintenance condition of the equipment, and specifically can comprise maintenance time, maintenance type, maintenance content, next maintenance time, maintenance reminding information, upgrading information, calibration information and the like. The device usage information is used for indicating the usage condition of the device, and specifically may include a start-up time, a shut-down time, a running time, a device status, a processor usage rate, a device failure rate, device borrowing information, and the like. The device accessory information is used for representing the basic condition of the accessory included in the device, and specifically may include an accessory version, a serial number, a batch, a use duration, a state, a replacement number, battery information, and the like. The equipment alarm information is used for indicating abnormal alarms occurring in the running process of equipment, for example, a display displays the abnormal alarms, and the equipment is moved out of a preset using range, such as a certain department to alarm. In order to distinguish from physiological alarms generated based on abnormal conditions of the patient, this type of alarm may be referred to as a technical alarm, and may specifically include alarm time, alarm content, alarm type, etc.

S203, the medical device sends device management information to the patient monitor.

Specifically, the medical device transmits any one or more of the types of device management information described above through a communication connection with the patient monitor.

S204, the patient monitor performs preset processing operation on the device management information.

Specifically, the preset processing operations may include adding a medical device identifier to the device management information to indicate from which medical device the device management information originated, and/or adding a time tag to the device management information to indicate the time of collection of the device management information. The processing operation is mainly to add some auxiliary information so that the device management server can make clear the basic situation of the device management information. Of course, the processing operation is not limited to the two kinds of the above, and other operations can be expected by those skilled in the art.

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

S205, the patient monitor sends the device management information after the preset processing operation is executed to the device management server.

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

The medical devices to which the patient monitors are connected may be one or more. If the medical devices are multiple, the patient monitor can collect and uniformly send the device management information of each medical device after receiving the device management information of each medical device, or can respectively send the device management information of each medical device.

In another embodiment, the steps of the patient monitor obtaining its own device management information and sending its own device management information to the device management server may be added. In this way, the patient monitor can send not only the collected device management information of the bedside medical device but also 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 may be collectively referred to as device management information of the medical device.

S206, the device management server stores the device management information.

Specifically, the device management server stores device management information locally at the server. The device management information may be stored in the memory unit so that the processor can provide device management services according to the device management information, on the one hand, or in the nonvolatile storage unit, from which reading is performed when the device management information needs to be used, on the other hand.

According to the technical scheme, the embodiment of the application provides a device information management method, which is applied to a device information management system, wherein the device management system comprises at least one medical device, a patient monitor in communication connection with the medical device and a device management server in communication connection with the patient monitor, the patient monitor obtains the device management information of the medical device through a bedside network and sends the device management information to the device management server, so that the device management information with the patient monitor as a core is automatically collected in a networking way, the cost of manual recording is saved, and the information management efficiency is higher.

It should be noted that, based on the above description, the patient monitor may be communicatively connected to one or more medical devices, and each medical device (including a medical device) may respectively establish a data transmission channel with the patient monitor for data transmission therebetween. Through the data transmission channel, the patient monitor not only can acquire the physiological parameter data acquired by the medical equipment, but also can acquire the equipment management information of the medical equipment. That is, the data transmission channel between the patient monitor and the medical device can be multiplexed, and when the medical device needs to perform data interaction with the device management information, for example, upload the device management information to the device management server or obtain maintenance service information returned by the device management server, the data transmission channel for transmitting the medical data is directly used, so that no additional data transmission network for setting up a single medical device and the device management server is required.

Further, the central monitoring server may be multiplexed with the device management server, i.e. both are integrated on one device or a service cluster consisting of multiple devices. Under the condition, the device management server is considered to be the central monitoring server, and the physiological parameter data and the 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, so that multiplexing of the data transmission channel between the patient monitor and the central monitoring server is realized, and the construction cost of a transmission network is saved.

Alternatively, the central monitoring server and the device management server are respectively deployed devices or clusters of devices. A data transmission channel is established between the patient monitor and the central monitoring server and is mainly used for transmitting physiological parameter data, and a data transmission channel is also established between the patient monitor and the equipment management server and is mainly used for transmitting equipment management information. Thus, the physiological parameter data obtained by the patient monitor and the collected device management information are sent to two different devices or clusters of devices, respectively, via two data transmission channels.

In yet another case, the central monitoring server and the device management server are separately deployed devices or clusters of devices. The data transmission channel established between the patient monitor and the central monitoring server can be used for transmitting physiological parameter data and multiplexing transmission equipment management information. Thus, the patient monitor can send the physiological parameter data and the 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 equipment management server, and the equipment management server is the server for realizing equipment information management, so that the central monitoring server transmits the equipment management information to the equipment management server through the data transmission channel. It can be seen that the existing data transmission channel between the patient monitoring device and the central monitoring server in this case can be used as part of the transmission path of the device management information from the patient monitoring device to the device management server, thereby saving the network construction cost to a certain extent.

The device management server may store device management information, and may display device management information, for example, display basic information of the device, such as a serial number, a production date, a software version, and a hardware version of the device board, and display an alarm list generated by alarm information of the device. Or further performs a device management flow using the device management information to provide the user with a desired device management service. The device management services may include, but are not limited to, information queries, maintenance reminders, escalation reminders, location alarms, and the like. Specifically, the device management server may process the device management information of one or more medical devices to obtain maintenance service information. It should be noted that, in different application scenarios, the requirements for device management are different, and the data processing modes are also different, so that the obtained maintenance service information may also be different. The specific generation process of the maintenance service information can be seen in the following detailed description. The device management server returns maintenance service information to the patient monitor, which further returns maintenance service information to the one or more medical devices. The patient monitor can be seen as a transit device, so that not only can the device management information of the medical device be uploaded to the device management server, but also the maintenance service information generated by the device management server can be returned to the medical device.

In order to provide device management services, an embodiment of the present application provides a medical device management system, as shown in fig. 3, which includes a device management server, a patient monitor, and a device management client. The patient monitor may be a patient monitor as described in any of the above embodiments, and the patient monitor is communicatively connected to at least one bedside medical device and a device management server, and it should be noted that other descriptions of the patient monitor may be referred to the above description and are not repeated herein.

Based on the medical device management system shown in fig. 1A and 1B, the embodiment of the present application adds a device management client communicatively connected to a device management server. The device management client may be in various forms such as a desktop computer, a notebook computer, a tablet computer, a mobile phone, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA), and the like. The device management client realizes communication connection with the device management server by installing an application program dedicated for realizing device management or other application programs integrated with the device management function. For example, the device management client may install a guardian-type application within which a device management module may be integrated to implement device management functions.

The embodiment of the application provides another device information management method depending on the medical device management system with the above architecture. As shown in fig. 4, the device information management method may specifically include steps S401 to S406.

The patient monitor transmits device management information of at least one medical device to the device management server S401.

The patient monitor may upload the device management information of the medical device, and may also upload the device management information of the patient monitor itself. The two types of device management information may be sent in a unified manner or sent separately and independently, and the present application is not limited in particular. In addition, the patient monitor may send the device management information directly to the device management server, or the patient monitor may forward the device management information to the device management server through the central monitoring server.

S402 the device management server stores the device management information.

S403, the device management client sends a device management request to the device management server.

Specifically, the device management client may provide a man-machine interaction interface through which a user inputs a trigger operation, and the device management server generates a device management request based on the trigger operation. This is the case where the user has a need for management of the medical device. Of course, in practical application, the device management client may also automatically generate a device management request if the medical device needs to be managed during the operation.

S404, the device management server processes the device management information by using a data processing mode corresponding to the device management request to obtain an information processing result.

The device management request is to request the device management server to provide a required device management service, and the device management service is generally classified into several types, such as an information viewing service, an alarm prompt service, an upgrade maintenance service, and the like.

After receiving the device management request, the device management server processes the pre-stored device management information by using a data processing mode corresponding to the device management request, thereby obtaining an information processing result corresponding to the device management request. It should be noted that, a correspondence between the device management request and the data processing manner may be preset, so that after the device management request is received, the data processing manner is determined according to the correspondence. The data processing mode may be considered as a functional module written by program code, different functional modules encapsulate different data processing modes represented by the program code, and the execution of the program code can implement the device management service provided by the functional module.

The following describes a specific implementation procedure of the device management service in connection with different application scenarios.

And in the first application scenario, the device management client requests to view the device management information.

When the user wants to view the device management information, the device management client may be triggered to generate a device management information viewing request. As shown in fig. 5A, the device management client transmits a device management information viewing request to the device management server. The device management information viewing request may include an identification of the target device that is desired to be viewed, such as a room number, bed number, or name of the device, etc. If the request does not include the identity of the target device, defaulting to the request to view device management information of all devices, and setting all devices as the target device by default after the device management server receives the request. First, the device management server searches for device management information corresponding to a device management information viewing request from among the stored device management information. For example, the device management information has an association relationship with the device identifier, and the device management server searches for the device management information associated with the target device identifier according to the target device identifier in the device management information viewing request, and for convenience of description, the searched device management information may be referred to as target device management information. Then, the device management server sends the target device management information to the management client as an information processing result for display.

In one embodiment, the device management information viewing request includes a device location information viewing request. The process of searching the target device management information by the device management server specifically comprises the steps of determining the target medical device corresponding to the device position information viewing request, wherein the target medical device can comprise bedside medical devices or patient monitors, and searching the position information of the target medical device in the device management information, wherein the position information comprises a real-time position and/or a historical position. Where the same target medical device may be used in multiple locations, such as a ventilator being moved from beside the bed to an operating room, the historical location represents the location information where the target medical device was previously used.

When the device management server stores the device management information, it may generate an information item of the history location, and if the device management information uploaded by the patient monitor carries an information value related to the history location, the information value is stored in the information item for storage. For example, the device management information uploaded by the patient monitor may include a borrowed location, which may be stored in an information item at a historical location. Of course, the specific form of the information value may be other forms that can be expected by those skilled in the art, and the present application is not limited in particular.

In another embodiment, the device management information viewing request includes a device maintenance information viewing request. The process of searching the target equipment management information by the equipment management server specifically comprises the steps of determining the target medical equipment corresponding to the equipment maintenance information viewing request, and searching the maintenance information of the target medical equipment in the equipment management information, wherein the maintenance information comprises any one or more of maintenance time, maintenance type, maintenance content, next maintenance time, maintenance reminding information, upgrading information and calibration information. Reference may be made to the above embodiment for a specific implementation, which is not described here in detail. For ease of viewing, maintenance information may be included in the list. The user can clearly determine the maintenance condition of the target medical equipment by looking up the maintenance information.

In yet another embodiment, the device management information viewing request comprises a device configuration information viewing request. The process of searching the target device management information by the device management server specifically comprises determining the target medical device corresponding to the device configuration information viewing request, and searching the configuration information of the target medical device in the device management information, wherein the configuration information comprises any one or more of a type, a name, a serial number, board card information, a software version and a hardware version. Reference may be made to the first embodiment for a specific implementation, which is not described here in detail. For ease of viewing, maintenance information may be included in the list. By looking up the configuration information, the user can determine the configuration condition of the target medical device.

In yet another embodiment, the device management information viewing request includes a device usage information viewing request. The process of searching the target device management information by the device management server specifically comprises determining the target medical device corresponding to the device use information viewing request, and searching the use information of the target medical device in the device management information, wherein the use information comprises any one or more of starting-up time, shutdown time, use state, processor use rate, failure rate and borrowing information. Reference may be made to the first embodiment for a specific implementation, which is not described here in detail. For ease of viewing, usage information may be included in the list. The user can determine the use condition of the target medical equipment by looking up the use information.

In yet another embodiment, the device management information viewing request comprises a device attachment information viewing request. The process of searching the target device management information by the device management server specifically comprises determining the target medical device corresponding to the device attachment information viewing request, and searching the attachment information of the target medical device in the device management information, wherein the attachment information comprises any one or more of version, serial number, batch, using duration, state, replacement times and battery information. Reference may be made to the first embodiment for a specific implementation, which is not described here in detail. For ease of viewing, the attachment information may be included in the list. By looking at the attachment information, the user can ascertain the basic condition of each medical attachment.

In yet another embodiment, the device management information viewing request comprises a device alarm information viewing request. The process of searching the target device management information by the device management server specifically comprises the steps of determining the target medical device corresponding to the device attachment information viewing request, and searching the alarm information of the target medical device in the device management information. Reference may be made to the first embodiment for a specific implementation, which is not described here in detail. For ease of viewing, alarm information may be included in the list. By checking the alarm information, the user can clearly determine the alarm condition of each medical device caused by abnormal operation.

In yet another embodiment, the device management information viewing request includes a device usage viewing request. The process of searching the target device management information by the device management server specifically comprises the steps of determining the target medical device corresponding to the device utilization rate checking request, obtaining the device utilization rate of the target medical device in the device management information, and marking the target device utilization rate exceeding a preset utilization rate threshold value to obtain an information processing result. Reference may be made to the first embodiment for a specific implementation, which is not described here in detail. For ease of viewing, device usage may be included in the list. By looking at the device usage rate, the user can ascertain whether individual medical devices are frequently used.

Illustratively, device usage represents the number of uses of the device over a period of time. The device usage rate may be calculated by the device management server receiving device management information uploaded by the patient monitor and storing the device usage rate as an information item. Or the device management server can be calculated according to the read device management information after receiving the device information viewing request. If the number of the determined target medical devices is multiple, the target medical devices with the device utilization rate reaching a certain threshold value can be marked so as to prompt related personnel that the utilization rate of the medical devices is high.

It should be noted that the device management information viewing request may also be in other forms, and the present application is not limited in particular. Any information that can be obtained based on the device management information stored by the device management server is within the scope of the embodiments of the present application.

And in the second application scenario, the equipment management server sends an equipment maintenance reminding message to the equipment management client so as to remind related personnel to regularly maintain the equipment.

As shown in fig. 5B, 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 a maintenance plan of the medical device according to the device maintenance information, where the maintenance plan includes a next maintenance time. The device maintenance information includes a last maintenance time point, and the device management server may calculate a next maintenance time according to the last maintenance time point and a preset device maintenance period. Further, the equipment management server generates a maintenance reminding message for the next maintenance time and sends the maintenance reminding message to the equipment management client so as to remind related personnel to maintain the medical equipment.

It should be noted that, the maintenance reminding message may be sent at a certain time point before the next maintenance time arrives. For example, the day before the next maintenance time arrives, a maintenance alert message is sent to the device management client of the maintenance person.

If a plurality of medical devices need to be maintained, the device management server can count the medical devices with the next maintenance time within the same time range according to the maintenance schedule of each medical device, and the medical devices with the next maintenance time within the same day. These medical devices are labeled.

And in the third application scenario, the equipment management server sends an upgrade reminding message to the medical equipment so as to realize automatic upgrade of the medical equipment.

As shown in fig. 5C, the device management information uploaded by the patient monitor may include device upgrade information. The device management client can send an upgrade information viewing request to the device management server, and the device management server determines the next upgrade time of the medical device according to the device upgrade information. The device upgrade information includes a last upgrade time point, and the device management server may calculate a next upgrade time according to the last upgrade time point and a preset device upgrade period, or the device upgrade information includes current version information of the medical device, and the device management server may determine that the latest version information developed for the medical device is the same, if the two version information are inconsistent, it indicates that the medical device needs to be upgraded, so as to determine that the next upgrade time of the medical device is the current time point or a time point after the preset time length. Further, the device management server generates an upgrade reminding message for the next upgrade time and sends the upgrade reminding message to the medical device so as to remind the medical device of automatic upgrade.

And in the fourth application scenario, the equipment management server sends alarm information to the equipment management client to prompt the position of the medical equipment to change.

As shown in fig. 5D, the device management information uploaded by the patient monitor may include location information. The device management server obtains the position limitation alarm condition of the medical device, and generates alarm information when the position information of the medical device meets the position limitation alarm condition. The position limiting alarm condition refers to preset use range for the medical equipment, and if the position information of the medical equipment exceeds the position use range, an alarm is required. For example, a patient monitor may be allowed to be used only in a particular patient room, and the patient room may be set to a preset range of use in a location-limited alarm condition, and alarm information may be generated when the location information uploaded by the patient monitor, i.e., the current location, exceeds the patient room. The device management server sends the alarm information to the device management client to prompt related personnel about the abnormal position of the medical device.

And S405, the device management server sends the information processing result to the device management client.

The device management server sends the information processing result to the device management client for the device management client to display after obtaining the information processing result no matter any data processing mode is used. The information processing result may also be referred to as maintenance service information.

S406, the device management client side displays the information processing result.

As can be seen from the above technical solutions, the present application provides an apparatus information management method, where an apparatus management server may generate a data processing result according to a preset data processing manner based on apparatus management information, where the data processing result may be considered as an apparatus management service provided by the apparatus management server, for example, apparatus information viewing, apparatus maintenance reminding, apparatus upgrade reminding, apparatus position alarm, and the like. Therefore, the embodiment of the application not only can realize the unified collection of the equipment management information, but also can provide various equipment management services for the user by utilizing the collected equipment management information so as to meet various management requirements of the user on the equipment.

In practical application, the medical care place may have performed networking management on all or part of medical equipment through schemes such as the internet of things, and the equipment information management scheme provided by the embodiment of the application can be used as a supplement to the scheme of the internet of things. In order to save the cost of the Internet of things reconstruction of all devices, the device management server can be in butt joint with the Internet of things device management system of a third party through a simple network management protocol (Simple Network Management Protocol, SNMP), an MQTT (Message Queuing Telemetry Transport, message queue telemetry transport protocol) and the like so as to collect the device management information of the medical devices. Or the device management server sends the device management information to a server in the device management system of the internet of things so that the server stores the device management information.

It should be noted that, the application scenario two, the application scenario three, and the application scenario four may not be limited to processing the device management information based on the device management request of the device management client. The device management server can automatically process the device according to the management requirement.

The device management server receives device management information of at least one medical device, stores the device management information, determines management services to be provided by the device management server, such as device upgrading reminding service, device maintenance reminding service, device position alarm service and the like, processes the device management information by using a data processing mode corresponding to the management services to obtain an information processing result, and outputs the information processing result. The specific implementation of each management service may refer to the above description, which is not repeated herein.

One specific example of a patient monitoring device is shown in fig. 6. Fig. 6 provides a system frame diagram of a parameter processing module in the multi-parameter monitor.

The multi-parameter monitor has a separate housing with a sensor interface area on a housing panel with a plurality of sensor interfaces integrated therein for connection to external individual physiological parameter sensor accessories 611, a small IXD display area, a display 618, an input interface circuit 620, and an alarm circuit 619 (e.g., LED alarm area), etc. The parameter processing module is used for external communication and power interface for communicating with the host and taking electricity from the host. The parameter processing module also supports an externally inserted parameter module, which can be used as an external accessory of the monitor by being inserted into the parameter module to form a plug-in monitor host as a part of the monitor or by being connected with the host through a cable. In addition, the multi-parameter monitor includes a memory 617 for storing computer programs and various data generated during the relevant monitoring process.

The internal circuitry of the parameter processing module is disposed within the housing, as shown in fig. 6, and includes at least two signal acquisition circuits 612, a front-end signal processing circuit 613, and a main processor 615 corresponding to physiological parameters.

The main processor 615 may implement the various process-related steps of the various apneic event monitoring methods described above.

The signal acquisition circuit 612 may be selected from an electrocardiograph circuit, a respiratory circuit, a body temperature circuit, an oximetry circuit, a noninvasive blood pressure circuit, an invasive blood pressure circuit, etc., and these signal acquisition circuits 612 are respectively electrically connected to corresponding sensor interfaces for electrically connecting to the sensor accessories 611 corresponding to different physiological sign parameters, the output ends of which are coupled to a front-end signal processor, the communication ports of which are coupled to a main processor, and the main processor is electrically connected to an external communication and power interface.

Various physiological physical sign parameter measuring circuits can adopt a general circuit in the prior art, and a front-end signal processor is used for completing sampling and analog-to-digital conversion of signals output by a signal acquisition circuit and outputting control signals to control the measurement process of physiological signals, wherein the parameters comprise, but are not limited to, electrocardio, respiration, body temperature, blood oxygen, noninvasive blood pressure and invasive blood pressure parameters.

The front-end signal processor can be realized by a singlechip or other semiconductor devices, and can also be realized by an ASIC or an FPGA. The front-end signal processor may be powered by an isolated power supply, and the sampled data may be simply processed and packaged for transmission to the host processor via an isolated communication interface, e.g., the front-end signal processor circuit may be coupled to the host processor 615 via the isolated power supply and communication interface 614.

The reason that the front-end signal processor is powered by the isolation power supply is that the DC/DC power supply isolated by the transformer plays a role in isolating a patient from power supply equipment, and the main purposes are that 1, the patient is isolated, an application part is floated to the ground through the isolation transformer, so that leakage current of the patient is sufficiently small, and 2, voltage or energy during defibrillation or electrotome application is prevented from affecting a board card and devices (guaranteed by creepage distance and electric gap) of intermediate circuits such as a main control board.

The main processor completes the calculation of physiological physical sign parameters, and sends the calculation result and waveform of the parameters to a host (such as a host with a display, a PC, a central station, etc.) through an external communication and power interface 616, which may be one or a combination of local area network interfaces formed by Ethernet (Token Ring), token Bus (Token Bus) and backbone network Fiber Distributed Data Interface (FDDI) serving as the three networks, or one or a combination of wireless interfaces such as infrared, bluetooth, wifi, WMTS communication, etc., or one or a combination of wired data connection interfaces such as RS232, USB, etc.

The external communication and power interface 616 may also be one or a combination of a wireless data transfer interface and a wired data transfer interface. The host computer can be any one of a host computer of a monitor, an electrocardiograph, an ultrasonic diagnostic apparatus, a computer and the like, and can form a monitoring device by installing matched software. The host can also be communication equipment, such as a mobile phone, and the parameter processing module sends data to the mobile phone supporting Bluetooth communication through the Bluetooth interface so as to realize remote transmission of the data.

In addition, the present application provides a readable storage medium having stored thereon a computer program which, when executed by a processor, implements the above-described various device information management methods.

It should be noted that, in the present specification, each embodiment is described in a progressive manner, and each embodiment is mainly described as different from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other.

It is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A patient monitor communicatively coupled to at least one medical device to form a bedside network centered on the patient monitor, and communicatively coupled to a device management server, the patient monitor comprising:

And the communication interface is used for acquiring equipment management information of the medical equipment from the medical equipment, wherein the equipment management information comprises any one or more of equipment configuration information, equipment position information, equipment maintenance information, equipment use information, equipment accessory information and equipment technology alarm information, and the equipment management information is sent to the equipment management server.

2. The patient monitor of claim 1, wherein the communication interface is specifically configured to, when transmitting the device management information to the device management server:

and transmitting the equipment management information to an equipment management server in communication connection with the patient monitor based on a communication protocol corresponding to the patient monitor and the equipment management server, wherein the communication protocols of different patient monitors and the equipment management server are different.

3. The patient monitor of claim 1, further communicatively coupled to a central monitoring server via the communication interface, the central monitoring server communicatively coupled to the device management server based on a particular communication protocol, the communication interface being operable to, upon sending the device management information to the device management server:

and transmitting the device management information to the central monitoring server, so that the central monitoring server transmits the device management information to the device management server based on a communication protocol corresponding to the device management server.

4. The patient monitor of claim 1, wherein the communication interface is specifically configured to, when acquiring device management information of the medical device from the medical device:

receiving device management information uploaded by at least one medical device communicatively coupled to the patient monitor, and/or,

And sending an information acquisition request to at least one medical device in communication connection with the patient monitor, and receiving device management information corresponding to the information acquisition request returned by the medical device.

5. The patient monitor of claim 1, wherein the medical device comprises a pluggable medical accessory, and wherein the communication interface is specifically configured to, when device management information of the medical device is obtained from the medical device:

and when the pluggable medical accessory is accessed and/or unplugged from the patient monitor, obtaining the equipment management information of the pluggable medical accessory.

6. The patient monitor of claim 1, wherein the device configuration information comprises at least one of a device type, a device name, a software version, a hardware version, and device board information, the device location information comprises at least one of a bed number, a room number, a department, a floor, and a hospital name, the device maintenance information comprises at least one of a maintenance time, a maintenance type, maintenance content, a next maintenance time, maintenance reminder information, upgrade information, and calibration information, the device usage information comprises at least one of a power on time, a power off time, a run time, a device status, a processor usage rate, a device failure rate, and device borrowing information, the device attachment information comprises at least one of an attachment version, a serial number, a lot, a usage duration, a status, a number of changes, and battery information, and the device technology alert information comprises any one or more of a display abnormality and a device being moved out of a preset usage range.

7. The patient monitor of claim 1, wherein the patient monitor comprises a monitor housing,

The communication interface is also used for sending the device management information of the patient monitor itself to the device management server.

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

9. The patient monitor of claim 1, wherein the processor is further configured to:

receiving maintenance service information returned by the equipment management server, wherein the maintenance service information is obtained by processing equipment management information of one or more medical equipment; and returning the maintenance service information to the corresponding medical equipment.

10. The patient monitor is characterized in that the patient monitor is in communication connection with at least one medical device to form a bedside network centering on the patient monitor, the patient monitor is in communication connection with a device management server, each medical device respectively establishes a data transmission channel with the patient monitor, and the patient monitor comprises:

The device comprises a communication interface, a device management server and a device management server, wherein the communication interface is used for acquiring physiological parameter data acquired by medical equipment through the data transmission channel between the communication interface and the medical equipment, acquiring device management information of the medical equipment through the data transmission channel between the communication interface and the medical equipment, wherein the device management information comprises any one or more of device configuration information, device position information, device maintenance information, device use information, device accessory information and device technology alarm information, and transmitting the device management information to the device management server.

11. The patient monitor of claim 10, wherein the processor is further configured to:

transmitting the physiological parameter data to a central monitoring server through a data transmission channel between the patient monitor and the central monitoring server, and

In the case that the device management server is a central monitoring server, the device management information is transmitted to the central monitoring server through a data transmission channel between the device management server and the central monitoring server.

12. The patient monitor of claim 10, wherein the processor is further configured to:

In the case that the device management server is not a central monitoring server, the device management information is transmitted to the device management server through a data transmission channel between the patient monitor and the device management server.

13. The patient monitor of claim 10, wherein the processor is further configured to:

And in the case that the equipment management server is not a central monitoring server, the equipment management information is sent to the central monitoring server through a data transmission channel between the patient monitor and the central monitoring server, so that the central monitoring server sends the equipment management information to the equipment management server through the data transmission channel between the central monitoring server and the equipment management server.

14. A device management server in communication with at least one patient monitor and device management client of any one of claims 1-13, the device management server comprising:

The communication interface is used for acquiring equipment management information of at least one medical equipment, wherein the equipment management information comprises any one or more of equipment configuration information, equipment position information, equipment maintenance information, equipment use information, equipment accessory information and equipment technology alarm information, and sending the equipment management information to the memory;

A memory for storing the device management information;

15. The device management server of claim 14, wherein the device management request comprises a device management information view request;

The processor is specifically configured to, when processing the device management information to obtain an information processing result by using a data processing manner corresponding to the device management request:

and searching target equipment management information corresponding to the equipment management information viewing request in the equipment management information, and sending the target equipment management information to the management client as an information processing result for display.

16. The device management server of claim 15, wherein the device management information viewing request comprises a device location 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:

determining target medical equipment corresponding to the equipment position information viewing request;

and searching the position information of the target medical equipment in the equipment management information, wherein the position information comprises a real-time position and/or a historical position.

17. The device management server of claim 15, wherein the device management information viewing request comprises a device maintenance information viewing request;

the processor is specifically configured to, when searching for target device management information corresponding to the device management information viewing request in the device management information:

Determining target medical equipment corresponding to the equipment maintenance information viewing request;

And searching the maintenance information of the target medical equipment in the equipment management information, wherein the maintenance information comprises any one or more of maintenance time, maintenance type, maintenance content, next maintenance time, maintenance reminding information, upgrading information and calibration information.

18. The device management server of claim 15, wherein the device management information viewing request comprises a device configuration information viewing request;

determining target medical equipment corresponding to the equipment configuration information viewing request;

and searching configuration information of the target medical equipment in the equipment management information, wherein the configuration information comprises any one or more of a type, a name, a serial number, board card information, a software version and a hardware version.

19. The device management server of claim 15, wherein the device management information viewing request comprises a device usage information viewing request;

determining a target medical device corresponding to the device usage information viewing request;

and searching the use information of the target medical equipment in the equipment management information, wherein the use information comprises any one or more of starting time, closing time, use state, processor use rate, failure rate and borrowing information.

20. The device management server of claim 15, wherein the device management information viewing request comprises a device attachment information viewing request;

determining target medical equipment corresponding to the equipment accessory information viewing request;

and searching the accessory information of the target medical equipment in the equipment management information, wherein the accessory information comprises any one or more of version, serial number, batch, using duration, state, replacement times and battery information.

21. The device management server of claim 15, wherein the device management information viewing request comprises a device alarm information viewing request;

and searching alarm information of the target medical equipment in the equipment management information.

22. The device management server of claim 15, wherein the device management request comprises a device usage viewing request;

Determining a target medical device corresponding to the device usage viewing request;

And obtaining the equipment utilization rate of the target medical equipment from the equipment management information, and marking the utilization rate of the target equipment exceeding a preset utilization rate threshold value to obtain an information processing result.

23. The device management server of claim 14, wherein the device management information includes device maintenance information;

The processor is also used for determining a maintenance plan of the medical equipment according to the equipment maintenance information of the medical equipment, wherein the maintenance plan comprises next maintenance time, generating a maintenance reminding message according to the next maintenance time and sending the maintenance reminding message to the equipment management client through the communication interface.

24. The device management server according to claim 14, wherein the device management information includes device upgrade information;

the processor is also used for determining the next upgrading time of the medical equipment according to the equipment upgrading information of the medical equipment, generating an upgrading reminding message according to the next upgrading time and sending the upgrading reminding message to the medical equipment through the communication interface.

25. The device management server according to claim 14, wherein the device management information includes location information;

and the processor is also used for generating alarm information when the position information of the medical equipment meets the position limiting alarm condition of the medical equipment and sending the alarm information to the equipment management client through the communication interface.

26. The device management server of claim 14, wherein the device management server,

The device management server is in communication connection with the patient monitor, and the communication interface is specifically used for receiving the device management information of at least one medical device sent by the patient monitor or when receiving the device management information of at least one medical device

The device management server is in communication connection with the patient monitor through the central monitoring server, and the communication interface is specifically used for receiving the device management information sent by the central monitoring server when receiving the device management information of at least one medical device, wherein the device management information of the central monitoring server is the device management information of the at least one medical device sent by the patient monitor.

27. The device management server of claim 14, wherein the device management server,

And the communication interface is also used for sending the equipment management information of the at least one medical equipment to a server in the equipment management system of the Internet of things so that the server in the equipment management system of the Internet of things stores the equipment management information.

28. A device management server in communication with at least one patient monitor as set forth in claims 1-13, the device management server comprising:

A memory for storing the device management information;

and the output device is used for outputting the information processing result.

29. A device information management method for use with a patient monitor communicatively coupled to at least one medical device to form a bedside network centered on the patient monitor, the patient monitor communicatively coupled to a device management server, the method comprising:

Collecting physiological parameter signals of a monitored object in real time;

Obtaining device management information of at least one medical device in communication with 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 attachment information, device technology alarm information;

30. A device information management method applied to a device management server in communication with at least one patient monitor and 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 comprises any one or more of device configuration information, device position information, device maintenance information, device use information, device accessory information and device technology alarm information;

31. A device information management method applied to a device management server in communication with at least one patient monitor and device management client according to claims 1-13, the method comprising:

receiving device management information of at least one medical device, wherein the device management information comprises any one or more of device configuration information, device position information, device maintenance information, device use information, device accessory information and device technology alarm information, and storing the device management information;

And outputting the information processing result.

32. A readable storage medium having stored thereon a computer program, wherein the computer program when executed by a processor implements the device information management method according to any one of claims 29 to 31.