Intelligent health record reminding system based on unified client

Abstract

The invention relates to medical health information, in particular to an intelligent health record reminding system based on a unified client, which develops an intelligent pushing mechanism based on user behavior analysis in the aspect of intelligent reminding, and triggers non-interference bubble reminding at a proper time by monitoring the working state of a doctor in real time. Through a three-stage penetration type interaction mode of bubble abstract-file overview-file details, the reminding processing efficiency of a doctor is effectively improved, and the workflow interruption rate is greatly reduced; in the aspect of health archive content, a doctor can directly open a health archive overview page of a main window and check archive overview information of a patient health archive by clicking a bubble popup window, so that the doctor is helped to clearly and quickly know key medical history of a patient, diagnosis and treatment time is effectively saved, and the doctor is assisted in clinical decision making; the technical scheme provided by the invention can effectively overcome the defect that the health archive of the patient is difficult to efficiently obtain in the prior art.

Description

Technical Field

[0001] This invention relates to medical and health information, specifically to a smart health record reminder system based on a unified client. Background Technology

[0002] The development of healthcare informatization is currently in a phase of rapid growth, with various health management applications and medical information systems (such as Hospital Information Systems (HIS), Clinical Information Systems (CIS), Medical Image Storage and Transmission Systems (PACS), and Electronic Medical Records (EMR)) experiencing explosive growth. However, due to issues such as inconsistent data standards and closed interfaces between systems, the sharing and integration of medical information still faces significant challenges, mainly manifested in the following ways:

[0003] 1) The phenomenon of information silos is serious: the internal systems of medical institutions usually operate independently and data is difficult to communicate. Although regional medical information systems can achieve some data sharing, the coverage is limited and the efficiency of cross-institutional data flow is low. At present, the phenomenon of "information silos" between various application systems within medical institutions is still obvious, and the construction of medical informatization cannot effectively meet the needs of doctors and patients.

[0004] 2) Increased workload for doctors: Because patient health data is scattered across different systems, doctors need to manually query and integrate information. Taking electronic medical records as an example, because patient health data cannot be efficiently transferred between different systems, doctors need to spend a lot of time manually querying and organizing patient information during the diagnosis and treatment process. On average, each doctor wastes more than 1 hour per day, which seriously affects the efficiency of diagnosis and treatment. At the same time, clinical decision-making lacks complete and real-time support from patient health records, which increases medical risks.

[0005] 3) Existing integration solutions are inadequate: Some solutions only achieve simple aggregation at the application level, lacking in-depth data fusion, intelligent analysis and reminder capabilities, and lack a unified and efficient interaction method. Doctors still need to switch frequently between different systems and cannot quickly obtain key health information. Summary of the Invention

[0006] (a) Technical problems to be solved

[0007] In view of the above-mentioned shortcomings of the existing technology, the present invention provides a health record intelligent reminder system based on a unified client, which can effectively overcome the shortcomings of the existing technology in that it is difficult to efficiently obtain patient health records.

[0008] (II) Technical Solution

[0009] To achieve the above objectives, the present invention provides the following technical solution:

[0010] A health record intelligent reminder system based on a unified client includes a data layer, a service layer, a middleware layer, and an application layer.

[0011] The service layer includes:

[0012] User authentication service supports multi-factor authentication (MFA) and single sign-on (SSO), and is compatible with OIDC / OAuth 2.0 protocol;

[0013] The data access service, acting as an access gateway for medical institutions, provides data format conversion and asynchronous queue buffering functions, and is compatible with multiple protocols including RESTful, HL7, and FHIR.

[0014] The data processing service uses the CRDT algorithm to ensure distributed data consistency and supports real-time batch processing and asynchronous tasks.

[0015] The reminder engine service is based on time / event triggering rules and supports dynamic priority queues and deduplication mechanisms.

[0016] The notification push service uses Electron to call the system's native API to implement unified desktop bubble reminders on the client side, pushing patient health records.

[0017] Basic services provide common capabilities including logging, messaging, and monitoring;

[0018] The application layer includes:

[0019] A unified client, based on the Electron+React technology stack to achieve cross-platform compatibility, integrates WebAssembly to accelerate the core rendering process, improves performance, supports offline mode, and ensures the availability of basic functions through local caching;

