Patient monitor connection and monitoring method, computer equipment

Abstract

The present application relates to the field of patient monitor connection and monitoring, and specifically to a patient monitor connection and monitoring method and computer equipment. A specific implementation of the method includes: the patient monitor front end responds to receiving Bluetooth connection address debugging information, and transmits the Bluetooth connection address debugging information to the monitor server; the monitor server performs permission identification processing based on the user identification of the technician and the Bluetooth connection address debugging information; sends the proxy connection address information and port information to the patient monitor front end; the patient monitor front end receives the proxy connection address information and port information, and generates a Bluetooth connection remote debugging request based on the Bluetooth connection address debugging configuration information; the monitor server receives the Bluetooth connection remote debugging request, and forwards the Bluetooth connection remote debugging request to the corresponding debugging port. This implementation method transmits information through the Bluetooth module, avoids many lines pressing under the patient, and reduces the risk of pressure sores.

Description

Technical Field

[0001] The present application relates to the field of patient monitor connection and monitoring, and specifically to a patient monitor connection and monitoring method and computer equipment. Background Art

[0002] At present, in intensive care, it is necessary to monitor multiple indicators such as heart rate, blood pressure, respiration, blood oxygen, intracranial pressure, arterial pressure, etc. Each type of existing monitoring equipment has several connecting wires, which have many problems: 1. Many wires will press under the patient, and patients with low protein are prone to blisters, leading to pressure sores; 2. The wires are messy, and it takes a lot of time to organize them, which increases the workload of nursing; 3. The wires are easily contaminated and breed bacteria. Incomplete disinfection will lead to cross infection, which has serious consequences in intensive care.

[0003] In addition, although some devices have the function of being used independently and do not require wiring, such as blood oxygen finger cuffs and ECG monitoring electrodes, they are only suitable for short-term emergency applications outside. They do not have storage and data transmission functions and have poor accuracy. Summary of the invention

[0004] The content of this application is used to introduce concepts in a brief form, which will be described in detail in the detailed implementation section below. The content of this application is not intended to identify the key features or essential features of the technical solution claimed for protection, nor is it intended to limit the scope of the technical solution claimed for protection.

[0005] Some embodiments of the present application propose a patient monitor connection and monitoring method and a computer device to solve the technical problems mentioned in the above background technology section.

[0006] In a first aspect, some embodiments of the present application provide a patient monitor connection and monitoring method, the method comprising: in response to receiving Bluetooth connection address debugging information input by a technician in any monitoring device included in the patient monitor, the patient monitor front end transmits the above Bluetooth connection address debugging information to the associated monitor server, wherein the patient monitor includes multiple different types of monitoring devices, each monitoring device is provided with a Bluetooth connection module and a signal enhancement module; in response to receiving the Bluetooth connection address debugging information of the monitoring device in the corresponding patient monitor, the monitor server performs permission identification processing according to the user identification of the above technician and the above Bluetooth connection address debugging information to obtain a permission identification result; the monitor server determines whether the remote connection server has opened the debugging port corresponding to the above Bluetooth connection address debugging information; the monitor server responds to determining that the remote connection server has opened the debugging port corresponding to the above Bluetooth connection address The debugging port of the address debugging information is received, and the above-mentioned permission identification result indicates that the permission identification is passed, and the proxy connection address information and port information are sent to the above-mentioned patient monitor front end; the above-mentioned patient monitor front end receives the proxy connection address information and port information sent by the above-mentioned monitor server, saves the above-mentioned proxy connection address information and the above-mentioned port information as Bluetooth connection address debugging configuration information, and generates a Bluetooth connection remote debugging request according to the above-mentioned Bluetooth connection address debugging configuration information, and sends it to the above-mentioned monitor server; the above-mentioned monitor server responds to receiving the Bluetooth connection remote debugging request sent by the corresponding patient monitor front end, forwards the above-mentioned Bluetooth connection remote debugging request to the debugging port corresponding to the above-mentioned Bluetooth connection address debugging information; the above-mentioned monitor server responds to determining that the Bluetooth connection debugging of the patient monitor is completed, and sends a Bluetooth connection test signal to the above-mentioned patient monitor to test the connection status with the above-mentioned patient monitor.

[0007] In a second aspect, the present application also provides a computer device, comprising a patient monitor front end, a monitor server, a patient monitor, a memory, and a computer program stored on the memory and executable by the patient monitor front end, the monitor server, and the patient monitor, wherein when the computer program is executed by the patient monitor front end, the monitor server, and the patient monitor, the method described in any implementation manner of the first aspect is implemented.

