Multi-role collaborative management system based on RBAC+HIS synchronization

Abstract

The present invention discloses a multi-role collaborative management system based on RBAC+HIS synchronization, including: a role authority management module, which constructs a static role authority baseline based on the RBAC model, and associates the real-time organizational structure data of the HIS system through a dynamic rule engine to generate a multi-level role authority tree; a data synchronization middleware, which uses an API gateway to realize one-way data push between the HIS system and the psychological assessment platform, contains a field-level encryption unit and an incremental data verification unit, and supports the isolated transmission of patient medical records, medical orders and assessment tasks by ward; a multi-terminal collaborative engine, which realizes the authority mapping of doctor workstations, mobile nursing terminals and patient self-service terminals through distributed session management, and has a built-in conflict detection mechanism, which triggers a secondary authentication process when a cross-ward operation is detected. The invention realizes dynamic authority management, ensures data security transmission and multi-terminal collaboration, strengthens audit tracing, improves diagnosis and treatment efficiency, and ensures business continuity when the system is abnormal.

Description

Technical Field

[0001] The present invention relates to the field of collaborative management of medical rights, and in particular to a multi-role collaborative management system based on RBAC+HIS synchronization. Background Art

[0002] In the healthcare information technology sector, traditional RBAC-based permission management systems generally lack dynamic adaptability. Static role configurations struggle to cope with the complex organizational structure of multiple departments and wards in hospitals, leading to permission adjustment cycles lasting several weeks and the risk of medical data leaks due to manual configuration errors.

[0003] Although existing technologies attempt to achieve HIS system data synchronization through API interfaces, they generally adopt a full data push mode, which not only takes up a large amount of network bandwidth, but also leads to the risk of patient privacy leakage due to the lack of field-level encryption.

[0004] In addition, when multiple terminals are operating collaboratively, doctors need to log in and authenticate repeatedly between different systems, which seriously affects the efficiency of diagnosis and treatment. Traditional solutions also have obvious defects in authority auditing. Cross-system operation logs are isolated from each other, making it difficult to trace the source of data leakage. For this reason, a multi-role collaborative management system based on RBAC+HIS synchronization is proposed. Summary of the Invention

[0005] In view of the deficiencies of the prior art, the present invention provides a multi-role collaborative management system based on RBAC+HIS synchronization to solve the problems raised in the above background technology.

[0006] To achieve the above objectives, the present invention provides the following technical solution: a multi-role collaborative management system based on RBAC+HIS synchronization, comprising:

[0007] The role permission management module builds a static role permission baseline based on the RBAC model and associates it with the real-time organizational structure data of the HIS system through a dynamic rule engine to generate a multi-level role permission tree;

[0008] Data synchronization middleware uses an API gateway to implement one-way data push between the HIS system and the psychological assessment platform. It includes field-level encryption units and incremental data verification units, and supports the isolated transmission of patient medical records, medical orders, and assessment tasks by ward.

[0009] The multi-terminal collaboration engine uses distributed session management to achieve permission mapping between doctor workstations, mobile nursing terminals, and patient self-service terminals. It also has a built-in conflict detection mechanism that triggers a secondary authentication process when cross-ward operations are detected.

[0010] The authority audit center records role change logs and associates them with HIS system operation logs with timestamps to generate a three-dimensional audit report that includes operation traces, data flows, and risk levels;

[0011] The emergency management module automatically switches to the locally cached role permission configuration when an HIS system anomaly is detected, and performs permission downgrade processing based on the preset department priority rules;

[0012] Among them, the role authority management module establishes a bidirectional mapping relationship between the ward code and the HIS system department code, the data synchronization middleware adopts the AES-256 segmented encryption algorithm at the transport layer, and the multi-terminal collaboration engine supports intelligent switching between the WebSocket protocol and HTTP long polling;

[0013] In the role and permission management module, if there are compatibility issues between the RBAC model and the organizational structure data of the HIS system, an intermediate adapter layer can be developed to parse the JSON format data returned by the HIS and convert it into a permission configuration format that can be recognized by the RBAC model, ensuring the effective integration of the static role and permission baseline and the dynamic organizational structure data.

[0014] The role and authority management module combines the RBAC model with the dynamic data of the HIS system to achieve flexible configuration and real-time update of role permissions, enhancing the system's adaptability to complex medical environments. The data synchronization middleware uses API gateway and field-level encryption technology to ensure the security and integrity of patient data during transmission. At the same time, it supports isolated transmission by ward, improving the efficiency and accuracy of data processing. The multi-terminal collaboration engine realizes seamless collaboration among doctors, nurses and patient terminals through distributed session management. The built-in conflict detection and secondary authentication mechanism effectively prevents authority abuse and data leakage. The authority audit center provides traceable audit basis for system security through detailed log records and correlation analysis. The addition of the emergency management module further improves the robustness of the system, ensuring that basic business operations can be maintained when the HIS system is abnormal.

[0015] Preferably, the dynamic rule engine includes:

[0016] The rule configuration interface supports visual editing of permission inheritance rules based on the tree structure of the hospital's organizational structure;