[0020] On the storage side, it provides block upload / download functionality for files and data, interfaces with OSS object storage, and supports breakpoint resume and encrypted transmission;

[0021] The back-end management platform, developed based on React+Ant Design, implements operation and maintenance functions including service monitoring, log querying, and user permission management.

[0022] Preferably, the data layer includes:

[0023] The database uses a MySQL cluster as the core storage and a Redis cluster to handle high-concurrency read and write operations.

[0024] OSS object storage stores unstructured data;

[0025] Logs and analytics are handled by Filebeat+ELK for unified log collection, Prometheus for monitoring service metrics, and SkyWalking for tracing the process.

[0026] Preferably, the middleware layer includes:

[0027] A unified API gateway, implemented based on Spring Cloud Gateway, provides unified management of microservice interfaces, integrates authentication, rate limiting, and circuit breaking capabilities, supports OIDC / OAuth 2.0 protocol authentication, and connects to user authentication services;

[0028] Multi-level caching employs a combination of local and distributed caching, reducing database pressure through cache preheating and consistent hashing.

[0029] Preferably, the data access service and data processing service in the service layer constitute a multi-source data integration unit, and the functions of the multi-source data integration unit include:

[0030] Develop standardized data access APIs for different medical institutions, supporting multiple protocols including RESTful, HL7, and FHIR;

[0031] Develop adapters for different data sources to convert heterogeneous data into a unified format;

[0032] Establish a data caching queue to ensure stable data transmission under high concurrency;

[0033] Build a rule base and define data cleaning strategies;

[0034] It uses a distributed database with patient ID shards for storage, supporting fast queries;

[0035] Establish a time-series database to store dynamic data;

[0036] The health record overview page is designed to visually display structured health history, recent medication records arranged on a timeline from recent to distant dates, recent medical information arranged on a timeline from recent to distant dates, and data including a trend chart of changes in vital signs.

[0037] Preferably, the defined data cleaning strategy includes deduplication, completion, and logical verification. Deduplication involves merging duplicate records based on key fields such as patient ID and consultation time. Completion involves automatically filling in missing fields or marking them as needing completion through associated data.

[0038] Preferably, the reminder engine service and notification push service in the service layer constitute an intelligent reminder generation and push unit, and the functions of the intelligent reminder generation and push unit include:

[0039] Deploy lightweight agents in the outpatient and inpatient physician workstations of the Hospital Information System (HIS) to monitor patient admission events in real time;

[0040] When a doctor selects a patient, the Agent sends a query request to the unified client using the patient ID to check if a health record exists. If a health record exists, the alert engine service is triggered to perform matching calculations and extract the patient's medical history and infectious disease history from the health record as key alert content.

[0041] The doctor workstation uses a unified client to pop up bubbles, supports flashing reminders, and provides dynamic and contextualized bubble reminder services to guide doctors to view the information. This achieves a "one screen, three views" interactive mode, enabling intelligent risk warnings and real-time decision support. Doctors can quickly understand the patient's key medical history through the bubble pop-up, improving diagnostic and treatment efficiency and reducing medical risks. The system ensures sub-second response through a microsecond-level event bus and edge computing nodes.

[0042] In the "one screen, three views" interactive mode, the three views include a bubble summary, a file overview, and file details.

[0043] Preferably, the data processing service and basic service in the service layer constitute a health record visualization unit, and the functions of the health record visualization unit include:

[0044] Doctors can click on the pop-up window to directly open the health record overview page in the main window and view the patient's health record overview information, including structured health history, recent medication records displayed on a timeline from recent to distant, recent diagnosis and treatment information displayed on a timeline from recent to distant, and data such as a trend chart of changes in vital signs, to help doctors quickly understand the patient's key medical history;

[0045] Doctors can click the "View Health Record Details" button on the health record overview page to jump to the health record details page, achieving a smooth transition from a key medical history overview to health details query. By initially presenting fragmented data in a centralized manner, it provides a complete path of "summary analysis - panoramic verification" to assist doctors in clinical decision-making.

[0046] (III) Beneficial Effects

[0047] Compared with existing technologies, the intelligent health record reminder system based on a unified client provided by this invention has the following beneficial effects:

[0048] 1) In terms of data integration, existing systems mostly adopt simple application entry aggregation, which can only achieve surface-level system docking. However, this invention achieves semantic-level integration of underlying medical information through a deep data fusion engine based on the FHIR / HL7 standard.