[0008] The above-mentioned embodiments of the present application have the following beneficial effects: information transmission through the Bluetooth module avoids many lines from pressing under the patient's body, reducing the risk of pressure sores. In addition, the problem of messy lines is eliminated, the nursing workload is reduced, and the nursing efficiency is improved; the risk of line pollution and cross infection is reduced, and the safety of intensive care is improved. In addition, it has storage and data transmission functions, which is convenient for doctors to perform routine treatment and long-term care, and improves the accuracy and reliability of monitoring. First, the patient monitor front end responds to receiving the Bluetooth connection address debugging information input by the technician in any monitoring device included in the patient monitor, and transmits the above Bluetooth connection address debugging information to the associated monitor server, wherein the patient monitor includes multiple different types of monitoring devices, and each monitoring device is provided with a Bluetooth connection module and a signal enhancement module. Thus, it is convenient to transmit data with the patient monitor through the Bluetooth connection module, the signal enhancement module. Secondly, the monitor server responds to receiving the Bluetooth connection address debugging information of the corresponding monitoring device in the patient monitor, and performs permission identification processing according to the user identification of the above technician and the above Bluetooth connection address debugging information to obtain the permission identification result. Thus, the technical personnel's authority for the remote debugging address information can be first identified to determine whether the technical personnel has the authority to debug the Bluetooth connection. Then, the monitor server determines whether the remote connection server has opened the debugging port corresponding to the above-mentioned Bluetooth connection address debugging information. Then, the monitor server responds to the determination that the remote connection server has opened the debugging port corresponding to the above-mentioned Bluetooth connection address debugging information, and the above-mentioned authority identification result indicates that the authority identification is passed, and sends the proxy connection address information and port information to the above-mentioned patient monitor front end. Afterwards, the above-mentioned patient monitor front end receives the proxy connection address information and port information sent by the above-mentioned monitor server, saves the above-mentioned proxy connection address information and the above-mentioned port information as Bluetooth connection address debugging configuration information, and generates a Bluetooth connection remote debugging request according to the above-mentioned Bluetooth connection address debugging configuration information, and sends it to the above-mentioned monitor server. Then, the above-mentioned monitor server responds to receiving the Bluetooth connection remote debugging request sent by the corresponding patient monitor front end, and forwards the above-mentioned Bluetooth connection remote debugging request to the above-mentioned debugging port corresponding to the above-mentioned Bluetooth connection address debugging information. Therefore, when debugging the remote Bluetooth connection, the technician only needs to input the Bluetooth connection address debugging information at the front end of the patient monitor, and the user does not need to perform complex configuration, which simplifies the configuration operation of remote debugging. In addition, because the front end of the patient monitor does not need to be directly connected to the debugging port of the remote connection server, but is forwarded through the monitor server, the possibility of the debugging port being used by other illegal users is reduced, and the security of debugging is improved. Finally, in response to determining that the Bluetooth connection debugging of the patient monitor is completed, the monitor server sends a Bluetooth connection test signal to the patient monitor to test the connection status with the patient monitor.Thus, the communication efficiency of the patient monitor can be tested to ensure smooth data transmission. Information transmission through the Bluetooth module avoids many lines pressing under the patient, reducing the risk of pressure sores. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The above and other features, advantages and aspects of the embodiments of the present application will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar figure labels represent the same or similar elements. It should be understood that the drawings are schematic and that the components and elements are not necessarily drawn to scale.

[0010] Figure 1 is a flow chart of some embodiments of the patient monitor connection and monitoring method according to the present application;

[0011] Figure 2 It is a schematic diagram of the structure of a computer device suitable for implementing some embodiments of the present application. DETAILED DESCRIPTION

[0012] Embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present application. It should be understood that the drawings and embodiments of the present application are only for exemplary purposes and are not intended to limit the scope of protection of the present application.

[0013] It should also be noted that, for ease of description, only the parts related to the invention are shown in the drawings. In the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other.

[0014] It should be noted that the concepts such as "first" and "second" mentioned in this application are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0015] It should be noted that the modifications of "one" and "plurality" mentioned in the present application are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0016] The names of the messages or information exchanged between multiple devices in the embodiments of the present application are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0017] The present application will be described in detail below with reference to the accompanying drawings and in combination with embodiments.