[0017] The rule parser converts the configured rules into executable scripts and matches them in real time with the JSON format organization data returned by the HIS system;

[0018] The conflict resolution unit, when detecting a conflict between RBAC baseline permissions and HIS dynamic data, conducts arbitration based on the preset medical service priority table;

[0019] Regarding the specific implementation of the conflict resolution unit in the dynamic rule engine, when a conflict is detected between the RBAC baseline permissions and HIS dynamic data, the system first reads the preset medical service priority table, which lists the priority order of various medical services in detail. Then, the system matches the priority table based on the type of medical service involved in the conflict and automatically selects the business rule with the higher priority as the arbitration basis, thereby resolving the permission conflict and ensuring the smooth operation of medical services.

[0020] The dynamic rule engine realizes the flexible editing and efficient execution of the hospital organizational structure permission inheritance rules through the collaborative work of the rule configuration interface, rule parser and conflict resolution unit. The tree structure visual editing function of the rule configuration interface makes the adjustment of permission inheritance rules intuitive and convenient, reducing management costs. The rule parser converts the configuration rules into executable scripts and matches them with the JSON format organization data returned by the HIS system in real time, ensuring the accuracy and timeliness of permission allocation. When the conflict resolution unit detects a conflict between RBAC baseline permissions and HIS dynamic data, it can arbitrate according to the preset medical business priority table, effectively avoiding the impact of permission conflicts on medical business and ensuring the efficiency and safety of hospital operations.

[0021] Preferably, the field-level encryption unit includes:

[0022] Encryption policy manager, dynamically selecting AES-256 or national encryption SM4 algorithm based on the sensitivity level of patient data;

[0023] The key distribution submodule pushes temporary session keys to each terminal through the hospital intranet security channel;

[0024] Encryption performance optimizer, which uses a cache pre-encryption mechanism for frequently accessed fields;

[0025] In the field-level encryption unit, the encryption policy manager automatically determines the sensitivity level of patient data (such as ID number and diagnosis information) based on its built-in sensitivity assessment algorithm, and selects AES-256 or the national encryption SM4 algorithm for encryption accordingly. The key distribution submodule uses the hospital's existing VPN or encrypted tunnel technology to establish a secure channel, encrypts the generated temporary session key, and pushes it to each terminal. The encryption performance optimizer analyzes historical access records to identify frequently accessed fields, pre-encrypts them when the system is idle, and stores them in the local cache to reduce the computational burden of real-time encryption.

[0026] The field-level encryption unit ensures the security of patient data at different sensitivity levels by dynamically selecting encryption algorithms, meeting compliance requirements while taking into account encryption efficiency. It uses the hospital's intranet secure channel to distribute keys, effectively preventing the risk of key leakage during transmission. At the same time, the encryption performance optimizer significantly improves the encryption speed of high-frequency access fields through a cache pre-encryption mechanism, reducing system latency and improving user experience.

[0027] Preferably, the distributed session management includes:

[0028] Session token generator, using JWT format to carry role identification, ward code and terminal type information;

[0029] Session status monitor: detects the activity of each terminal session in real time and automatically logs out sessions that have been idle for longer than a preset time.

[0030] The session migration component enables doctors to maintain operational context continuity when switching seamlessly between different terminals;

[0031] For the session token generator in distributed session management, the JWT (JSON Web Token) standard can be used. The role identifier, ward code (processed into a hash value using the SHA-256 algorithm to protect privacy), and terminal type (such as a unique identifier generated by the device MAC address and operating system version as the terminal fingerprint) are encoded into the JWT's Payload portion to ensure secure information transmission and parsing. The session status monitor polls each terminal session through a scheduled task to detect its last activity time. If it exceeds a preset threshold (such as 30 minutes), the session logout logic is automatically triggered. The session migration component uses a distributed cache (such as Redis) to store session context. When the doctor switches between different terminals, seamless switching is achieved by verifying the JWT and restoring the context data from the cache.

[0032] The distributed session management mechanism uses session tokens in the JWT format to achieve unified identity authentication and permission verification across terminals, ensuring the security and consistency of doctors' operations across different devices. The introduction of the session state monitor effectively manages the life cycle of terminal sessions, avoiding the security risks that may be brought about by long-term idle sessions, while releasing system resources. The support of the session migration component greatly improves the work efficiency of doctors, allowing them to switch freely between different devices without losing operation progress, ensuring the continuity and efficiency of medical services. Overall, this distributed session management solution not only enhances the security and stability of the system, but also significantly improves the user experience, providing solid technical support for the multi-terminal collaborative work of medical information systems.

[0033] Preferably, the three-dimensional audit report generation method includes:

[0034] Log collector, which synchronously captures RBAC system operation logs and HIS system business logs;

[0035] Log correlation engine, which establishes cross-system log correlation through unique patient ID and operation timestamp;

[0036] Visual renderer, presenting audit results in the form of timeline, heat map and Sankey diagram;