[0049] 2) Regarding intelligent reminders, most existing systems do not have health record reminder functions. However, this invention innovatively develops an intelligent push mechanism based on user behavior analysis. By monitoring the doctor's work status in real time, it triggers non-intrusive bubble reminders (including key medical histories such as disease history and infectious disease history in the patient's health record) at appropriate times. Through a three-level penetrating interactive mode of "bubble summary - record overview - record details", it effectively improves the efficiency of doctors in handling reminders and significantly reduces the workflow interruption rate.

[0050] 3) Regarding the content of health records, most existing systems do not have a health record overview function. However, this invention innovatively develops a health record overview page in the main window that doctors can directly open by clicking on the pop-up bubble. This allows doctors to view the overview information of the patient's health record, helping them to clearly and quickly understand the patient's key medical history, effectively saving treatment time and assisting doctors in clinical decision-making. Attached Figure Description

[0051] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are merely some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without any creative effort.

[0052] Figure 1 This is a schematic diagram of the system of the present invention;

[0053] Figure 2 This is a functional diagram of the multi-source data integration unit in this invention;

[0054] Figure 3 This is a functional diagram of the intelligent reminder generation and push unit in this invention;

[0055] Figure 4 This is a functional diagram of the health record visualization unit in this invention. Detailed Implementation

[0056] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0057] A health record intelligent reminder system based on a unified client, such as Figure 1 As shown, it includes a data layer, a service layer, a middleware layer, and an application layer;

[0058] The data layer includes:

[0059] The database uses a MySQL cluster (master-slave replication + database sharding) as the core storage, and a Redis cluster to handle high-concurrency read and write operations.

[0060] OSS object storage stores unstructured data (such as images, documents, etc.);

[0061] Logs and analytics: unified log collection via Filebeat+ELK, Prometheus monitoring of service metrics, and SkyWalking tracing of log paths.

[0062] The service layer includes:

[0063] User authentication service supports multi-factor authentication (MFA) and single sign-on (SSO), and is compatible with OIDC / OAuth 2.0 protocol;

[0064] The data access service, acting as a gateway for medical institutions, provides data format conversion and asynchronous queue (RocketMQ) buffering functions, and is compatible with multiple protocols including RESTful, HL7, and FHIR.

[0065] The data processing service uses the CRDT algorithm to ensure distributed data consistency and supports real-time batch processing (Flink) and asynchronous tasks (XXL-JOB).

[0066] The reminder engine service is based on time / event triggering rules (Quartz) and supports dynamic priority queues and deduplication mechanisms.

[0067] The notification push service uses Electron to call the system's native API to implement unified desktop bubble reminders on the client side, pushing patient health records.

[0068] Basic services provide common capabilities including logging, messaging, and monitoring;

[0069] The middleware layer includes:

[0070] A unified API gateway, implemented based on Spring Cloud Gateway, provides unified management of microservice interfaces, integrates authentication, rate limiting, and circuit breaker (Sentinel) capabilities, supports OIDC / OAuth 2.0 protocol authentication, and connects to user authentication services;

[0071] Multi-level caching employs a combination of local caching (Caffeine) and distributed caching (Redis), reducing database pressure through cache preheating and consistent hashing;

[0072] The application layer includes:

[0073] A unified client, based on the Electron+React technology stack to achieve cross-platform compatibility (Windows first), integrates WebAssembly to accelerate the core rendering process and improve performance, supports offline mode, and ensures the availability of basic functions through local caching (IndexedDB);

[0074] On the storage side, it provides block upload / download functionality for files and data, interfaces with OSS object storage, and supports breakpoint resume and encrypted transmission;

[0075] The back-end management platform, developed based on React+Ant Design, implements operation and maintenance functions including service monitoring, log querying, and user permission management.

[0076] ① The data access service and data processing service in the service layer constitute a multi-source data integration unit, such as Figure 2 As shown, the functions of the multi-source data integration unit include:

[0077] Develop standardized data access APIs for different medical institutions (such as hospitals, community clinics, third-party testing institutions, etc.), supporting multiple protocols including RESTful, HL7, and FHIR;

[0078] Develop adapters for different data sources (such as HIS, LIS, PACS, etc.) to convert heterogeneous data into a unified format (such as JSON Schema);