[0018] Figure 1 1 is a flow chart of some embodiments of the patient monitor connection and monitoring method according to the present application. 100 of some embodiments of the patient monitor connection and monitoring method according to the present application is shown. The patient monitor connection and monitoring method comprises the following steps:

[0019] Step 101 , in response to receiving Bluetooth connection address debugging information input by a technician in any monitoring device included in the patient monitor, the patient monitor front end transmits the Bluetooth connection address debugging information to the associated monitor server.

[0020] In some embodiments, the patient monitor front end responds to receiving the Bluetooth connection address debugging information input by the technician in any monitoring device included in the patient monitor, and transmits the above Bluetooth connection address debugging information to the associated monitor server. Among them, the patient monitor includes multiple different types of monitoring devices, and a Bluetooth connection module and a signal enhancement module are set in each monitoring device. The patient monitor front end may refer to the front-end device of the patient monitor. For example, the patient monitor front end may refer to a computing device that displays the monitoring software of the patient monitor. The monitoring software may refer to the operating software for controlling the patient monitor, which has various operation pages. The patient monitor may include: ECG monitors, blood pressure monitors, respiratory monitors, blood oximeters, intracranial pressure monitors, arterial pressure monitors and other monitoring devices. The Bluetooth connection module may refer to a Bluetooth communication module set in the monitoring device. The signal enhancement module may be a signal enhancement module set in the monitoring device. For example, the signal enhancement module can be a wireless enhancement module: covering Bluetooth and wireless signal enhancement, such as the ZK-502L module 5.0 Bluetooth 2*50W digital amplifier board, used for HIFI fever high-power 2.0 stereo enhancement, and various models of wireless signal amplifier modules, such as the AB89 wireless signal enhancement module, which supports 868MHz and 915MHz signal enhancement. That is, a Bluetooth connection module and a signal enhancement module are set in each monitoring device (ECG monitor, blood pressure monitor, respiratory monitor, blood oximeter, intracranial pressure monitor, arterial pressure monitor). The monitor server can be a server that processes data, tests signals, tests and maintains monitoring software for the patient monitor front end and the patient monitor. The monitor server can receive data collected by the patient monitor through the Bluetooth connection module. Among them, the above-mentioned monitor server can also receive requests from the patient monitor front end, and then forward these requests to other servers, and return the server's response to the patient monitor front end. The patient monitor front end and the monitor server can be connected in LAN mode or in public network mode. The patient monitor front end and the monitor server can be connected via a wired connection or a wireless connection. The monitor server can be deployed with software that supports TCP protocol request forwarding. For example, the software may include: nginx, haproxy. The monitor server can set multiple ports, each of which corresponds to a debug port (debug port) of a remote server for forwarding mapping. The above-mentioned patient monitor front end can be installed with an IDEA plug-in. The user can input the Bluetooth connection address debugging information through the IDEA plug-in. The Bluetooth connection address debugging information can be the IP address of the server that needs to perform remote debugging of the Bluetooth connection address.

[0021] Step 102, in response to receiving the Bluetooth connection address debugging information of the monitoring device in the corresponding patient monitor, the monitor server performs permission identification processing according to the user identification of the technician and the Bluetooth connection address debugging information to obtain a permission identification result.

[0022] In some embodiments, in response to receiving the Bluetooth connection address debugging information of the monitoring device in the corresponding patient monitor, the monitor server performs permission identification processing according to the user identification of the technician and the Bluetooth connection address debugging information to obtain a permission identification result.

[0023] For example, first, obtain the permission information corresponding to the above-mentioned user identification and the above-mentioned Bluetooth connection address debugging information. The monitor server can obtain the permission information corresponding to the above-mentioned user identification and the above-mentioned Bluetooth connection address debugging information from the technical service end through the permission information acquisition interface. The permission information acquisition interface can be a previously encapsulated interface for obtaining the permission-related information of the user stored by the technical service end. The technical service end can be the server end of the ERP system. The above-mentioned user identification and the above-mentioned Bluetooth connection address debugging information can be used as interface parameters of the permission information acquisition interface. Then, the above-mentioned permission information is determined as the user authentication result. The user identification can uniquely represent the technician. The permission information can indicate whether the technician has the authority to debug the debug port corresponding to the Bluetooth connection address debugging information.

[0024] Step 103: The monitor server determines whether the remote connection server has opened a debugging port corresponding to the debugging information of the Bluetooth connection address.