[0037] The log collector uses multi-threaded concurrent technology to establish stable connections with the RBAC system and HIS system, capturing log data in real time. After receiving the log, the log correlation engine first extracts the unique patient ID and operation timestamp, uses a hash algorithm to generate a unique correlation key, and then uses this key to correlate cross-system logs. The visual renderer uses a front-end chart library to dynamically generate timelines, heat maps, and Sankey diagrams based on audit results data, and provides interactive functions to facilitate in-depth analysis.

[0038] Using unique patient IDs and operation timestamps to establish cross-system log associations effectively solves the problem of log fragmentation, allowing auditors to easily track all operation trajectories of specific patients. The visual renderer presents the audit results in the form of timelines, heat maps, and Sankey diagrams, which not only intuitively demonstrates the dynamic changes of audit data, but also reveals potential risk points and operation hotspots in a graphical manner, providing strong decision-making support for hospital management. This method not only improves audit efficiency, but also enhances the availability and comprehensibility of audit results, helping hospitals better manage role permissions and ensure the security and compliance of medical data.

[0039] Preferably, the emergency management module includes:

[0040] Local cache unit, which stores role permission snapshots within the last 72 hours;

[0041] Degradation policy library, pre-setting permission restriction schemes corresponding to different HIS fault levels;

[0042] Recovery validator, which automatically compares the consistency of local cache with the latest HIS data after the HIS system is restored;

[0043] After the HIS system is restored, the recovery verifier automatically starts the data comparison task. It first extracts the role permission snapshot data within the last 72 hours from the local cache unit, then obtains the latest role permission data from the HIS system through the API interface. It uses a hash algorithm to perform integrity verification on the two sets of data and compares the permission configuration items one by one to ensure data consistency. If any discrepancies are found, the details of the discrepancies are recorded and an alarm mechanism is triggered to notify the administrator for manual intervention.

[0044] The local cache unit stores snapshots of role permissions within the last 72 hours to ensure that when the HIS system fails, the system can quickly switch to the local cache to maintain basic business operations and avoid business interruptions. The downgrade policy library presets permission restriction schemes corresponding to different HIS failure levels, allowing the system to flexibly adjust permissions according to actual conditions, which not only ensures business continuity but also avoids the risk of permission abuse. After the HIS system is restored, the recovery validator automatically compares the consistency of the local cache with the latest HIS data to ensure data accuracy, providing strong guarantees for the safe and stable operation of the system. The design of this module not only improves the system's emergency response speed, but also greatly reduces business losses caused by system failures, providing medical institutions with more reliable and efficient management tools.

[0045] Preferably, the tree structure visual editing supports:

[0046] Drag-and-drop node adjustment to reflect changes in permission inheritance relationships in real time;

[0047] Batch rule import function, compatible with HL7 FHIR standard medical data format;

[0048] Rule version controller, supporting rollback and difference comparison of historical configurations;

[0049] The system interface uses a WebGL-based 3D tree diagram display, supports node adjustment by dragging the mouse, and synchronizes permission inheritance relationship data with the backend in real time via WebSocket. The batch rule import function parses HL7 FHIR standard XML or JSON files and automatically maps them to the system permission model. The rule version controller uses Git principles to maintain a version library in the background, record every configuration change, and support version rollback and difference comparison through interface buttons.

[0050] First, drag-and-drop node adjustment greatly improves the intuitiveness and efficiency of permission configuration. Managers can operate directly on the interface and see changes in permission inheritance relationships in real time, reducing the risk of system failures due to configuration errors. Second, the batch rule import function is compatible with the HL7 FHIR standard medical data format, enabling the system to seamlessly connect to various medical information systems, achieving standardization and automated processing of permission data, and reducing the error rate of manual entry. Finally, the introduction of the rule version controller provides historical tracing and version rollback capabilities for permission management. Managers can easily view the details of each configuration change, quickly locate the root cause of the problem, and restore to the previous stable state when necessary, thereby ensuring the continued stable operation of the system.

[0051] Preferably, the dynamic selection mechanism includes:

[0052] Sensitive field identifier, which matches patient ID number and diagnosis information preset fields based on regular expressions;

[0053] Algorithm negotiation component, which negotiates with the terminal to determine the final encryption algorithm;

[0054] Encryption performance monitor that automatically switches to a lightweight algorithm when encryption latency exceeds a threshold

[0055] The algorithm negotiation component can incorporate a terminal performance evaluation step into the negotiation process, recommending the optimal encryption algorithm based on the terminal's computing power. The encryption performance monitor can set multiple thresholds. When latency reaches different levels, it will switch to a lighter encryption algorithm in sequence, ensuring a balance between data transmission efficiency and security.

[0056] The dynamic selection mechanism has significant advantages in ensuring the secure transmission of patient data. Through the sensitive field identifier, the system can accurately identify and encrypt key information, effectively preventing data leakage. The algorithm negotiation component enhances the flexibility and adaptability of the system, and can dynamically adjust the encryption strategy according to the terminal performance, which not only ensures the security of data transmission but also avoids unnecessary performance loss. The introduction of the encryption performance monitor enables the system to monitor and adjust the performance bottlenecks in the encryption process in real time while ensuring security. When the encryption delay is detected to be too high, it automatically switches to a lightweight algorithm to ensure the smoothness of data transmission. This mechanism not only improves the overall operating efficiency of the system, but also enhances the user experience, providing a solid security guarantee for medical informatization.