[0079] Establish a data caching queue (such as Kafka or RabbitMQ) to ensure stable data transmission under high concurrency;

[0080] Build a rule base and define data cleaning strategies;

[0081] It uses a distributed database (such as MongoDB + Elasticsearch) to shard the data by patient ID, supporting fast querying;

[0082] Establish a time-series database (such as InfluxDB) to store dynamic data (such as continuous blood pressure, blood glucose, and BMI monitoring records);

[0083] The health record overview page is designed to visually display a structured health history (including past medical history, allergy history, surgical history, infectious disease history, and family history), recent medication records (including medication time, drug name, and drug specifications) displayed on a timeline from recent to distant, recent medical information (including consultation time, hospital, department, and diagnosed disease) displayed on a timeline from recent to distant, and data including trend graphs of vital signs (including blood pressure trend graph, blood glucose trend graph, and BMI change curve).

[0084] Specifically, the data cleaning strategy is defined to include deduplication, completion, and logical verification. Deduplication involves merging duplicate records based on key fields such as patient ID and consultation time. Completion involves automatically filling in or marking missing fields (such as allergy history, family history, etc.) by linking data.

[0085] ② The reminder engine service and notification push service in the service layer constitute the intelligent reminder generation and push unit, such as Figure 3 As shown, the functions of the intelligent reminder generation and push unit include:

[0086] Deploy lightweight agents in the outpatient and inpatient physician workstations of the Hospital Information System (HIS) to monitor patient reception events in real time (such as successful registration, access to medical records, etc.);

[0087] When a doctor selects a patient, the Agent sends a query request to the unified client using the patient ID to check if a health record exists. If a health record exists, the alert engine service is triggered to perform matching calculations and extract the patient's medical history (such as hypertension) and infectious disease history (such as hepatitis B) from the health record as key alert content.

[0088] The doctor workstation uses a unified client to pop up bubbles, supporting flashing reminders (lasting until the doctor clicks), providing dynamic and contextualized bubble reminder services to guide doctors to view the information, realizing an interactive mode of "one screen, three views", achieving intelligent risk warning and real-time decision support. Doctors can quickly understand the patient's key medical history through the bubble pop-up, improving diagnosis and treatment efficiency and reducing medical risks. The system ensures sub-second response through a microsecond-level event bus and edge computing nodes.

[0089] In the "one screen, three views" interactive mode, the three views include a bubble summary, a file overview, and file details.

[0090] In the technical solution of this application, the pop-up window displays the following format: "Patient XXX has a health record, past medical history: hypertension; history of infectious diseases: hepatitis B".

[0091] ③ Data processing services and basic services in the service layer constitute the health record visualization unit, such as Figure 4 As shown, the functions of the health record visualization unit include:

[0092] Doctors can click on the pop-up window to directly open the health record overview page in the main window and view the patient's health record overview information, including structured health history, recent medication records displayed on a timeline from recent to distant, recent diagnosis and treatment information displayed on a timeline from recent to distant, and data such as a trend chart of changes in vital signs, to help doctors quickly understand the patient's key medical history;

[0093] Doctors can click the "View Health Record Details" button on the health record overview page to jump to the health record details page, achieving a smooth transition from a key medical history overview to health details query. By initially presenting fragmented data in a centralized manner, it provides a complete path of "summary analysis - panoramic verification" to assist doctors in clinical decision-making.

[0094] The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions will not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A health record intelligent reminder system based on a unified client, characterized in that: It includes the data layer, service layer, middleware layer, and application layer; The service layer includes: User authentication service supports multi-factor authentication (MFA) and single sign-on (SSO), and is compatible with OIDC / OAuth 2.0 protocol; The data access service, acting as an access gateway for medical institutions, provides data format conversion and asynchronous queue buffering functions, and is compatible with multiple protocols including RESTful, HL7, and FHIR. The data processing service uses the CRDT algorithm to ensure distributed data consistency and supports real-time batch processing and asynchronous tasks. The reminder engine service is based on time / event triggering rules and supports dynamic priority queues and deduplication mechanisms. The notification push service uses Electron to call the system's native API to implement unified desktop bubble reminders on the client side, pushing patient health records. Basic services provide common capabilities including logging, messaging, and monitoring; The application layer includes: A unified client, based on the Electron+React technology stack to achieve cross-platform compatibility, integrates WebAssembly to accelerate the core rendering process, improves performance, supports offline mode, and ensures the availability of basic functions through local caching; On the storage side, it provides block upload / download functionality for files and data, interfaces with OSS object storage, and supports breakpoint resume and encrypted transmission; The back-end management platform, developed based on React+Ant Design, implements operation and maintenance functions including service monitoring, log querying, and user permission management.

