Intelligent ward data change monitoring method
By setting up timed tasks and message queue monitoring data changes in the smart ward system, the problems of excessive network load and untimely data updates caused by polling are solved, real-time data updates and system stability are achieved, and medical services are ensured. Efficiency.
Patent Information
- Application Number
- CN202411056703.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-02
- Publication Date
- 2024-11-08
AI Technical Summary
The digital bedside machine data update in the existing smart ward system adopts polling method, resulting in excessive network and server resources being occupied and real-time updates cannot be achieved, affecting system stability and medical service efficiency.
Set up timing tasks on the server, generate data characteristic values through the information digest algorithm, monitor data changes using hash sets and message queues, push data change events to medical equipment, and realize real-time data updates.
It reduces network and server load, realizes real-time data updates, improves system stability and medical service efficiency, and enables medical workers and patients to perceive data changes in a timely manner.
Smart Images

Figure CN118916367A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of smart wards, and in particular to a method for monitoring data changes in smart wards. Background Art
[0002] With the development of science and technology, medical informationization has become an important part of modern medical services. Among them, the smart ward system is a typical medical information system. It uses digital technology to realize intelligent management of wards and improve the quality and efficiency of medical services. In the smart ward system, the digital bedside machine is an important device. It is mainly used to display the patient's basic information, medical order information, vital signs, etc., so that medical staff can understand the patient's condition in time; however, the data update of the digital bedside machine is a key issue. If the data is not updated in time, it may affect the quality and efficiency of medical services; in the existing technology, polling is usually used to achieve data update of the digital bedside machine. Specifically, the medical device will periodically send query requests to the server. After receiving the query request, the server will send the current data to the medical device, thereby realizing the update of medical data. In order to ensure the timeliness of data update, the polling time is usually shortened and the number of requests is increased;
[0003] The polling method used in the prior art has the following problems: 1. The polling method requires a large amount of network and server resources, especially when there are a large number of wards, which may cause excessive network and server loads and affect the stability and reliability of the system; 2. It is impossible to achieve real-time update of data. Each query takes a certain amount of time. If the data changes during the query, the medical device will display outdated data; 3. Medical workers and patients cannot perceive when the data changes; Based on the above, we propose a method for monitoring data changes in smart wards. Summary of the invention
[0004] Based on the technical problems existing in the background technology, the present invention proposes a method for monitoring data changes in a smart ward.
[0005] The present invention proposes a method for monitoring data changes in a smart ward, comprising the following steps:
[0006] S1: Set a scheduled task on the service backend. In actual applications, you can adjust the interval of the scheduled task according to actual needs. At the same time, you can also expand the data table that needs to be monitored according to actual needs.
[0007] S2: First, determine whether to enable data change monitoring. If so, query the table in the data that needs to monitor data changes. The table that needs to monitor data changes is the patient information table, and generate data feature values through the information summary algorithm;
[0008] S3: traverses all records in the data change table that needs to be monitored in S2, obtains the previous data feature value of the record according to the unique identifier, and uses the data unique identifier as the key and the data feature value as the value to store them in a hash set A in the form of a key-value pair, and stores the hash set A in the cache middleware;
[0009] S4: When querying the database table next time, the same information digest algorithm is used to calculate the eigenvalue again, and the eigenvalue is stored in the hash set B, and it is determined whether the same eigenvalue exists in the cache. If so, it is determined whether the eigenvalue is the same. If so, the data and the eigenvalue are stored in the cache. If the same eigenvalue does not exist, it is directly added to the data change list.
[0010] S5: Compare the hash set A in S3 and the hash set B in S4 one by one, obtain the intersection C of the eigenvalue set calculated last time and the eigenvalue set calculated this time, compare the data eigenvalues in the intersection C one by one according to the data unique identifier, and the records with differences are the modified data. The eigenvalue set A minus the intersection C is the deleted data, and the eigenvalue set B minus the intersection C is the newly added data. The deleted data, newly added data, and modified data are all changed data.
[0011] S6: For the changed data, obtain the list of medical devices that need to be pushed according to the type of data, and push the corresponding data change event to the medical device through the message queue. The medical device will perform corresponding business processing according to the type of data change event.
[0012] Preferably, in S2, the patient information table contains the basic information of the patient, including name, age, gender and medical record number, etc., and the unique identifier of the data in S3 may be the case number.
[0013] Preferably, in S6, the types of data change events include patient information change events and device information change events, and the data change events to be pushed and the devices to be pushed can be modified according to actual needs.
[0014] Preferably, in S6, the specific process of processing the data change event received by the medical device is as follows:
[0015] S601: First, determine whether the medical device has just been turned on. If it has just been turned on, initialize the calling service interface. If not, directly receive the message of the data change event through the medical device monitoring message queue;
[0016] S602: Call different interfaces to perform business processing according to the event type, and perform different business processing;
[0017] S603: Update the data or display and remind personnel in the interface, so that the staff and patients can directly perceive the changes in medical data.
[0018] Preferably, in S2, the information digest algorithm is the MD5 information digest algorithm.
[0019] Preferably, in the S3, the cache middleware is a Redis remote dictionary server.
[0020] Compared with the prior art, the present invention has the following beneficial effects:
[0021] 1. By monitoring data changes in the service backend, when data changes, data change events are pushed through the message queue. This method avoids frequent polling operations, thereby reducing the load on the network and server and improving the stability and reliability of the system;
[0022] 2. By monitoring the message queue of medical equipment, calling the interface for different data change events received and performing different business processing, real-time data update can be achieved, avoiding the problem of digital bedside machine displaying expired data when data changes during query. In addition, while ensuring timely data update, unnecessary network requests are reduced, which greatly reduces the system's requirements for network bandwidth and server performance, thereby reducing deployment costs;
[0023] 3. By displaying and reminding updated data in the interface, medical workers and patients can perceive changes in medical data in a timely manner, thereby improving medical outcomes;
[0024] The smart ward data change monitoring method proposed in the present invention can call interfaces for different data change events received by monitoring the message queue, perform different business processing, and realize real-time data update, avoiding frequent polling operations, thereby reducing the load on the network and server, and improving the stability and reliability of the system. In addition, through real-time update, the problem of data changes during query and the digital bedside machine displaying expired data is avoided. In addition, when medical data changes, medical workers and patients can perceive it in time, thereby improving medical effectiveness. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] Figure 1 This is a flow chart of a smart ward data change monitoring method proposed by the present invention;
[0026] Figure 2 The present invention provides a flowchart for processing data change events received by medical equipment in a smart ward data change monitoring method. DETAILED DESCRIPTION
[0027] The present invention will be further explained below in conjunction with specific embodiments.
[0028] Example
[0029] Reference Figure 1-2 This embodiment proposes a method for monitoring data changes in a smart ward, comprising the following steps:
[0030] S1: Set a scheduled task on the service backend. In actual applications, you can adjust the interval of the scheduled task according to actual needs. At the same time, you can also expand the data table that needs to be monitored according to actual needs.
[0031] S2: First, determine whether to enable data change monitoring. If so, query the table in the data that needs to monitor data changes. The table that needs to monitor data changes is the patient information table, and generate data feature values through an information digest algorithm, where the information digest algorithm is an MD5 information digest algorithm.
[0032] The patient information form contains the patient's basic information, including name, age, gender, and medical record number;
[0033] S3: traverse all records in the data change table that needs to be monitored in S2, obtain the previous data feature value of the record according to the unique identifier, and use the data unique identifier as the key and the data feature value as the value to store them in a hash set A in the form of key-value pairs, and store the hash set A in the cache middleware, where the cache middleware is a Redis remote dictionary server;
[0034] Taking the patient information table as an example, the unique identifier of the data may be the case number;
[0035] S4: When querying the database table next time, the same information digest algorithm is used to calculate the eigenvalue again, and the eigenvalue is stored in the hash set B, and it is determined whether the same eigenvalue exists in the cache. If so, it is determined whether the eigenvalue is the same. If so, the data and the eigenvalue are stored in the cache. If the same eigenvalue does not exist, it is directly added to the data change list.
[0036] S5: Compare the hash set A in S3 and the hash set B in S4 one by one, obtain the intersection C of the eigenvalue set calculated last time and the eigenvalue set calculated this time, compare the data eigenvalues in the intersection C one by one according to the data unique identifier, and the records with differences are the modified data. The eigenvalue set A minus the intersection C is the deleted data, and the eigenvalue set B minus the intersection C is the newly added data. The deleted data, newly added data, and modified data are all changed data.
[0037] S6: For the changed data, according to the type of data, obtain the list of medical devices that need to be pushed, and push the corresponding data change event to the medical device through the message queue, where the types of data change events include patient information change events and device information change events. The data change events and devices that need to be pushed can be modified according to actual needs;
[0038] Medical equipment will perform corresponding business processing according to the type of data change event;
[0039] The specific process of handling medical equipment receiving data change events is as follows:
[0040] S601: First, determine whether the medical device has just been turned on. If it has just been turned on, initialize the calling service interface. If not, directly receive the message of the data change event through the medical device monitoring message queue;
[0041] S602: Call different interfaces to perform business processing according to the event type, and perform different business processing;
[0042] S603: Update the data or display and remind personnel in the interface, so that the staff and patients can directly perceive the changes in medical data;
[0043] This embodiment can call the interface for different data change events received by monitoring the message queue and perform different business processing, thereby realizing real-time data update and avoiding frequent polling operations, thereby reducing the load on the network and server and improving the stability and reliability of the system. In addition, through real-time update, it avoids the problem of data changing during the query period and the digital bedside machine displaying expired data. In addition, when medical data changes, medical workers and patients can perceive it in time, thereby improving medical effectiveness.
[0044] The above description is only a preferred specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can make equivalent replacements or changes according to the technical scheme and inventive concept of the present invention within the technical scope disclosed by the present invention, which should be covered by the protection scope of the present invention.
Claims
1. A method for monitoring data changes in a smart ward, characterized in that: The following steps are involved: S1: Set a scheduled task on the service backend. In actual applications, you can adjust the interval of the scheduled task according to actual needs. At the same time, you can also expand the data table that needs to be monitored according to actual needs. S2: First, determine whether to enable data change monitoring. If so, query the table in the data that needs to monitor data changes. The table that needs to monitor data changes is the patient information table, and generate data feature values through the information summary algorithm; S3: traverses all records in the data change table that needs to be monitored in S2, obtains the previous data feature value of the record according to the unique identifier, and uses the data unique identifier as the key and the data feature value as the value to store them in a hash set A in the form of a key-value pair, and stores the hash set A in the cache middleware; S4: When querying the database table next time, the same information digest algorithm is used to calculate the eigenvalue again, and the eigenvalue is stored in the hash set B, and it is determined whether the same eigenvalue exists in the cache. If so, it is determined whether the eigenvalue is the same. If so, the data and the eigenvalue are stored in the cache. If the same eigenvalue does not exist, it is directly added to the data change list. S5: Compare the hash set A in S3 and the hash set B in S4 one by one, obtain the intersection C of the eigenvalue set calculated last time and the eigenvalue set calculated this time, compare the data eigenvalues in the intersection C one by one according to the data unique identifier, and the records with differences are the modified data. The eigenvalue set A minus the intersection C is the deleted data, and the eigenvalue set B minus the intersection C is the newly added data. The deleted data, newly added data, and modified data are all changed data. S6: For the changed data, obtain the list of medical devices that need to be pushed according to the type of data, and push the corresponding data change event to the medical device through the message queue. The medical device will perform corresponding business processing according to the type of data change event.
2. A method for monitoring data changes in a smart ward according to claim 1, characterized in that: In S2, the patient information table contains the basic information of the patient, including name, age, gender and medical record number, and the data unique identifier in S3 can be the case number.
3. A method for monitoring data changes in a smart ward according to claim 1, characterized in that: In S6, the types of data change events include patient information change events and device information change events, and the data change events to be pushed and the devices to be pushed can be modified according to actual needs.
4. According to claim 1, a smart ward data change monitoring method is characterized in that: In S6, the specific process of processing the data change event received by the medical device is as follows: S601: First, determine whether the medical device has just been turned on. If it has just been turned on, initialize the calling service interface. If not, directly receive the message of the data change event through the medical device monitoring message queue; S602: Call different interfaces to perform business processing according to the event type, and perform different business processing; S603: Update the data or display and remind personnel in the interface, so that the staff and patients can directly perceive the changes in medical data.
5. According to claim 1, a smart ward data change monitoring method is characterized in that: In S2, the information digest algorithm is the MD5 information digest algorithm.
6. A method for monitoring data changes in a smart ward according to claim 1, characterized in that: In the S3, the cache middleware is a Redis remote dictionary server.
Citation Information
Patent Citations
Intelligent queuing mode and system based on event bus
CN110895848A
Database table data comparison method and device based on MD5
CN112948389A
Method, system and device for processing medical data of patient and storage medium
CN114694784A
Streaming data monitoring and responding method, terminal equipment and storage medium
CN116319399A
Smart hospital care system
US20130275148A1
Cited By
Data processing method, device and equipment
CN119722181A
A data processing method, apparatus and device
CN119722181B