[0057] Preferably, the JWT payload of the session token generator includes:

[0058] Role coding adopts the hospital's unified identity authentication system standards;

[0059] Ward hash value, generated by processing the original ward code using the SHA-256 algorithm;

[0060] Terminal fingerprint, a unique identifier generated based on the device's MAC address and operating system version;

[0061] The role code directly maps to the existing role ID in the hospital's unified identity authentication system to ensure consistency. When generating the ward hash value, the original ward code is input into the SHA-256 algorithm, which outputs a fixed-length hash value to protect data privacy. The terminal fingerprint reads the device MAC address and operating system version information, combined with a specific algorithm to generate a unique identifier to ensure unique tracking of the terminal.

[0062] The JWT payload is designed to include role codes, ward hash values, and terminal fingerprints, significantly improving the security and manageability of the system. The role code adopts the hospital's unified standard, simplifying the permission management process and ensuring consistency of roles across systems. The ward hash value is generated using the SHA-256 algorithm, which not only protects the privacy of the original ward code but also enables rapid verification without decryption, enhancing data security. The introduction of terminal fingerprints enables the system to accurately identify and manage each access device, effectively preventing the access of illegal devices and the risk of data leakage.

[0063] Preferably, the association process includes:

[0064] Log normalization processing, unifying the log formats of different systems into JSON Schema;

[0065] Event time alignment, using the NTP protocol for cross-system clock synchronization;

[0066] Association rule engine, which defines log association paths based on medical business process diagrams;

[0067] In terms of log standardization, the use of customized log parsing scripts can be further described to parse each system log line by line, identify key fields, and reorganize them according to predefined JSON Schema templates to ensure that all log items (such as operation type, timestamp, user ID, etc.) conform to a unified format. For event time alignment, the deployment location and configuration method of the NTP server can be specifically described to ensure that all system clocks are synchronized with the standard time source. The association rule engine can accurately match key information in the log by writing XPath or JSONPath expressions based on medical business processes, thereby achieving automatic association of log items.

[0068] The combination of log normalization, event time alignment, and an association rule engine can significantly improve the efficiency and accuracy of multi-system log management. Log normalization unifies log data from different systems, facilitating subsequent analysis and processing. Event time alignment ensures the accuracy of log records and avoids analysis biases caused by clock differences. The association rule engine, based on medical business process diagrams, accurately links related log items, providing strong support for audit tracking, problem troubleshooting, and business optimization.

[0069] In summary, compared with the prior art, the present invention provides a multi-role collaborative management system based on RBAC+HIS synchronization, which has the following beneficial effects:

[0070] This invention achieves dynamic optimization and efficient collaboration of medical rights management by building a multi-role collaborative management system based on RBAC+HIS synchronization, which has significant benefits.

[0071] This architecture leverages the linkage between the role-based permission management module and the HIS system's real-time organizational structure data, combined with a dynamic rule engine to generate a multi-level role-based permission tree. This significantly shortens the permission adjustment cycle and reduces the risk of data leakage caused by manual configuration errors. Furthermore, the bidirectional mapping between roles and department codes ensures the accuracy of permission allocation and improves hospital management efficiency.

[0072] The data synchronization middleware uses field-level encryption and incremental verification, combined with transport layer encryption algorithms, to ensure the security of data transmission and avoid bandwidth waste and privacy leakage in the full push mode. The multi-terminal collaboration engine implements permission mapping through distributed session management, and has built-in conflict detection and secondary authentication processes, which not only ensures data security, but also improves the convenience of doctors' operations between different terminals, significantly improving the efficiency of diagnosis and treatment. In addition, the three-dimensional audit report of the permission audit center provides a basis for data leakage tracing, and the emergency management module ensures business continuity in the event of system abnormalities, further enhancing the security and reliability of the medical system. BRIEF DESCRIPTION OF THE DRAWINGS

[0073] Figure 1 This invention is a schematic diagram of a multi-role collaborative management system based on RBAC+HIS synchronization. DETAILED DESCRIPTION

[0074] This invention provides a technical solution, a multi-role collaborative management system based on RBAC+HIS synchronization, please refer to Figure 1 ,include:

[0075] The role permission management module builds a static role permission baseline based on the RBAC model and associates it with the real-time organizational structure data of the HIS system through a dynamic rule engine to generate a multi-level role permission tree;

[0076] Data synchronization middleware uses an API gateway to implement one-way data push between the HIS system and the psychological assessment platform. It includes field-level encryption units and incremental data verification units, and supports the isolated transmission of patient medical records, medical orders, and assessment tasks by ward.

[0077] The multi-terminal collaboration engine uses distributed session management to achieve permission mapping between doctor workstations, mobile nursing terminals, and patient self-service terminals. It also has a built-in conflict detection mechanism that triggers a secondary authentication process when cross-ward operations are detected.

[0078] The authority audit center records role change logs and associates them with HIS system operation logs with timestamps to generate a three-dimensional audit report that includes operation traces, data flows, and risk levels;