[0025] In some embodiments, the monitor server determines whether the remote connection server opens a debugging port corresponding to the above-mentioned Bluetooth connection address debugging information.

[0026] The remote connection server may be a server where an application program that a technician needs to debug via remote Bluetooth connection is located. The debugging port corresponding to the remote debugging address information may be pre-set. For example, the port status of the debugging port corresponding to the Bluetooth connection address debugging information may be obtained from the remote connection server. Then, after determining that the port status indicates that the port is enabled, it is determined that the remote connection server has enabled the debugging port corresponding to the remote debugging address information.

[0027] Step 104, in response to determining that the remote connection server has opened the debugging port corresponding to the Bluetooth connection address debugging information, and the permission identification result indicates that the permission identification is passed, the monitor server sends the proxy connection address information and port information to the patient monitor front end.

[0028] In some embodiments, the monitor server sends the proxy connection address information and port information to the patient monitor front end in response to determining that the remote connection server has opened the debugging port corresponding to the above-mentioned Bluetooth connection address debugging information, and the above-mentioned permission identification result indicates that the permission identification is passed. The above-mentioned proxy connection address information and the above-mentioned port information may be an IP address and port for providing reverse Bluetooth connection service for the patient monitor front end. The above-mentioned proxy connection address information and the above-mentioned port information may be an available IP address and an available port assigned to the above-mentioned patient monitor front end. The above-mentioned proxy connection address information and the above-mentioned port information may be assigned to the above-mentioned patient monitor front end through a port allocation service.

[0029] Step 105, the patient monitor front end receives the proxy connection address information and port information sent by the monitor server, saves the proxy connection address information and the port information as Bluetooth connection address debugging configuration information, and generates a Bluetooth connection remote debugging request based on the Bluetooth connection address debugging configuration information, and sends it to the monitor server.

[0030] In some embodiments, the patient monitor front end receives the proxy connection address information and port information sent by the monitor server, saves the proxy connection address information and the port information as Bluetooth connection address debugging configuration information, and generates a Bluetooth connection remote debugging request based on the Bluetooth connection address debugging configuration information, and sends it to the monitor server. That is, a Bluetooth connection remote debugging request including a remote connection request and a remote operation request can be generated. Then, based on the proxy connection address information and port information included in the Bluetooth connection address debugging configuration information, the Bluetooth connection remote debugging request is sent to the monitor server. The remote debugging request can be a request for requesting a remote debugging operation. The remote debugging operation can be an operation for debugging a Bluetooth connection. For example, the remote debugging operation can include: setting a breakpoint, continuing to execute a program, entering a function, and terminating and exiting.

[0031] Further, the monitor server associates the Bluetooth connection address debugging information with the exit address information of the front end of the patient monitor. The exit address information may be the exit IP address of the front end of the patient monitor. The monitor server may map the Bluetooth connection address debugging information with the exit address information of the front end of the patient monitor to associate the Bluetooth connection address debugging information with the exit address information of the front end of the patient monitor.

[0032] Step 106 , in response to receiving the Bluetooth connection remote debugging request sent by the corresponding patient monitor front end, the monitor server forwards the Bluetooth connection remote debugging request to the debugging port corresponding to the Bluetooth connection address debugging information.

[0033] In some embodiments, in response to receiving a Bluetooth connection remote debugging request sent by a corresponding patient monitor front end, the monitor server forwards the Bluetooth connection remote debugging request to a debugging port corresponding to the Bluetooth connection address debugging information.

[0034] In an actual application scenario, the monitor server can forward the Bluetooth connection remote debugging request to the debugging port corresponding to the Bluetooth connection address debugging information through the following steps:

[0035] The first step is to read the exit address information from the Bluetooth connection remote debugging request. For example, the source IP address can be extracted from the IP header of the TCP message segment of the Bluetooth connection remote debugging request as the exit address information.

[0036] The second step is to determine the Bluetooth connection address debugging information bound to the above export address information.

[0037] The third step is to send the above Bluetooth connection remote debugging request to the debugging port corresponding to the Bluetooth connection address debugging information.

[0038] Step 107 : In response to determining that the Bluetooth connection debugging of the patient monitor is completed, the monitor server sends a Bluetooth connection test signal to the patient monitor to test the connection status with the patient monitor.