2. The health record intelligent reminder system based on a unified client according to claim 1, characterized in that: The data layer includes: The database uses a MySQL cluster as the core storage and a Redis cluster to handle high-concurrency read and write operations. OSS object storage stores unstructured data; Logs and analytics are handled by Filebeat+ELK for unified log collection, Prometheus for monitoring service metrics, and SkyWalking for tracing the process.

3. The health record intelligent reminder system based on a unified client according to claim 2, characterized in that: The middleware layer includes: A unified API gateway, implemented based on Spring Cloud Gateway, provides unified management of microservice interfaces, integrates authentication, rate limiting, and circuit breaking capabilities, supports OIDC / OAuth 2.0 protocol authentication, and connects to user authentication services; Multi-level caching employs a combination of local and distributed caching, reducing database pressure through cache preheating and consistent hashing.

4. The intelligent health record reminder system based on a unified client according to claim 3, characterized in that: The data access service and data processing service in the service layer constitute a multi-source data integration unit, and the functions of the multi-source data integration unit include: Develop standardized data access APIs for different medical institutions, supporting multiple protocols including RESTful, HL7, and FHIR; Develop adapters for different data sources to convert heterogeneous data into a unified format; Establish a data caching queue to ensure stable data transmission under high concurrency; Build a rule base and define data cleaning strategies; It uses a distributed database with patient ID shards for storage, supporting fast queries; Establish a time-series database to store dynamic data; The health record overview page is designed to visually display structured health history, recent medication records arranged on a timeline from recent to distant dates, recent medical information arranged on a timeline from recent to distant dates, and data including a trend chart of changes in vital signs.

5. The intelligent health record reminder system based on a unified client according to claim 4, characterized in that: The defined data cleaning strategy includes deduplication, completion, and logical verification. Deduplication involves merging duplicate records based on key fields such as patient ID and visit time. Completion involves automatically filling in missing fields or marking them as needing completion through associated data.

6. The health record intelligent reminder system based on a unified client according to claim 4, characterized in that: The reminder engine service and notification push service in the service layer constitute the intelligent reminder generation and push unit. The functions of the intelligent reminder generation and push unit include: Deploy lightweight agents in the outpatient and inpatient physician workstations of the Hospital Information System (HIS) to monitor patient admission events in real time; When a doctor selects a patient, the Agent sends a query request to the unified client using the patient ID to check if a health record exists. If a health record exists, the alert engine service is triggered to perform matching calculations and extract the patient's medical history and infectious disease history from the health record as key alert content. The doctor workstation uses a unified client to pop up bubbles, supports flashing reminders, and provides dynamic and contextualized bubble reminder services to guide doctors to view the information, realizing an interactive mode of "one screen with three views". It enables intelligent risk warning and real-time decision support. Doctors can quickly understand the patient's key medical history through the bubble pop-up, improve diagnosis and treatment efficiency, and reduce medical risks. The system ensures sub-second response through a microsecond-level event bus and edge computing nodes. In the "one screen, three views" interactive mode, the three views include a bubble summary, a file overview, and file details.

7. The intelligent health record reminder system based on a unified client according to claim 6, characterized in that: The data processing services and basic services in the service layer constitute the health record visualization unit, and the functions of the health record visualization unit include: Doctors can click on the pop-up window to directly open the health record overview page in the main window and view the patient's health record overview information, including structured health history, recent medication records displayed on a timeline from recent to distant, recent diagnosis and treatment information displayed on a timeline from recent to distant, and data such as a trend chart of changes in vital signs, to help doctors quickly understand the patient's key medical history; Doctors can click the "View Health Record Details" button on the health record overview page to jump to the health record details page, achieving a smooth transition from a key medical history overview to health details query. By initially presenting fragmented data in a centralized manner, it provides a complete path of "summary analysis - panoramic verification" to assist doctors in clinical decision-making.

Images