[0079] The emergency management module automatically switches to the locally cached role permission configuration when an HIS system anomaly is detected, and performs permission downgrade processing based on the preset department priority rules;

[0080] The role authority management module establishes a bidirectional mapping relationship between ward codes and HIS system department codes. The data synchronization middleware uses the AES-256 segmented encryption algorithm at the transport layer, and the multi-terminal collaboration engine supports intelligent switching between the WebSocket protocol and HTTP long polling.

[0081] In the role and permission management module, if there are compatibility issues between the RBAC model and the organizational structure data of the HIS system, an intermediate adapter layer can be developed to parse the JSON format data returned by the HIS and convert it into a permission configuration format that can be recognized by the RBAC model, ensuring the effective integration of the static role and permission baseline and the dynamic organizational structure data.

[0082] The role and authority management module combines the RBAC model with the dynamic data of the HIS system to achieve flexible configuration and real-time update of role permissions, enhancing the system's adaptability to complex medical environments. The data synchronization middleware uses API gateway and field-level encryption technology to ensure the security and integrity of patient data during transmission. At the same time, it supports isolated transmission by ward, improving the efficiency and accuracy of data processing. The multi-terminal collaboration engine realizes seamless collaboration among doctors, nurses and patient terminals through distributed session management. The built-in conflict detection and secondary authentication mechanism effectively prevents authority abuse and data leakage. The authority audit center provides traceable audit basis for system security through detailed log records and correlation analysis. The addition of the emergency management module further improves the robustness of the system, ensuring that basic business operations can be maintained when the HIS system is abnormal.

[0083] See also Figure 1 , the dynamic rule engine includes:

[0084] The rule configuration interface supports visual editing of permission inheritance rules based on the tree structure of the hospital's organizational structure;

[0085] The rule parser converts the configured rules into executable scripts and matches them in real time with the JSON format organization data returned by the HIS system;

[0086] The conflict resolution unit, when detecting a conflict between RBAC baseline permissions and HIS dynamic data, conducts arbitration based on the preset medical service priority table;

[0087] Regarding the specific implementation of the conflict resolution unit in the dynamic rule engine, when a conflict is detected between the RBAC baseline permissions and HIS dynamic data, the system first reads the preset medical service priority table, which lists the priority order of various medical services in detail. Then, the system matches the priority table based on the type of medical service involved in the conflict and automatically selects the business rule with the higher priority as the arbitration basis, thereby resolving the permission conflict and ensuring the smooth operation of medical services.

[0088] The dynamic rule engine realizes the flexible editing and efficient execution of the hospital organizational structure permission inheritance rules through the collaborative work of the rule configuration interface, rule parser and conflict resolution unit. The tree structure visual editing function of the rule configuration interface makes the adjustment of permission inheritance rules intuitive and convenient, reducing management costs. The rule parser converts the configuration rules into executable scripts and matches them with the JSON format organization data returned by the HIS system in real time, ensuring the accuracy and timeliness of permission allocation. When the conflict resolution unit detects a conflict between RBAC baseline permissions and HIS dynamic data, it can arbitrate according to the preset medical business priority table, effectively avoiding the impact of permission conflicts on medical business and ensuring the efficiency and safety of hospital operations.

[0089] See also Figure 1 , the field-level encryption units include:

[0090] Encryption policy manager, dynamically selecting AES-256 or national encryption SM4 algorithm based on the sensitivity level of patient data;

[0091] The key distribution submodule pushes temporary session keys to each terminal through the hospital intranet security channel;

[0092] Encryption performance optimizer, using cache pre-encryption mechanism for frequently accessed fields;

[0093] In the field-level encryption unit, the encryption policy manager automatically determines the sensitivity level of patient data (such as ID number and diagnosis information) based on its built-in sensitivity assessment algorithm, and selects AES-256 or the national encryption SM4 algorithm for encryption accordingly. The key distribution submodule uses the hospital's existing VPN or encrypted tunnel technology to establish a secure channel, encrypts the generated temporary session key, and pushes it to each terminal. The encryption performance optimizer analyzes historical access records to identify frequently accessed fields, pre-encrypts them when the system is idle, and stores them in the local cache to reduce the computational burden of real-time encryption.

[0094] The field-level encryption unit ensures the security of patient data at different sensitivity levels by dynamically selecting encryption algorithms, meeting compliance requirements while taking into account encryption efficiency. It uses the hospital's intranet secure channel to distribute keys, effectively preventing the risk of key leakage during transmission. At the same time, the encryption performance optimizer significantly improves the encryption speed of high-frequency access fields through a cache pre-encryption mechanism, reducing system latency and improving user experience.

[0095] See also Figure 1 , distributed session management includes:

[0096] Session token generator, using JWT format to carry role identification, ward code and terminal type information;

[0097] Session status monitor: detects the activity of each terminal session in real time and automatically logs out sessions that have been idle for longer than a preset time.

[0098] The session migration component enables doctors to maintain operational context continuity when switching seamlessly between different terminals;