[0039] In some embodiments, in response to determining that the Bluetooth connection debugging of the patient monitor is completed, the monitor server sends a Bluetooth connection test signal to the patient monitor to test the connection status with the patient monitor.

[0040] Furthermore, in response to receiving the Bluetooth connection test signal, the patient monitor adds a time stamp to the Bluetooth connection test signal to obtain a marked Bluetooth connection test signal, and sends the marked Bluetooth connection test signal to the monitor server.

[0041] In some embodiments, in response to receiving the Bluetooth connection test signal, the patient monitor adds a time stamp to the Bluetooth connection test signal to obtain a marked Bluetooth connection test signal, and sends the marked Bluetooth connection test signal to the monitor server. The time stamp may refer to a timestamp when the Bluetooth connection test signal is received.

[0042] Furthermore, the monitor server extracts the time stamp in the marked Bluetooth connection test signal in response to receiving the marked Bluetooth connection test signal sent by the patient monitor, generates a feedback signal corresponding to the marked Bluetooth connection test signal, and sends the feedback signal to the patient monitor.

[0043] In some embodiments, the monitor server extracts the time stamp in the marked Bluetooth connection test signal in response to receiving the marked Bluetooth connection test signal sent by the patient monitor, generates a feedback signal corresponding to the marked Bluetooth connection test signal, and sends the feedback signal to the patient monitor.

[0044] Furthermore, in response to receiving the feedback signal, the patient monitor adds a time stamp to the feedback signal to obtain a marked feedback signal, and sends the marked feedback signal to the monitor server.

[0045] In some embodiments, in response to receiving the feedback signal, the patient monitor adds a time stamp to the feedback signal to obtain a marked feedback signal, and sends the marked feedback signal to the monitor server.

[0046] Furthermore, in response to receiving the marked feedback signal sent by the patient monitor, the monitor server generates Bluetooth communication connection delay detection information according to the marked feedback signal and the time stamp in the marked Bluetooth connection test signal.

[0047] In some embodiments, the monitor server generates Bluetooth communication connection delay detection information in response to receiving a tag feedback signal sent by the patient monitor according to a time stamp in the tag feedback signal and the tag Bluetooth connection test signal.

[0048] In an actual application scenario, the above execution subject can generate Bluetooth communication connection delay detection information through the following steps:

[0049] The first step is to extract a time stamp from the above-mentioned marked feedback signal as a feedback time stamp.

[0050] The second step is to determine the receiving time of the marking feedback signal sent by the patient monitor as the feedback receiving time.

[0051] The third step is to determine the reception time of the marked Bluetooth connection test signal sent by the patient monitor as the marked reception time.

[0052] The fourth step is to determine the time difference between the time mark and the time when the mark is received as the first time difference.

[0053] The fifth step is to determine the time difference between the feedback reception time and the feedback time stamp as the second time difference.

[0054] In a sixth step, in response to determining that the difference between the first time difference and the second time difference is less than or equal to a preset threshold, generate Bluetooth communication connection delay detection information indicating no delay.

[0055] Furthermore, in response to detecting an update test instruction for the monitoring software in the patient monitor, the monitor server receives basic monitoring software code information and monitoring software branch information input by the target technician, and determines a software code difference information set corresponding to the monitoring software branch information.

[0056] In some embodiments, the monitor server receives basic monitoring software code information and monitoring software branch information input by a target technician in response to detecting an update test instruction for the monitoring software in the patient monitor, and determines a software code difference information set corresponding to the monitoring software branch information, wherein one software code difference information corresponds to one update method.

[0057] Among them, the above-mentioned basic monitoring software code information can represent the basic monitoring software code branch, and can be the branch name of the basic monitoring software code branch. The above-mentioned monitoring software branch information can represent the code branch that needs to analyze the software code update situation, and can be the branch name of the software code branch. For example, the basic monitoring software code branch and the monitoring software code branch can correspond to codes written in an object-oriented programming language. The above-mentioned software code difference information set can represent the various update methods of the monitoring software code branch relative to the basic monitoring software code branch. The update method may refer to the method in which the software code has an update. The software code difference information may include: the name of the update method, the class name to which the update method belongs, the parameter information corresponding to the update method, and the signature of the method and class.

[0058] In an actual application scenario, the execution subject can determine the software code difference information set corresponding to the monitoring software branch information through the following steps:

[0059] The first step is to determine the code update files of the monitoring software branch information relative to the basic monitoring software code information. The code files in the software code branch that are different from the monitoring software code branch can be determined as code update files through a version control tool to obtain the code update files. For example, the version control tool can be JGit.