[0099] For the session token generator in distributed session management, the JWT (JSON Web Token) standard can be used. The role identifier, ward code (processed into a hash value using the SHA-256 algorithm to protect privacy), and terminal type (such as a unique identifier generated by the device MAC address and operating system version as the terminal fingerprint) are encoded into the JWT's Payload portion to ensure secure information transmission and parsing. The session status monitor polls each terminal session through a scheduled task to detect its last activity time. If it exceeds a preset threshold (such as 30 minutes), the session logout logic is automatically triggered. The session migration component uses a distributed cache (such as Redis) to store session context. When the doctor switches between different terminals, seamless switching is achieved by verifying the JWT and restoring the context data from the cache.

[0100] The distributed session management mechanism uses session tokens in the JWT format to achieve unified identity authentication and permission verification across terminals, ensuring the security and consistency of doctors' operations across different devices. The introduction of the session state monitor effectively manages the life cycle of terminal sessions, avoiding the security risks that may be brought about by long-term idle sessions, while releasing system resources. The support of the session migration component greatly improves the work efficiency of doctors, allowing them to switch freely between different devices without losing operation progress, ensuring the continuity and efficiency of medical services. Overall, this distributed session management solution not only enhances the security and stability of the system, but also significantly improves the user experience, providing solid technical support for the multi-terminal collaborative work of medical information systems.

[0101] See also Figure 1, the three-dimensional audit report generation method includes:

[0102] Log collector, which synchronously captures RBAC system operation logs and HIS system business logs;

[0103] Log correlation engine, which establishes cross-system log correlation through unique patient ID and operation timestamp;

[0104] Visual renderer, presenting audit results in the form of timeline, heat map and Sankey diagram;

[0105] The log collector uses multi-threaded concurrent technology to establish stable connections with the RBAC system and HIS system, capturing log data in real time. After receiving the log, the log correlation engine first extracts the unique patient ID and operation timestamp, uses a hash algorithm to generate a unique correlation key, and then uses this key to correlate cross-system logs. The visual renderer uses a front-end chart library to dynamically generate timelines, heat maps, and Sankey diagrams based on audit results data, and provides interactive functions to facilitate in-depth analysis.

[0106] Using unique patient IDs and operation timestamps to establish cross-system log associations effectively solves the problem of log fragmentation, allowing auditors to easily track all operation trajectories of specific patients. The visual renderer presents the audit results in the form of timelines, heat maps, and Sankey diagrams, which not only intuitively demonstrates the dynamic changes of audit data, but also reveals potential risk points and operation hotspots in a graphical manner, providing strong decision-making support for hospital management. This method not only improves audit efficiency, but also enhances the availability and comprehensibility of audit results, helping hospitals better manage role permissions and ensure the security and compliance of medical data.

[0107] See also Figure 1 , the emergency management module includes:

[0108] Local cache unit, which stores role permission snapshots within the last 72 hours;

[0109] Degradation policy library, pre-setting permission restriction schemes corresponding to different HIS fault levels;

[0110] Recovery validator, which automatically compares the consistency of local cache with the latest HIS data after the HIS system is restored;

[0111] After the HIS system is restored, the recovery verifier automatically starts the data comparison task. It first extracts the role permission snapshot data within the last 72 hours from the local cache unit, then obtains the latest role permission data from the HIS system through the API interface. It uses a hash algorithm to perform integrity verification on the two sets of data and compares the permission configuration items one by one to ensure data consistency. If any discrepancies are found, the details of the discrepancies are recorded and an alarm mechanism is triggered to notify the administrator for manual intervention.

[0112] The local cache unit stores snapshots of role permissions within the last 72 hours to ensure that when the HIS system fails, the system can quickly switch to the local cache to maintain basic business operations and avoid business interruptions. The downgrade policy library presets permission restriction schemes corresponding to different HIS failure levels, allowing the system to flexibly adjust permissions according to actual conditions, which not only ensures business continuity but also avoids the risk of permission abuse. After the HIS system is restored, the recovery validator automatically compares the consistency of the local cache with the latest HIS data to ensure data accuracy, providing strong guarantees for the safe and stable operation of the system. The design of this module not only improves the system's emergency response speed, but also greatly reduces business losses caused by system failures, providing medical institutions with more reliable and efficient management tools.

[0113] See also Figure 1 , tree structure visual editing supports:

[0114] Drag-and-drop node adjustment to reflect changes in permission inheritance relationships in real time;

[0115] Batch rule import function, compatible with HL7 FHIR standard medical data format;

[0116] Rule version controller, supporting rollback and difference comparison of historical configurations;

[0117] The system interface uses a WebGL-based 3D tree diagram display, supports node adjustment by dragging the mouse, and synchronizes permission inheritance relationship data with the backend in real time via WebSocket. The batch rule import function parses HL7 FHIR standard XML or JSON files and automatically maps them to the system permission model. The rule version controller uses Git principles to maintain a version library in the background, record every configuration change, and support version rollback and difference comparison through interface buttons.

[0118] First, drag-and-drop node adjustment greatly improves the intuitiveness and efficiency of permission configuration. Managers can operate directly on the interface and see changes in permission inheritance relationships in real time, reducing the risk of system failures due to configuration errors. Second, the batch rule import function is compatible with the HL7 FHIR standard medical data format, enabling the system to seamlessly connect to various medical information systems, achieving standardization and automated processing of permission data, and reducing the error rate of manual entry. Finally, the introduction of the rule version controller provides historical tracing and version rollback capabilities for permission management. Managers can easily view the details of each configuration change, quickly locate the root cause of the problem, and restore to the previous stable state when necessary, thereby ensuring the continued stable operation of the system.

[0119] See also Figure 1, the dynamic selection mechanisms include:

[0120] Sensitive field identifier, which matches patient ID number and diagnosis information preset fields based on regular expressions;

[0121] Algorithm negotiation component, which negotiates with the terminal to determine the final encryption algorithm;

[0122] Encryption performance monitor that automatically switches to a lightweight algorithm when encryption latency exceeds a threshold

[0123] The algorithm negotiation component can incorporate a terminal performance evaluation step into the negotiation process, recommending the optimal encryption algorithm based on the terminal's computing power. The encryption performance monitor can set multiple thresholds. When latency reaches different levels, it will switch to a lighter encryption algorithm in sequence, ensuring a balance between data transmission efficiency and security.

[0124] The dynamic selection mechanism has significant advantages in ensuring the secure transmission of patient data. Through the sensitive field identifier, the system can accurately identify and encrypt key information, effectively preventing data leakage. The algorithm negotiation component enhances the flexibility and adaptability of the system, and can dynamically adjust the encryption strategy according to the terminal performance, which not only ensures the security of data transmission but also avoids unnecessary performance loss. The introduction of the encryption performance monitor enables the system to monitor and adjust the performance bottlenecks in the encryption process in real time while ensuring security. When the encryption delay is detected to be too high, it automatically switches to a lightweight algorithm to ensure the smoothness of data transmission. This mechanism not only improves the overall operating efficiency of the system, but also enhances the user experience, providing a solid security guarantee for medical informatization.

[0125] See also Figure 1 , the JWT payload of the session token generator contains:

[0126] Role coding adopts the hospital's unified identity authentication system standards;

[0127] Ward hash value, generated by processing the original ward code using the SHA-256 algorithm;

[0128] Terminal fingerprint, a unique identifier generated based on the device's MAC address and operating system version;

[0129] The role code directly maps to the existing role ID in the hospital's unified identity authentication system to ensure consistency. When generating the ward hash value, the original ward code is input into the SHA-256 algorithm, which outputs a fixed-length hash value to protect data privacy. The terminal fingerprint reads the device MAC address and operating system version information, combined with a specific algorithm to generate a unique identifier to ensure unique tracking of the terminal.

[0130] The JWT payload is designed to include role codes, ward hash values, and terminal fingerprints, significantly improving the security and manageability of the system. The role code adopts the hospital's unified standard, simplifying the permission management process and ensuring consistency of roles across systems. The ward hash value is generated using the SHA-256 algorithm, which not only protects the privacy of the original ward code but also enables rapid verification without decryption, enhancing data security. The introduction of terminal fingerprints enables the system to accurately identify and manage each access device, effectively preventing the access of illegal devices and the risk of data leakage.

[0131] See also Figure 1 , the associated process includes:

[0132] Log normalization processing, unifying the log formats of different systems into JSON Schema;

[0133] Event time alignment, using the NTP protocol for cross-system clock synchronization;

[0134] Association rule engine, which defines log association paths based on medical business process diagrams;

[0135] In terms of log standardization, the use of customized log parsing scripts can be further described to parse each system log line by line, identify key fields, and reorganize them according to predefined JSON Schema templates to ensure that all log items (such as operation type, timestamp, user ID, etc.) conform to a unified format. For event time alignment, the deployment location and configuration method of the NTP server can be specifically described to ensure that all system clocks are synchronized with the standard time source. The association rule engine can accurately match key information in the log by writing XPath or JSONPath expressions based on medical business processes, thereby achieving automatic association of log items.

[0136] The combination of log normalization, event time alignment, and an association rule engine can significantly improve the efficiency and accuracy of multi-system log management. Log normalization unifies log data from different systems, facilitating subsequent analysis and processing. Event time alignment ensures the accuracy of log records and avoids analysis bias caused by clock discrepancies. The association rule engine, based on medical business process diagrams, accurately links related log items, providing strong support for audit tracking, problem troubleshooting, and business optimization.

[0137] Improved efficiency: The time required to configure role permissions has been reduced from 30 minutes per session to 5 minutes per session, and department data synchronization efficiency has increased by 80%. The time required to issue group physical examination tasks has been reduced by 70% (configuration for a group of 1,000 people can be completed within 1 hour).

[0138] Data consistency: The cross-end data synchronization error rate was reduced from 15% to 0.5%, and the matching accuracy of prescription association evaluation tasks was ≥ 98%;

[0139] Enhanced security: Through ward binding and field-level encryption (AES-256), patient data leakage is achieved; the risk of incorrect permission operation is reduced by 90% (compared to traditional static RBAC).