[0060] The second step is to determine the update line numbers corresponding to each of the above code update files. The update line numbers corresponding to each of the code update files can be determined by a version control tool.

[0061] The third step is to determine each update mode information as a software code difference information set according to each determined update line number. Each update mode information includes a method name and a class name. Each update mode information can be determined by a parser according to each determined update line number. For example, the parser can be a JavaParser based on an object-oriented programming language.

[0062] Furthermore, for each update method corresponding to the software code difference information set, the monitor server generates link call information corresponding to the update method according to the software code difference information corresponding to the update method in the software code difference information set.

[0063] In some embodiments, for each update method corresponding to the software code difference information set, the monitor server generates link call information corresponding to the update method according to the software code difference information corresponding to the update method in the software code difference information set. Among them, the link call information can be information related to the call relationship of the update method. For example, the link call information can include various method name groups, each method name group includes two method names. Each method name group includes the method name corresponding to the update method. For example, the link call information can include various method name sequences, each method name sequence includes the method name corresponding to the update method, and the previous method calls the method corresponding to the next method name. The method name and class name included in the software code difference information can be input into the encapsulated call chain analysis method to obtain the link call information corresponding to the update method.

[0064] Furthermore, the patient monitor server generates a software code link call graph according to each link call information, and sends the software code link call graph to the patient monitor front end.

[0065] In some embodiments, the patient monitor server generates a software code link call graph based on each link call information, and sends the software code link call graph to the patient monitor front end. The software code link call graph can be a graph that visualizes the call relationship of each update method in a tree structure. For example, the link call information can be input into a packaged link call graph generation method to obtain a software code link call graph.

[0066] Furthermore, in response to receiving the software code link call graph, the patient monitor front end determines each link call information corresponding to the software code link call graph as an expected link table.

[0067] In some embodiments, the patient monitor front end, in response to receiving the software code link call graph, determines each link call information corresponding to the software code link call graph as an expected link table. The patient monitor front end may adopt a static agent to pass in startup parameter information. The startup parameter information may include: the package name of the software code branch to be tested, and each link call information of each update method corresponding to the software code branch. The static agent may be a static agent based on an object-oriented programming language. Then, by calling the premain method, the expected link list may be initialized to the above-mentioned each link call information.

[0068] Furthermore, the patient monitor front end performs instrumentation processing on each application method of the loaded monitoring software branch information in response to determining that the application method belongs to the expected link in the expected link table, so as to store the record information of executing the instrumentation method in the local log file.

[0069] In some embodiments, the patient monitor front end performs a pile processing on each application method of the loaded monitoring software branch information in response to determining that the application method belongs to the expected link in the expected link table, so as to store the record information of executing the pile method in a local log file. Each class and method can be loaded through an implemented converter, and in response to determining that the application method belongs to the expected link in the expected link list, the application method is piled to store the record information of executing the pile method in a log file. ASM can be used for bytecode pile processing to execute related logic before and after the method call. The record information may include: class information, method information, and parameter information.

[0070] Therefore, the call links of each update method can be visualized. Also, because the call link analysis is for each update method, the update method can indicate that the code has been changed, so the scope of the code change points can be analyzed through the link call graph of the update method; in addition, the call link of the update method can be instrumented to analyze the test coverage, thereby improving the test efficiency and reducing the risk of going online.

[0071] Figure 2 A schematic block diagram of the structure of a computer device provided in an embodiment of the present application. The computer device may include: a monitor server 1, a patient monitor front end 2, and a patient monitor 3. For example, the patient monitor 3 may include multiple monitoring devices, for example, monitoring device 301, monitoring device 302, monitoring device 303, and monitoring device 304.

[0072] Among them, the monitor server 1 is directly connected to the patient monitor front end 2; the patient monitor front end 2 is connected to the patient monitor 3 through a Bluetooth connection module; the monitor server 1 is connected to the patient monitor 3 through a Bluetooth connection module. The monitor server 1, the patient monitor front end 2, and the patient monitor 3 are all provided with a memory, and the memory stores the computer program executed by the patient monitor front end, the monitor server, and the patient monitor.

[0073] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system 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 system. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or system including the element.