[0140] User experience optimization: The doctor's workstation integrates HIS and psychological CT functions, shortening the operation path by 50%; the nurse's pad only displays tasks bound to the ward, reducing the interface complexity by 60%.

[0141] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus.

[0142] While embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions, and variations may be made to these embodiments without departing from the principles and spirit of the invention, and that the scope of the invention is defined by the appended claims and their equivalents.

Claims

1. Multi-role collaborative management system based on RBAC+HIS synchronization, characterized by: include: The role permission management module builds a static role permission baseline based on the RBAC model and associates it with the real-time organizational structure data of the HIS system through a dynamic rule engine to generate a multi-level role permission tree; Data synchronization middleware uses an API gateway to implement one-way data push between the HIS system and the psychological assessment platform. It includes field-level encryption units and incremental data verification units, and supports the isolated transmission of patient medical records, medical orders, and assessment tasks by ward. The multi-terminal collaboration engine uses distributed session management to achieve permission mapping between doctor workstations, mobile nursing terminals, and patient self-service terminals. It also has a built-in conflict detection mechanism that triggers a secondary authentication process when cross-ward operations are detected. The authority audit center records role change logs and associates them with HIS system operation logs with timestamps to generate a three-dimensional audit report that includes operation traces, data flows, and risk levels; The emergency management module automatically switches to the locally cached role permission configuration when an HIS system anomaly is detected, and performs permission downgrade processing based on the preset department priority rules; Among them, the role authority management module establishes a bidirectional mapping relationship between the ward code and the HIS system department code, the data synchronization middleware adopts the AES-256 segmented encryption algorithm at the transport layer, and the multi-terminal collaboration engine supports intelligent switching between the WebSocket protocol and HTTP long polling; The dynamic rule engine includes: The rule configuration interface supports visual editing of permission inheritance rules based on the tree structure of the hospital's organizational structure; The rule parser converts the configured rules into executable scripts and matches them in real time with the JSON format organization data returned by the HIS system; The conflict resolution unit, when detecting a conflict between the RBAC baseline authority and the HIS dynamic data, conducts arbitration based on the preset medical service priority table.

2. The multi-role collaborative management system based on RBAC+HIS synchronization according to claim 1 is characterized in that: The field-level encryption unit includes: Encryption policy manager, dynamically selecting AES-256 or national encryption SM4 algorithm based on the sensitivity level of patient data; The key distribution submodule pushes temporary session keys to each terminal through the hospital intranet security channel; Encryption performance optimizer, which uses a cache pre-encryption mechanism for frequently accessed fields.

3. The multi-role collaborative management system based on RBAC+HIS synchronization according to claim 1 is characterized in that: The distributed session management includes: Session token generator, using JWT format to carry role identification, ward code and terminal type information; Session status monitor: detects the activity of each terminal session in real time and automatically logs out sessions that have been idle for longer than a preset time. The session migration component enables doctors to maintain operational context continuity when switching seamlessly between different terminals.

4. The multi-role collaborative management system based on RBAC+HIS synchronization according to claim 1 is characterized in that: The three-dimensional audit report generation method includes: Log collector, which synchronously captures RBAC system operation logs and HIS system business logs; Log correlation engine, which establishes cross-system log correlation through unique patient ID and operation timestamp; Visual renderer presents audit results in the form of timeline, heat map and Sankey diagram.

5. The multi-role collaborative management system based on RBAC+HIS synchronization according to claim 1 is characterized in that: The emergency management module includes: Local cache unit, which stores role permission snapshots within the last 72 hours; Degradation policy library, pre-setting permission restriction schemes corresponding to different HIS fault levels; Recovery validator automatically compares the consistency of local cache with the latest HIS data after the HIS system is restored.

6. The multi-role collaborative management system based on RBAC+HIS synchronization according to claim 1 is characterized in that: The tree structure visual editing supports: Drag-and-drop node adjustment to reflect changes in permission inheritance relationships in real time; Batch rule import function, compatible with HL7 FHIR standard medical data format; Rule version controller, supports rollback and difference comparison of historical configurations.

7. The multi-role collaborative management system based on RBAC+HIS synchronization according to claim 2 is characterized in that: The dynamic selection mechanism includes: Sensitive field identifier, which matches patient ID number and diagnosis information preset fields based on regular expressions; Algorithm negotiation component, which negotiates with the terminal to determine the final encryption algorithm; Encryption performance monitor that automatically switches to a lightweight algorithm when it detects that encryption latency exceeds a threshold.

8. The multi-role collaborative management system based on RBAC+HIS synchronization according to claim 3 is characterized in that: The JWT payload of the session token generator contains: Role coding adopts the hospital's unified identity authentication system standards; Ward hash value, generated by processing the original ward code using the SHA-256 algorithm; Terminal fingerprint, a unique identifier generated based on the device's MAC address and operating system version.

9. The multi-role collaborative management system based on RBAC+HIS synchronization according to claim 4 is characterized in that: The association process includes: Log normalization processing, unifying the log formats of different systems into JSON Schema; Event time alignment, using the NTP protocol for cross-system clock synchronization; Association rule engine, defines log association paths based on medical business process diagrams.

Images