[0074] The serial numbers of the embodiments of the present application are for description only and do not represent the advantages and disadvantages of the embodiments. The above description is only a specific implementation mode of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present application, and these modifications or replacements should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A patient monitor connection and monitoring method, the method comprising: The patient monitor front end transmits the Bluetooth connection address debugging information to the associated monitor server in response to receiving the Bluetooth connection address debugging information input by the technician in any monitoring device included in the patient monitor, wherein the patient monitor includes a plurality of different types of monitoring devices, each of which is provided with a Bluetooth connection module and a signal enhancement module; In response to receiving the Bluetooth connection address debugging information of the monitoring device in the corresponding patient monitor, the monitor server performs permission identification processing according to the user identification of the technician and the Bluetooth connection address debugging information to obtain a permission identification result; The monitor server determines whether the remote connection server has opened a debugging port corresponding to the debugging information of the Bluetooth connection address; The monitor server sends the proxy connection address information and port information to the patient monitor front end in response to determining that the remote connection server has opened the debugging port corresponding to the Bluetooth connection address debugging information, and the permission identification result indicates that the permission identification is passed; The patient monitor front end receives the proxy connection address information and port information sent by the monitor server, saves the proxy connection address information and the port information as Bluetooth connection address debugging configuration information, and generates a Bluetooth connection remote debugging request according to the Bluetooth connection address debugging configuration information, and sends it to the monitor server; In response to receiving a Bluetooth connection remote debugging request sent by a corresponding patient monitor front end, the monitor server forwards the Bluetooth connection remote debugging request to a debugging port corresponding to the Bluetooth connection address debugging information; In response to determining that the Bluetooth connection debugging of the patient monitor is completed, the monitor service end sends a Bluetooth connection test signal to the patient monitor to test the connection status with the patient monitor.

2. The patient monitor connection and monitoring method according to claim 1, characterized in that: The method further comprises: In response to receiving the Bluetooth connection test signal, the patient monitor adds a time stamp to the Bluetooth connection test signal to obtain a marked Bluetooth connection test signal, and sends the marked Bluetooth connection test signal to the monitor server; In response to receiving the marked Bluetooth connection test signal sent by the patient monitor, the monitor server extracts a time stamp in the marked Bluetooth connection test signal, generates a feedback signal corresponding to the marked Bluetooth connection test signal, and sends the feedback signal to the patient monitor; In response to receiving the feedback signal, the patient monitor adds a time stamp to the feedback signal to obtain a marked feedback signal, and sends the marked feedback signal to the monitor server; In response to receiving the marked feedback signal sent by the patient monitor, the monitor service end generates Bluetooth communication connection delay detection information according to the marked feedback signal and the time stamp in the marked Bluetooth connection test signal.

3. The patient monitor connection and monitoring method according to claim 1, characterized in that: Before the step of forwarding the Bluetooth connection remote debugging request to the debugging port corresponding to the Bluetooth connection address debugging information in response to receiving the Bluetooth connection remote debugging request sent by the front end of the corresponding patient monitor, the method further includes: The patient monitor service end associates the Bluetooth connection address debugging information with the export address information of the patient monitor front end.

4. The patient monitor connection and monitoring method according to claim 3, characterized in that: The step of forwarding the Bluetooth connection remote debugging request to a debugging port corresponding to the Bluetooth connection address debugging information includes: Read the export address information from the Bluetooth connection remote debugging request; Determine the Bluetooth connection address debugging information bound to the export address information; The Bluetooth connection remote debugging request is sent to the debugging port corresponding to the Bluetooth connection address debugging information.

5. The patient monitor connection and monitoring method according to claim 1, characterized in that: The method further comprises: In response to detecting an update test instruction for the monitoring software in the patient monitor, the monitor server receives basic monitoring software code information and monitoring software branch information input by a target technician, and determines a software code difference information set corresponding to the monitoring software branch information, wherein one software code difference information corresponds to one update method; The monitor server generates, for each update method corresponding to the software code difference information set, link call information corresponding to the update method according to the software code difference information corresponding to the update method in the software code difference information set; The patient monitor service end generates a software code link call graph according to each link call information, and sends the software code link call graph to the patient monitor front end.

6. A computer device, wherein: The computer device includes a patient monitor front end, a monitor server, a patient monitor, a memory, and a computer program stored in the memory and executable by the patient monitor front end, the monitor server, and the patient monitor, wherein when the computer program is executed by the patient monitor front end, the monitor server, and the patient monitor, the steps of the method described in any one of claims 1 to 5 are implemented.

Images