Medical management system and data access method thereof
Through the multi-layer architecture and dual unidirectional isolation switching technology of the medical management system, combined with 5G dual-domain private network authentication, the complexity and security issues of data access in cross-network environments are solved, and safe, controllable, real-time data access and system stability are achieved.
Patent Information
- Application Number
- CN202511281998.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-09-09
- Publication Date
- 2025-10-17
- Estimated Expiration
- 2045-09-09
AI Technical Summary
It is difficult to achieve secure, controllable, and real-time data access between different access environments. The existing medical management system has problems such as high data access complexity, heavy user operation burden, multiple security risks, and low efficiency of high-concurrency access in a cross-network environment.
The multi-layer architecture design of the medical management system is adopted, including the access layer, service layer, business application layer and data layer. The dual unidirectional isolation switching technology is used to realize the one-way secure transmission of business data between different network environments. It is combined with the 5G dual-domain private network for identity authentication and data access control, and the basic layer is used for dynamic resource scheduling to ensure system stability.
It achieves secure, controllable, and real-time data access in different network environments, improves user access convenience and system stability, and reduces operational burdens and security risks.
Smart Images

Figure CN120811775A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of medical treatment, in particular, the present application relates to a medical management system and a data access method thereof. BACKGROUND
[0002] With the continuous improvement of medical informatization level, the medical management system gradually presents the trend of multi-layer architecture, distributed deployment and cross-institutional cooperation, and can support data interaction between different medical institutions and different access environments. However, the existing data access mode still has many deficiencies in the cross-environment access scene.
[0003] Specifically, due to the consideration of business data security and compliance, the medical management system usually needs to strictly control the access path and access permission, which to some extent increases the complexity of data access, making it difficult for users to obtain the required business data in a timely manner in a non-local access environment.
[0004] Based on this, it is difficult to achieve safe, controllable and real-time data access between different access environments, which is a problem to be solved. SUMMARY
[0005] Embodiments of the present application provide a medical management system and a data access method, device, computer equipment, storage medium and computer program product, which can solve the problem of difficult safe, controllable and real-time data access between different access environments in related technologies. The technical solution is as follows: According to an aspect of the present application, a data access method of a medical management system, the system comprising an access layer, a service layer, a business application layer and a data layer; wherein the data layer is deployed in a first network environment, and the access layer is deployed in a second network environment which is isolated from the first network environment; the method comprising: providing an access platform for a user in the access layer, and generating a business access request based on a business access operation of the user on the access platform, and sending the business access request to the service layer; the business access request being used to indicate a target business requested to be accessed by the user; calling a target business module corresponding to the target business according to the business access request in the service layer, and forwarding the business access request to the business application layer according to the target business module; constructing a data access request corresponding to the target business module according to the target business indicated by the business access request in the business application layer, and sending the data access request to the data layer; the data access request being used to request the data layer to acquire target business data corresponding to the target business module; acquiring the target business data corresponding to the target business based on the data access request in the data layer, and performing encryption processing on the target business data, and returning the encrypted target business data to the access layer through a double one-way isolated exchange technology; wherein the double one-way isolated exchange technology is used to realize one-way secure transmission of business data between the first network environment and the second network environment; performing decryption processing on the encrypted target business data in the access layer, and displaying the decrypted target business data on the access platform, so that the user views the target business data on the access platform.
[0006] According to an aspect of the present application, a data access device of a medical management system, the system comprising an access layer, a service layer, a business application layer and a data layer; wherein the data layer is deployed in a first network environment, and the access layer is deployed in a second network environment which is isolated from the first network environment; the device comprising: a business access module configured to provide an access platform for a user in the access layer, and generate a business access request based on a business access operation of the user on the access platform, and send the business access request to the service layer; the business access request being used to indicate a target business requested to be accessed by the user; a business calling module configured to call a target business module corresponding to the target business according to the business access request in the service layer, and forward the business access request to the business application layer according to the target business module; a data access module configured to construct a data access request corresponding to the target business module according to the target business indicated by the business access request in the business application layer, and send the data access request to the data layer; the data access request being used to request the data layer to obtain target business data corresponding to the target business module; a data obtaining module configured to obtain the target business data corresponding to the target business based on the data access in the data layer, and perform encryption processing on the target business data, and return the encrypted target business data to the access layer through a double one-way isolated exchange technology; wherein the double one-way isolated exchange technology is used to realize one-way secure transmission of business data between the first network environment and the second network environment; and a data display module configured to perform decryption processing on the encrypted target business data in the access layer, and display the decrypted target business data on the access platform, so that the user views the target business data on the access platform.
[0007] According to an aspect of the present application, a medical management system comprises an access layer, a service layer, a business application layer and a data layer; the access layer is configured to provide an access platform for a user, generate a business access request based on a business access operation of the user on the access platform, send the business access request to the service layer, receive target business data after encryption sent by the data layer, decrypt the target business data after encryption, and display the target business data after decryption on the access platform, so that the user views the target business data on the access platform; the business access request is used to indicate a target business requested to be accessed by the user; the service layer is configured to call a corresponding target business module according to the business access request, and forward the business access request to the business application layer according to the target business module; the business application layer is configured to construct a data access request corresponding to the target business module according to the target business indicated by the business access request, and send the data access request to the data layer; the data access request is used to request the data layer to obtain target business data corresponding to the target business module; the data layer is configured to receive the data access request, obtain target business data corresponding to the target business based on the data access request, and encrypt the target business data, and return the target business data after encryption to the access layer through a double one-way isolation exchange technology; wherein the data layer is deployed in a first network environment, and the access layer is deployed in a second network environment isolated from the first network environment; the double one-way isolation exchange technology is used to realize one-way secure transmission of business data between the first network environment and the second network environment.
[0008] According to an aspect of the present application, a computer device comprises at least one processor and at least one memory, wherein the memory stores a computer program, and the computer program is executed by the processor to implement the data access method of the medical management system.
[0009] According to an aspect of the present application, a storage medium stores a computer program, and the computer program is executed by one or more processors to implement the data access method of the medical management system.
[0010] According to an aspect of the present application, a computer program product comprises a computer program, and the computer program is executed by one or more processors to implement the data access method of the medical management system.
[0011] The technical scheme provided by the present application has the beneficial effects that: In the technical solution, the secure access and display of target business data across different network environments in the medical management system is realized, a complete business access link is constructed between the access layer, the service layer, the business application layer and the data layer, and it is ensured that the business access request initiated by the user in the external network environment can be securely transmitted to the data layer of the internal network environment for processing after authentication, routing and data generation, and the encrypted target business data is unidirectionally returned to the access layer for decryption and display, thereby effectively solving the problem of difficult secure, controllable and real-time data access between different access environments in the related art. BRIEF DESCRIPTION OF DRAWINGS
[0012] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments of the present application will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor on the basis of these drawings.
[0013] Figure 1 is a structural block diagram of a medical management system according to the present application; Figure 2 is a system block diagram of a medical management system according to an exemplary embodiment; Figure 3 is a flowchart of a data access method of a medical management system according to an exemplary embodiment; Figure 4 is Figure 3 corresponding to step 310 in the flowchart of one embodiment; Figure 5 is Figure 3 corresponding to step 350 in the flowchart of one embodiment; Figure 6 is Figure 5 corresponding to step 351 in the flowchart of one embodiment; Figure 7 is Figure 6 is a specific implementation schematic diagram of the double one-way isolation exchange technology involved in the corresponding embodiment; Figure 8 is Figure 3 corresponding to the data access method of the medical management system in the flowchart of one embodiment; Figures 9 to 10 is a specific implementation schematic diagram of a data access method of a medical management system in an application scenario; Figure 11 is a structural block diagram of a data access device of a medical management system according to an exemplary embodiment. DETAILED DESCRIPTION
[0014] Embodiments of the present application are described in detail below with reference to the attached drawing figures, wherein the same or like component have the same or similar designations throughout the attaching figures. The embodiments described below are presented by way of example only and are not intended to limit the application as defined in the claims.
[0015] As can be appreciated by one skilled in the art, the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. It should be further understood that the terms “comprise,” “comprises,” “comprising,” “include,” “includes,” “including,” “contain,” “contains,” “containing,” and the like are used interchangeably with “comprising” and “including” and should be understood as not excluding the presence of other features, integers, steps, operations, elements, and / or components. It will be understood that when an element is referred to as being “connected” or “coupled” to another element, it can be directly connected or coupled to the other element or intervening elements can be present. In addition, the use of “connection” or “coupling” herein also includes wireless connection or wireless coupling. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed items.
[0016] As mentioned above, the existing data access mode still has many deficiencies under the cross-network environment.
[0017] On the one hand, in order to protect the security of sensitive business data, the inventors thought that different functional modules of the medical management system can be deployed in mutually isolated network environments. However, this isolation improves the data security to some extent, but also increases the complexity of cross-network access, and users often cannot directly and conveniently access the required business data from the external environment.
[0018] On the other hand, the inventors found that the existing medical management system lacks a unified mechanism for security access control, and the access portals and authentication processes between different business modules are independent of each other, resulting in the need for multiple logins and repeated authentication for users, increasing the operation burden, and also possibly causing security risks due to inconsistent authentication standards.
[0019] In addition, in a high-concurrency access scenario, due to the lack of cross-level resource dynamic scheduling capability, when the resource consumption of a certain system layer is too high, it may cause access delay, request blocking and other problems, affecting the overall running efficiency and stability.
[0020] As can be appreciated from the above, there are still defects in the related art that it is difficult to achieve secure, controllable, and real-time data access between different access environments.
[0021] To this end, the data access method of the medical management system provided by the present application can effectively improve the security of data access of the medical management system. Accordingly, the data access method of the medical management system is applicable to a data access device of the medical management system, which can be deployed on an electronic device, such as a computer device configured with a von Neumann architecture, for example, including a desktop computer, a notebook computer, a server, etc.
[0022] To make the objectives, technical solutions, and advantages of the present application clearer, the embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
[0023] Please refer to Figure 1 , Figure 1 is a structural diagram of a medical management system, as Figure 1 indicated, the medical management system 100 includes an access layer 110, a service layer 130, a business application layer 150, and a data layer 170. Among them, the data layer 170 is deployed in a first network environment, and the access layer 110 is deployed in a second network environment isolated from the first network environment.
[0024] The access layer 110 is configured to provide an access platform for a user, generate a business access request based on a business access operation of the user on the access platform, and send the business access request to the service layer. The business access request is used to indicate a target business requested to be accessed by the user. The access layer 110 receives encrypted target business data sent by the data layer, decrypts the encrypted target business data, and displays the decrypted target business data on the access platform, so that the user can view the target business data on the access platform. Among them, the access layer 110 can provide the access platform for the user through various ways such as a mobile application (APP) installed on a user terminal, a WeChat public number, and an Alipay life number.
[0025] The service layer 130 is configured to call a corresponding target business module according to the business access request, and forward the business access request to the business application layer according to the target business module.
[0026] The business application layer 150 is configured to construct a data access request corresponding to the target business module according to the target business indicated by the business access request, and send the data access request to the data layer. The data access request is used to request the data layer to obtain target business data corresponding to the target business module.
[0027] The data layer 170 is configured to receive the data access request, obtain the target business data corresponding to the target business based on the data access request, and encrypt the target business data. The encrypted target business data is returned to the access layer through a double one-way isolation exchange technology.
[0028] The data layer is deployed in a first network environment, and the access layer is deployed in a second network environment isolated from the first network environment; and the two-way isolation switching technology is used to realize one-way secure transmission of service data between the first network environment and the second network environment.
[0029] In one possible implementation, the medical management system can further include a base layer for obtaining resource usage information of the access layer, the service layer, the business application layer and the data layer; based on the resource usage information, allocating or adjusting resources for data transmission between the access layer, the service layer, the business application layer and the data layer; and if it is detected that the resource usage of the access layer, the service layer, the business application layer or the data layer exceeds a set threshold, re-allocating resources to the access layer, the service layer, the business application layer and / or the data layer.
[0030] In one possible implementation, Figure 2 A system block diagram of a medical management system is shown, which includes, from top to bottom in the order of functional logic, an access layer, a service layer, a business application layer, a data layer and a base layer, and the layers interact through information security mechanisms and data standard specifications. Figure 2 As shown, the system includes, from top to bottom in the order of functional logic, an access layer, a service layer, a business application layer, a data layer and a base layer, and the layers interact through information security mechanisms and data standard specifications.
[0031] The access layer is used to provide a unified access portal for terminal users (such as doctors, patients, third-party medical service institutions, etc.), which can be accessed through mobile applications (APP), WeChat public numbers, Alipay life numbers and other ways. The access layer is responsible for carrying a business access module, which can provide an access platform for users and generate a business access request based on the business access operation of the user on the access platform, and send the request to the service layer.
[0032] The service layer is used to receive and process the business access request from the access layer, and provides unified accounts, unified authentication, unified login and unified services. The service layer carries a business calling module, which can call the corresponding target business module according to the business access request, and forward the request to the business application layer to realize access control and business logic scheduling.
[0033] The business application layer includes various functional application modules for medical services, such as appointment registration, online consultation, image examination, report query, health record, medical insurance settlement, etc. The business application layer carries a data access module, which can generate a data access request according to the business access request, and send the data access request to the data layer to obtain the corresponding business data.
[0034] Data layer: responsible for the storage, management and processing of business data, including data collection, data control, data storage, data analysis, data mining and other functions. The data layer carries the data acquisition module, which can find the corresponding target business data based on data access requests, and encrypt the target business data, and then transmit the encrypted data to the access layer through the double one-way isolation exchange technology, realizing the one-way secure transmission of business data between different access environments.
[0035] In one possible implementation, the data layer includes a data acquisition module that can be used to collect real-time video signals output by an ultrasound device and ensure low latency, high reliability and high security during video signal transmission.
[0036] Specifically, the data acquisition module collects real-time pictures of the ultrasound machine through the HDMI interface, uses the built-in acquisition chip to perform signal equalization and jitter suppression, and sends the video frames into the hard-coded unit through the DMA direct memory access mode; the Slice hard-coded mode is used to divide a single frame of video into multiple independent Slices, and only the missing part is retransmitted when the network condition is poor, thereby shortening the recovery time and reducing error propagation.
[0037] The collected video stream is transmitted through the pass-through video transmission protocol, which is based on memory semantic optimization and zero-copy transmission technology, combines RDMA to write data directly into the network buffer, reduces CPU occupation and reduces delay; during transmission, TLS encryption handshake is integrated and supports SM1, SM2, SM3, SM4, SM6 algorithms, realizing video stream encryption and integrity check.
[0038] Data display module: can be deployed in the access layer, used for decrypting the received encrypted business data, and displaying on the access platform, so that users can view the target business data on the access platform.
[0039] Foundation layer: provides cloud computing resources, network resources, storage resources and management functions for the above layers, and monitors and dynamically schedules the resource usage to ensure stable operation of the system under high concurrency or load changes.
[0040] In one possible implementation, the foundation layer can be deployed in the cloud or hybrid cloud environment, based on the decoupled architecture design of the application layer and the physical layer, through the application interface abstraction layer, the plug-in type scheduling strategy engine, the scheduling strategy configuration layer and the resource real-time perception layer, realizing the on-demand allocation and dynamic scheduling of various heterogeneous computing resources (including CPU, GPU, DPU, FPGA, high-speed storage nodes, etc.) in the system.
[0041] The application interface abstraction layer is used to shield the differences between underlying hardware architectures, and provides a unified resource request and interaction interface for the access layer, the service layer, the business application layer, and the data layer, so that the business modules of each layer do not need to care about the specific deployment details of the underlying computing power, and only need to describe their computing power requirements (such as real-time requirements, concurrent access volume, bandwidth requirements, algorithm types, etc.) in a business-friendly manner.
[0042] The plug-in scheduling strategy engine can match the optimal heterogeneous computing resource combination according to the real-time, throughput, and algorithm type requirements of the business module, and support dynamic replacement of scheduling strategies in different business scenarios. For example, in the real-time analysis of ultrasonic video scene, DPU and GPU nodes with video codec hardware acceleration can be preferentially allocated; in the batch data analysis scene, NVME-oF nodes with high storage throughput can be preferentially allocated.
[0043] The scheduling strategy configuration layer can provide management and configuration capabilities for the plug-in scheduling strategy, allowing system administrators to configure the computing power allocation rules and priorities in different stages according to the target business scenario, such as limiting the maximum resource occupation ratio of a single task, optimizing the utilization of specific resources (such as GPU), or reserving a redundant computing power pool for critical businesses.
[0044] The resource real-time perception layer can collect the health status, bandwidth utilization, hardware topology structure, and running load of the distributed computing nodes in real time, and feed back the perception results to the scheduling strategy engine to realize dynamic optimization of resource allocation. For example, when detecting that a node has a high load or hardware failure, the task can be automatically migrated to other healthy nodes, thereby ensuring the continuity and stability of the business.
[0045] In one possible implementation, the basic layer can also access a third-party security platform to provide key, token, and certificate management capabilities of cryptographic algorithms such as SM1, SM4, SM2, SM3, and SM6, for ensuring the security of cross-layer data transmission and access control.
[0046] Referring to Figure 3 , the embodiment of the present application provides a data access method of a medical management system. Figure 1 as shown in the medical management system.
[0047] In the following method embodiment, in order to facilitate description, the medical management system is taken as an example to illustrate the execution subject of each step of the method, but this does not constitute a specific limitation.
[0048] As Figure 3 shown, the method can include the following steps: At step 310, the access layer provides an access platform for the user, and generates a service access request based on the service access operation of the user on the access platform, and sends the service access request to the service layer.
[0049] The service access request is used to indicate a target service requested by the user to access.
[0050] Firstly, the data access method of the embodiment is applicable to a medical management system, which includes an access layer, a service layer, a service application layer, and a data layer. The data layer is deployed in a first network environment, and the access layer is deployed in a second network environment which is isolated from the first network environment.
[0051] Specifically, the access layer can provide a unified access portal, i.e., an access platform, for the user through an access server, a portal system, or a client application deployed in the second network environment. The access platform can be a Web-based portal page, or a client application installed on a user terminal (such as a smart phone, a tablet computer, a personal computer, etc.), which is used to receive the service operation instruction of the user.
[0052] In the embodiment, the first network environment can be an internal secure network environment in which the data layer of the medical management system is deployed, which is usually an information private network in a medical institution, a hospital local area network, or a health industry intranet accessed through a dedicated line. The first network environment is physically isolated from the Internet, and is used to store and process sensitive data such as patient privacy information, diagnosis and treatment data, and electronic medical records.
[0053] It can be understood that the first network environment is an internal network carrying core business systems and sensitive data of a hospital, and can have the following characteristics: isolated from the Internet, limited data exchange with external networks through a secure access point or isolation device; internal devices are interconnected through a high-speed local area network (LAN) to ensure low latency and high reliability of data transmission; the network topology can adopt a multi-layer structure (core layer, aggregation layer, access layer), and multiple levels of protection strategies are deployed.
[0054] The second network environment can be an external network environment in which the access layer of the medical management system is deployed, which is usually a public network environment accessible through the Internet, such as an Internet access platform open to the public by a hospital, a patient service website, a mobile application platform, etc. The network environment is used to provide a service access portal for terminal users (such as doctors, patients, third-party medical service institutions, etc.) to initiate a service access request and view the returned data.
[0055] It can be understood that, in contrast to the first network environment, the second network environment mainly carries the externally open medical service access layer.
[0056] Furthermore, the first network environment and the second network environment can achieve one-way secure data transmission through dual one-way isolation exchange technology, preventing the first network environment from being directly accessed or invaded by the outside.
[0057] When a user performs a service access operation through the access platform, the access layer collects relevant parameters, such as the target hospital identifier, service data type, and user authentication information, and constructs a service access request based on these parameters. The service access request can include information about the service object targeted by the user operation and contextual information required for subsequent access control and data scheduling.
[0058] In one possible implementation, the business access request includes a target hospital identifier and a business data type. The target hospital identifier is used to indicate the data layer of the target hospital that needs to be accessed, and the business data type is used to indicate the specific business data category that needs to be accessed. The user identity authentication information can be used to parse the target member information in the subsequent service layer or business application layer to ensure the legitimacy and accuracy of data access.
[0059] After generating a service access request, the access layer sends it to the service layer. To ensure secure transmission across network environments, the access and service layers can exchange data over an encrypted communication channel (such as TLS / SSL). Access tokens or session keys can be attached during transmission to verify the source and integrity of the service access request.
[0060] In one possible implementation, such as Figure 4 As shown, step 310 may further include the following steps: Step 311: Establish a public communication domain and a secure communication domain in the communication network element through the 5G dual-domain private network.
[0061] The secure communication domain is connected to the first network environment where the data layer is located, and the public communication domain is connected to the second network environment where the access layer is located.
[0062] Specifically, the communication network element can be a core network device that supports 5G private network functions, such as a user plane function node or a multi-access edge computing node of the 5G core network.
[0063] In this embodiment, the communication network element can be divided into two isolated logical domains on the same hardware platform or virtualization platform: Secure communication domain: connected to the first network environment where the data layer is located, used to carry secure access channels involving sensitive business data.
[0064] Public communication domain: connected to the second network environment where the access layer is located, used to carry non-sensitive data traffic such as access to external Internet resources.
[0065] Therefore, by the network slicing or multi-access technology of the 5G dual-domain private network, two types of communication domains can be established on the physical link at the same time, realizing the domain management and isolated transmission of different service traffics, so as to ensure the security of medical data access and the efficiency of service processing.
[0066] In a possible implementation, the hospital internal devices are mainly deployed in the first network environment, which is usually an internal information private network of the hospital or an industry intranet accessed through a private line, is physically isolated from the public Internet, and has a high security protection level. The hospital internal devices include but are not limited to server devices (for example, a medical management system data server), network and security devices, and terminal devices (terminals for use in the hospital only, for example, a doctor workstation, a nurse station terminal, a medical technology department query terminal, and the like).
[0067] In step 313, based on the user identity authentication rule, the communication network element performs dual-domain identity authentication on the user terminal corresponding to the access layer in the public communication domain and the secure communication domain.
[0068] The user terminal corresponding to the access layer can be a user-side device deployed with an access platform client and used to initiate a service access request and receive a service processing result. The user terminal can establish a communication relationship with the access layer by accessing the 5G network (private network or public network).
[0069] In this embodiment, the dual-domain identity authentication refers to the verification of the access rights of the user terminal corresponding to the access layer in the public communication domain and the secure communication domain by the communication network element. The authentication process can include the following operations: In the public communication domain, the network access identity of the user terminal is authenticated, for example, 5G access authentication based on a SIM card / USIM card.
[0070] In the secure communication domain, the service access identity of the user terminal is authenticated again, for example, access right verification based on user identity authentication information, a digital certificate, a token, and the like.
[0071] In a possible implementation, the dual-domain identity authentication includes access authentication and service authorization in the public communication domain and the secure communication domain, to ensure the identity consistency and the legal rights of the terminal accessing the two domains; the process can adopt a two-way authentication mechanism based on user identity authentication information, to prevent unauthorized terminals from accessing sensitive service systems in the first network environment.
[0072] Through the dual-domain identity authentication, it can be ensured that the user terminal not only has network access rights, but also has service authorization to access sensitive service data, thereby realizing multi-layer protection of medical data access.
[0073] Step 315, if the service access request is directed to the target service data in the first network environment, the service access request is forwarded to the data layer through the secure communication domain.
[0074] Specifically, after identifying the access target of the service access request, if the target is the data layer deployed in the first network environment, the communication network element selects the secure communication domain as the transmission path, and routes the request to the internal network address where the target data layer is located through the secure communication domain.
[0075] At this time, the communication network element can direct the service access request to the corresponding first network environment data layer address according to the target hospital identifier and the service data type carried in the service access request, realizing secure access from the external network environment to the internal network service system.
[0076] To ensure transmission security, end-to-end encryption and access control policies can be enabled in the secure communication domain, so as to avoid interception or tampering of service requests during transmission.
[0077] Step 317, if the service access request is directed to external Internet resources, the service access request is forwarded to the external server through the public communication domain.
[0078] In this embodiment, the external Internet resource can be a third-party hospital platform, a public health information platform, or an external cloud service interface, etc.
[0079] After the communication network element determines that the target address of the service access request belongs to the Internet range, the request is forwarded to the corresponding external server through the public communication domain, so as to interact with the external system. Since the public communication domain is physically isolated from the first network environment, the external request cannot directly access the internal data layer, effectively preventing the exposure risk of the internal network.
[0080] Therefore, this way can realize flexible access to the internal network service system and Internet resources in the same terminal session, and the access paths and permission systems of the two are completely isolated, thereby ensuring the security of the first network environment and the convenience of Internet access.
[0081] Through the above process, through the 5G dual-domain private network, intelligent distribution of data access is realized in the communication network element, so that users in the external network environment can safely, quickly and conveniently access the health and health industry private network through the terminal where the access layer is located without changing the SIM card or phone number, thereby directly accessing the applications and data services in the first network environment in the second network environment.
[0082] It is supplemented that the access layer can deploy a user information verification module for verifying the identity of the user before accessing the platform to prevent unauthorized terminals or users from accessing the medical management system.
[0083] In one possible implementation, after the access layer receives a user-initiated access platform login request, the user information is verified; specifically, the access layer receives the login credential information input by the user on the access platform, which can include user identity authentication information (such as a username, a password), a dynamic verification code, and biometric information (such as a fingerprint, facial recognition data), and the access layer can send the user identity authentication information to the authentication service component for verification. The authentication service component can be locally deployed in the access layer or can call the interface of the service layer or an external identity authentication center for implementation; then, in the case of successful identity authentication, the access layer can generate an access token (Token) and a session key for the user, and bind the access token with the user type (such as a doctor, a patient, an administrator, a third-party medical service institution user, etc.), which is used for subsequent business access request permission verification and call control; of course, if the identity authentication fails, the user login request is rejected, and the access platform returns corresponding prompt information, prompting the user to check the login credentials or reapply for access permission.
[0084] In another possible implementation, the access layer can also verify the user information while combining the user terminal device information (such as a device unique identification code, an IP address, geographic location information, etc.) to perform security policy judgment, so as to identify potential unauthorized access or abnormal login behavior, thereby further improving the security of the system.
[0085] Step 330, the service layer calls the target business module corresponding to the target business according to the business access request, and forwards the business access request to the business application layer according to the target business module.
[0086] Specifically, the service layer can be deployed in an independent application server or a cloud computing environment, serving as a business processing hub between the access layer and the business application layer. After receiving the business access request sent by the access layer, the service layer first parses the business access request to extract the key parameters contained therein, such as: target hospital identification, business data type, user identity authentication information, etc.
[0087] In one possible implementation, the service layer can maintain a plurality of different target business modules, each of which corresponds to one or more business processing logics. For example, an electronic medical record query module, a test report acquisition module, an image data review module, a reservation registration module, etc. When the business access request is parsed, the service layer can determine the target business module to be called according to the business data type, the target hospital identification, and the module mapping rule inside the system.
[0088] In addition, the target business module can determine the calling strategy in combination with the user type. For example, for a doctor user, the target business module can include an electronic medical record query module, a test report acquisition module, an image data review module, a prescription issuing module, etc. For a patient user, the target business module can include a reservation registration module, a test result viewing module, a fee list query module, an online payment module, etc.
[0089] It is further explained that the target business module can be dynamically loaded and displayed on the user interface of the access platform, so that the user can directly access the business function matching the role and permission in the access platform interface.
[0090] Therefore, the displayed target business module not only provides the user with viewing, but also further responds to the operation instruction (such as clicking, querying, modifying, downloading, etc.) of the user, and transmits these operations as an updated business access request to the service layer again, which is further processed by the service layer or forwarded to the business application layer.
[0091] In this way, the service layer not only realizes the calling and forwarding function of the target business module, but also dynamically adjusts the business function displayed on the access platform according to the user type and operation context, thereby improving the interactivity and personalized service capability of the system.
[0092] Therefore, after calling the target business module, the service layer can convert the business access request into a data request format matching the target business module based on the business application layer interface address, communication protocol and data format associated with the target business module, and forward it to the corresponding business processing unit in the business application layer. After receiving the request, the business application layer can process the request according to the predetermined business logic.
[0093] For example, when the target business module is an electronic medical record viewing module, the service layer can encapsulate the business access request according to the standard parameter format of the electronic medical record interface, and forward it to the service process responsible for medical record data query in the business application layer; when the target business module is a test report query module, the business access request is forwarded to the functional unit responsible for test report retrieval in the business application layer.
[0094] It should be noted that the target business module is closely related to the user type of the user. Even if multiple users request to access the same target business (such as an "online consultation" service), due to different identity attributes, the target business module called by the system may also be different, thereby affecting the subsequent business processing flow and data display form.
[0095] In a possible implementation, the method further includes: determining a user type of the user according to the service access request; and invoking a corresponding target service module according to the target service indicated by the service access request based on the user type.
[0096] The user type can be a classification identification based on a role or permission assumed by the user in the medical management system, and is used to distinguish the operation permission, data access range, and interaction content difference of different users in a service process.
[0097] In a possible implementation, the user type includes a doctor, a patient, a nurse, an expert remote consultation personnel, and the like, which are not specifically limited herein.
[0098] For example, if the user is a patient, the system can invoke an online consultation module dedicated to patients to provide functions including consultation initiation, graphic and text inquiry, historical record viewing, and the like; if the user is a doctor, the system can invoke an online inquiry module on the doctor side to support functions including patient queue viewing, consultation request responding, medical record filling, and the like.
[0099] For the identification of the user type, the user access request can include a user identifier (such as a user ID, an account name, and the like), and the system can query the registration information or authorization information of the user based on the information to determine the user type corresponding to the user; for example, if the user information includes a “role=doctor” field, the user can be identified as a doctor.
[0100] In addition, when the user accesses the system through a specific access platform, channel, or path, the user type can be inferred based on the access platform, channel, or path; for example, access from a hospital HIS system intranet is considered as a medical staff such as a doctor or a nurse by default, and external access from a mobile app is considered as a patient or a family member by default, which are not specifically limited herein.
[0101] Through the above process, the identification of the user type can be used to guide the system to make a differentiated decision when invoking the target service module, so as to achieve precise access control and personalized interaction.
[0102] In step 350, a data access request corresponding to the target service module is constructed according to the target service indicated by the service access request in the service application layer, and the data access request is sent to the data layer.
[0103] The data access request is used to request the data layer to obtain target service data corresponding to the target service module.
[0104] It should be understood that after the target business module call of the business access request is completed, the system generates a corresponding data access request based on the selected target business module, which is used to request the target business data related to the target business module from the data layer. The data access request can include business data types, target member information, etc. The data access request can support the data layer to complete the accurate extraction, semantic association and structured processing of the target business data, and return the processed target business data to the access layer for final display and use.
[0105] Specifically, the business application layer is deployed in the business logic processing environment of the medical management system, and is usually composed of multiple application services oriented to different business fields, such as electronic medical record service, image diagnosis service, laboratory report service, drug management service, etc.
[0106] After receiving the service layer forwarded business access request, the business application layer can parse the business data range and access conditions required to be accessed based on the target hospital identifier, business data type, user identity authentication information and other parameters contained in the business access request.
[0107] In one possible implementation, the business access request includes a target hospital identifier and a business data type; as shown in Figure 5 Step 350 includes: Step 351, if the target hospital indicated by the target hospital identifier is not the hospital corresponding to the current access platform, the target member information is parsed based on the business access request.
[0108] It can be understood that if the target hospital indicated by the target hospital identifier is not the hospital corresponding to the current access platform, the business access request needs to be processed across hospitals, that is, the target member information is parsed based on the business access request.
[0109] In one possible implementation, as shown in Figure 6 Step 351 can further include the following steps: Step 3511, based on the business access request, an access credential is obtained, and in the case of hospital interconnection, the access credential is sent to the target access platform corresponding to the target hospital indicated by the target hospital identifier.
[0110] The access credential is used to establish a secure access session between different hospital platforms. The access credential can be an authorization code, which is not limited here.
[0111] Specifically, after receiving the cross-hospital access business access request, the business application layer first parses the target hospital identifier based on the business access request, and confirms that the target hospital indicated by the identifier is not the hospital corresponding to the current access platform. At this time, a secure channel for cross-hospital access needs to be built.
[0112] To this end, the business application layer can extract the basic parameters (such as user identity authentication information) for cross-hospital access authorization from the business access request and generate an access credential.
[0113] The above-mentioned access credential can be in the form of a single-time valid random string and be encapsulated by an encryption algorithm (such as AES or RSA) combined with a digital signature technology to ensure the confidentiality and tamper resistance of the access credential during transmission.
[0114] Subsequently, under the condition of hospital interconnection (for example, based on the national health industry private network or regional medical data exchange platform), the business application layer sends the generated access credential to the target hospital identification corresponding target access platform, for initiating a cross-hospital session initialization request.
[0115] Step 3513, by interacting with one or more application programming interfaces of the target access platform, the target user information of the user in the target access platform is obtained based on the access credential, and the target member information of the user in the target access platform is determined according to the target user information.
[0116] In one possible implementation, the TOKEN token can be obtained based on the access credential through a first application programming interface of the target access platform; the target user information of the user can be obtained based on the TOKEN token through a second application programming interface of the target access platform; and the target member information can be obtained based on the target user information through a third application programming interface of the target access platform.
[0117] Specifically, after receiving the access credential, the target access platform can verify the access credential through a first application programming interface (API1).
[0118] In one possible implementation, the verification process can include: checking whether the digital signature of the access credential matches the public key of the target hospital; checking whether the validity period of the access credential is within a set time window (for example, valid within 60 seconds or 5 minutes); and verifying whether the source of the access credential is in the trusted access platform whitelist.
[0119] Then, after the verification is passed, the target access platform generates a TOKEN token with timeliness and uniqueness for this cross-hospital access. The TOKEN token is usually a unpredictable random value, and can bind the identity information of the access user, the authorized range, the accessible business data type and the like. The generation of the TOKEN token can rely on a customized hospital internal token mechanism, and be stored in the session management module of the target hospital.
[0120] After the generation of the TOKEN token, the business application layer initiates a target user information obtaining request to the target access platform based on the token through a second application programming interface (API2).
[0121] After receiving the target user information acquisition request, the target access platform parses the user identifier bound to the TOKEN token, and queries the registration information, permission level, role type (such as doctor, nurse, patient, and third-party service personnel) of the user in the user management system of the target hospital.
[0122] The return of the target user information can be in the form of an encrypted data packet, and can be accompanied by a data signature to prevent man-in-the-middle attacks or data tampering.
[0123] Specifically, the target member information includes the user's clinic card number in the target hospital. In addition, the target member information can also include the user's medical record number, outpatient or inpatient registration information, and the like, which are not limited here.
[0124] It should be noted that the target user information can refer to the basic identity information and account information related to the user in the target hospital, which can be used to confirm the user's identity in the target hospital business system and obtain more specific member information, such as the user's name, ID number, mobile phone number, etc. The target member information can refer to the business identity information corresponding to the user in the target hospital internal business system, which is a key identifier for querying medical business data directly, and can be used as a search condition in a data access request to locate the business data related to the user in the target hospital database, such as employee number (doctor or nurse), clinic card number, medical record number, hospitalization number, electronic medical record unique identifier, etc.
[0125] Step 353, generating a data access request based on the business data type indicated by the business access request and the target member information.
[0126] Then, after obtaining the target member information in the business application layer, the data access request for accessing the target hospital data layer can be further generated in combination with the business data type indicated in the business access request.
[0127] Specifically, the business data type can be used to indicate the data category to be accessed, such as outpatient clinic records, inpatient medical records, test results, imaging data, prescription information, etc. The target member information can uniquely identify the user in the target hospital, such as employee number (doctor or nurse), clinic card number, patient unique code, etc.
[0128] When generating the data access request, the business application layer can also bind the business data type and the target member information, and add necessary access control parameters, such as access timestamp, user identity authentication information, session token, etc., to facilitate access permission verification and data scheduling in the data layer.
[0129] At step 355, the data layer access address of the target hospital is determined based on the target hospital identifier, and the data access request is sent to the data layer of the target hospital based on the data layer access address.
[0130] Specifically, the target hospital data layer access address, such as the secure access gateway address, the dedicated line IP address, or the virtual private network (VPN) portal address of the data layer, can be found in the address mapping table or directory service of the hospital interconnection based on the target hospital identifier contained in the business access request.
[0131] After the access address is determined, the data access request can be sent by the business application layer to the target hospital data layer through a secure transmission channel. The secure transmission channel can use a 5G dual-domain private network, a VPN dedicated line, or a TLS / SSL encryption link supporting a national encryption algorithm to ensure that the data access request is not eavesdropped, tampered with, or replayed during transmission.
[0132] At step 370, the target business data corresponding to the target business is obtained based on the data access request at the data layer, and the target business data is encrypted and returned to the access layer through a dual one-way isolation exchange technology.
[0133] The dual one-way isolation exchange technology is used to realize one-way secure transmission of business data between the first network environment and the second network environment.
[0134] In one possible implementation, step 370 can further include the following steps: based on the target member information of the data access request, searching for the target database corresponding to the target member information in the data layer of the target hospital; based on the business data type indicated by the data access request, searching for the target business data in the target database.
[0135] Specifically, after the data layer receives the data access request, the target database corresponding to the target member information is first searched in the target hospital data layer based on the target member information contained in the data access request.
[0136] For example, when the target member information is the patient's medical card number in the target hospital, the data layer can locate the corresponding patient file database or its logical partition in the patient information index table.
[0137] Then, the data layer can further search for the corresponding data record in the target database based on the business data type indicated in the data access request. For example, when the business data type is "test result", the system can search for the record meeting the access condition in the patient's test data table; when the business data type is "image data", the corresponding image file and its structured report can be located and extracted from the image storage system (PACS).
[0138] After obtaining the target service data, the data layer will encrypt it to prevent unauthorized access or tampering during cross-network transmission. The encryption method can support the SM1, SM4 symmetric encryption, SM2 asymmetric encryption, SM3, and SM6 hash algorithms. The encryption key and token used can be generated by the system's foundation layer or accessed through a third-party security platform via the foundation layer.
[0139] After encryption, the data layer sends the encrypted target service data to the access layer through a double one-way isolation exchange technology.
[0140] In one possible implementation, the double one-way isolation exchange technology includes a front-end machine, a back-end machine, and a one-way optical gate. The front-end machine is deployed in the first network environment where the data layer is located, used to receive the encrypted target service data and transmit it to the one-way optical gate. The one-way optical gate is set between the first network environment and the second network environment where the access layer is located, allowing the target service data to be transmitted from the front-end machine to the back-end machine in a predetermined direction only. The back-end machine is deployed in the second network environment where the access layer is located, used to receive the target service data transmitted by the one-way optical gate and transmit it to the access layer.
[0141] Figure 7 A specific implementation diagram of a double one-way isolation exchange technology is shown, as shown in Figure 8 The double one-way isolation exchange technology includes a front-end machine and a back-end machine deployed in different network environments, and a one-way optical gate device between them. The isolation exchange system on the mobile private network side is deployed as a front-end machine, connected to the first network environment (such as the internal secure network where the data layer of the hospital is located). The isolation exchange system on the office private network side is deployed as a back-end machine, connected to the second network environment (such as the external office network or Internet access environment where the access layer is located). Two optical gate devices (labeled as "optical gate (in)" in the figure) realize one-way transmission channels in different directions, ensuring that data can only flow in a predetermined direction and preventing reverse access or data backflow.
[0142] Then, the data layer can deliver the encrypted target service data to the front-end machine on the mobile private network side, transmit it to the back-end machine on the office private network side through the optical gate, and then transfer the target service data to the access layer by the back-end machine, finally displaying it to the user on the access platform.
[0143] Through the above double one-way isolation exchange technology, it can be ensured that the internal network data only goes out but not in. Even in the case of transmitting sensitive medical data across private networks, it can effectively prevent direct intrusion of external networks into the first network environment, realizing the secure interconnection of medical management systems between different private networks.
[0144] In a possible implementation, the method can further include: performing semantic-level data analysis processing on the target service data to obtain a target service data subset associated with the user context information, and returning the target service data subset to the access layer.
[0145] Specifically, the user context information can include, but is not limited to, user type (such as doctor, patient, administrator, etc.), access time, terminal type, service data type, and the like. Based on the user context information, the data layer can perform semantic-level data analysis processing on the target service data through structured extraction, semantic understanding, feature matching, and the like, filter out the most relevant subset data for the current user access purpose, and return the target service data subset to the access layer.
[0146] For example, when a user requests to access the image data of a patient, if the user is the primary doctor and the access purpose is "postoperative review", the system can only extract the image report and operation record of the patient within 7 days after the operation; and when the user is the patient himself and the access purpose is "health consultation", the system can preferentially present the basic image results and explanatory documents.
[0147] In this way, the system can realize personalized data delivery at the data layer, improve data response efficiency, reduce redundant transmission content, and at the same time enhance the accuracy and security of terminal display.
[0148] At step 390, the encrypted target service data is decrypted at the access layer, and the decrypted target service data is displayed on the access platform, so that the user can view the target service data on the access platform.
[0149] Specifically, after receiving the target service data transmitted through the double one-way isolation exchange technology and encrypted by the data layer, the access layer can call a local decryption module or access a decryption service provided by the basic layer to decrypt the target service data.
[0150] In a possible implementation, the decryption process can be performed based on a cryptographic algorithm matched with the encryption process, such as the symmetric encryption algorithms SM1 and SM4, the asymmetric encryption algorithm SM2, the hash algorithms SM3 and SM6, and the like. The keys and tokens required for decryption can be generated and managed by the basic layer, or can be provided by the basic layer by accessing a third-party security platform through a secure interface.
[0151] After decryption, the access layer displays the obtained plaintext target service data through the access platform. The access platform can present the data in different ways such as list, chart, electronic medical record view, and examination report view according to the type of the service data, so as to ensure that the user can intuitively and accurately view the data content.
[0152] In a possible implementation, the access layer can also perform permission control and audit recording on the displayed data, for example, verifying whether a user has permission to view specific data according to user identity authentication information and an access token, and recording information such as time, source IP, operation type and the like of each data access, to meet medical data security and compliance requirements.
[0153] Through the above process, secure access and display of target business data across different network environments in the medical management system are achieved, and a complete business access link is constructed between the access layer, the service layer, the business application layer and the data layer, ensuring that a business access request initiated by a user in an external network environment can be securely transmitted to the data layer in an internal network environment for processing after authentication, routing and data generation, and the encrypted target business data is unidirectionally returned to the access layer for decryption and display.
[0154] The above process realizes physical isolation and unidirectional secure transmission between the first network environment and the second network environment through the double unidirectional isolation exchange technology and the encryption and decryption mechanism, prevents internal data leakage or illegal access; at the same time, through decryption and display of the data by the access layer, the user can efficiently and conveniently obtain the required business information under the premise of ensuring data security and compliance, thereby improving the availability and access security of medical data.
[0155] Please refer to Figure 8 In an exemplary embodiment, the medical management system further includes a foundation layer. Accordingly, the above method can further include the following steps: Step 410, obtaining resource usage information of the access layer, the service layer, the business application layer and the data layer through the foundation layer.
[0156] In this embodiment, the foundation layer serves as the bottom support platform of the medical management system, and can monitor the running load and resource occupation of each system level. The resource usage information can include, but is not limited to, CPU occupation rate, memory usage, network bandwidth occupation, storage space usage and encryption / decryption processing resource consumption, etc. The resource usage information can be periodically reported to the foundation layer through the monitoring agent module deployed in each layer, or can be collected in real time through a centralized resource management interface.
[0157] Step 430, based on the resource usage information, the foundation layer allocates or adjusts resources for data transmission between the access layer, the service layer, the business application layer and the data layer.
[0158] Specifically, the base layer can optimize the allocation of computing resources, storage resources and network resources of the data layer in combination with the number of current access requests, data transmission volume, service processing type and other factors. For example, when the access volume surges, the base layer can temporarily add computing nodes or bandwidth quotas for the data layer to ensure the stability and low latency of the service access link; when the access volume decreases, the excess resources can be released to improve the overall resource utilization.
[0159] At step 450, if it is detected that the resource usage of the access layer, the service layer, the service application layer or the data layer exceeds a set threshold, the base layer re-allocates resources to the access layer, the service layer, the service application layer and / or the data layer.
[0160] Specifically, the base layer can pre-configure multiple threshold strategies, such as an 80% warning value for CPU occupancy, a peak limit for network bandwidth, etc. When it is detected that the resource usage of a certain layer exceeds a set threshold, the base layer can trigger a resource reallocation process to dynamically schedule the resources of idle or low-load nodes to the high-load layer; if necessary, it can also trigger a load balancing mechanism to migrate part of the service requests to other available nodes, thereby avoiding the performance degradation of the system caused by single-point overload.
[0161] In one possible implementation, in addition to being used to collect resource usage information of the access layer, the service layer, the service application layer and the data layer and to perform dynamic resource allocation, the base layer can also provide unified security support capabilities for the system.
[0162] Specifically, the base layer can generate or manage security credentials such as keys and access tokens involved in data encryption. The keys and access tokens can support the SM series cryptographic algorithms of the national cryptography standard, including but not limited to the SM1 and SM4 symmetric encryption algorithms, the SM2 asymmetric encryption algorithm, the SM3 hash algorithm, and the SM6 and other new generation cryptographic algorithms.
[0163] Further, in actual deployment, the base layer can either locally deploy a key management module to directly generate and distribute the keys and tokens, or interface with a third-party security platform through a security interface to have the third-party security platform generate and manage the keys and tokens.
[0164] In the above manner, the confidentiality, integrity and traceability of service access requests, data access requests and target service data can be ensured during transmission and processing in a cross-network environment.
[0165] Under the action of the above-mentioned embodiments, by uniformly collecting the resource usage information of each system level in the base layer, and based on the real-time monitoring results, the dynamic allocation and adjustment of resources are realized, and the on-demand allocation and load balancing of data transmission resources between the access layer, the service layer, the business application layer and the data layer are realized. When the resource usage of any layer exceeds the set threshold, resource reallocation can be triggered in time to avoid single-point overload and ensure the stability and response speed of the system in high-concurrency and complex business scenarios, thereby improving the overall operation efficiency and reliability of the medical management system.
[0166] Figures 9 to 10 is a specific implementation schematic diagram of a data access method of a medical management system in an application scenario, and the application scenario is applicable to Figure 1 the medical management system shown in the figure.
[0167] Now the application scenario will be described in conjunction with Figure 9 and Figure 10 A user accesses the access platform of the medical management system through a mobile terminal (such as a secure mobile phone, a secure tablet computer, etc.) deployed with a secure access application. The user terminal first establishes a secure connection with the access layer through a 5G special network, and the connection is realized through a 5G dual-domain private network provided by an operator.
[0168] Specifically, the user terminal connects to a second user plane function network element (UPF) by accessing a 5G special base station. The second UPF can be deployed in a public network access area and is used to carry business access requests from the Internet or a public 5G network; the first UPF is deployed in a private network access area (5G dual-domain private network) and is used to carry business access requests from medical private network users. The system can intelligently select the first UPF or the second UPF for data access based on business policies and user identity authentication information, realize dynamic switching and shunting of access paths, and thus stably and safely access target business data in different network environments.
[0169] It should be noted that the first UPF can be one of the access points for accessing the first network environment, and the business traffic carried by the first UPF is ultimately introduced to the core resources such as the data layer in the first network environment; the second UPF can be one of the access points for accessing the second network environment, and the business traffic carried by the second UPF is introduced to the core resources such as the access layer in the second network environment.
[0170] When a user initiates a business access operation (such as calling patient image data or viewing test reports) on the access platform, the access layer generates a business access request based on the operation and sends it to the service layer. The service layer calls a target business module (such as a PACS image system access module or a LIS test system access module) matched with the user type according to the business access request, and forwards the business access request to the business application layer.
[0171] The service application layer generates a data access request according to a service access request, and determines a target hospital data layer that needs to be accessed based on a target hospital identifier and a service data type. When a user needs to access non-hospital data, the system can obtain target member information (such as a user's medical card number in a target hospital) across hospitals through an authorization code, a TOKEN token, or other mechanisms, and encapsulate the target member information and the service data type into the data access request.
[0172] Then, the data access request can be securely transmitted to the data layer of the target hospital through the double one-way isolation exchange technology of the secure isolation area (including a front-end machine, a one-way optical gate, and a back-end machine). After receiving the data access request, the data layer searches for the required target service data (such as ultrasound video streams and test report data) from the corresponding target database, and encrypts the data using the encryption mechanism provided by the basic layer (supporting SM1, SM4, SM2, SM3, and SM6 cryptographic algorithms).
[0173] In scenarios involving large-scale ultrasound images, the data acquisition module deployed in the data layer can collect real-time images of ultrasound equipment through HDMI, use Slice hard coding for low-latency video encoding, and efficiently transmit the data to the data center through the pass-through video transmission protocol. Then, the cloud processing module can work with the basic layer to perform real-time processing and AI analysis on the data using distributed computing nodes and DPU hardware acceleration.
[0174] Further, the encrypted target service data is transmitted to the network environment where the access layer is located through the one-way optical gate. After decryption in the access layer, the data is displayed to the user on the access platform, thereby realizing the secure and fast access of the user to the internal service data of the medical institution in an external network environment.
[0175] In the present application scenario, by introducing an access path dynamic selection mechanism based on service policies and user identity authentication information in the access layer, intelligent switching and service offloading between the first UPF and the second UPF are realized, so that the system can maintain the stability and security of service access in different network environments; in cooperation with the target member information acquisition mechanism for cross-hospital access, the data access consistency and service processing continuity of the user among multiple medical institutions are ensured; in combination with the double one-way isolation exchange technology and the encryption mechanism of the basic layer, the confidentiality and integrity of the service data during cross-network transmission are ensured; when high-bandwidth services such as large-scale ultrasound images are involved, low-latency video acquisition and efficient transmission are realized using Slice hard coding and the pass-through video transmission protocol, and further combined with the AI processing capability of the cloud distributed computing nodes and DPU hardware acceleration, real-time processing and intelligent analysis of large amounts of medical images are realized, thereby improving the overall access efficiency, data security, and cross-institution service collaboration capability of the system.
[0176] It should be understood that although each step in the flowchart of the accompanying drawings is shown in sequence according to the direction of the arrow, these steps are not necessarily executed in sequence according to the direction of the arrow. Unless explicitly stated herein, the execution of these steps is not strictly limited in sequence, and they can be executed in other sequences. Moreover, at least part of the steps in the flowchart of the accompanying drawings can include multiple sub-steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution sequence is not necessarily sequential, but can be alternately executed with at least part of other steps or sub-steps or stages of other steps.
[0177] The following is an apparatus embodiment of the present application, which can be used to execute the data access method of the medical management system involved in the present application. For details not disclosed in the apparatus embodiment of the present application, please refer to the method embodiment of the data access method of the medical management system involved in the present application.
[0178] Please refer to Figure 11 In the embodiment of the present application, a data access apparatus 900 of a medical management system is provided, which can be deployed in a medical management system including an access layer, a service layer, a business application layer and a data layer. The data layer is deployed in a first network environment, and the access layer is deployed in a second network environment isolated from the first network environment.
[0179] The apparatus 900 includes but is not limited to a business access module 910, a business calling module 930, a data access module 950, a data acquisition module 970 and a data display module 990.
[0180] The business access module 910 is configured to provide an access platform for a user in the access layer, and generate a business access request based on the business access operation of the user on the access platform, and send the business access request to the service layer. The business access request is used to indicate a target business requested to be accessed by the user. The business calling module 930 is configured to call a target business module corresponding to the target business in the service layer according to the business access request, and forward the business access request to the business application layer according to the target business module. The data access module 950 is configured to construct a data access request corresponding to the target business module according to the target business indicated by the business access request in the business application layer, and send the data access request to the data layer. The data access request is used to request the data layer to acquire target business data corresponding to the target business module. The data acquisition module 970 acquires target business data corresponding to the target business based on data access at the data layer, performs encryption processing on the target business data, and returns the encrypted target business data to the access layer through a double one-way isolation exchange technology; the double one-way isolation exchange technology is used to realize one-way secure transmission of business data between the first network environment and the second network environment. The data display module 990 is configured to perform decryption processing on the encrypted target business data at the access layer, and display the decrypted target business data on the access platform, so that the user can view the target business data on the access platform.
[0181] It should be noted that the data access device of the medical management system provided in the above embodiments only divides the above functions for example, and in actual application, the above functions can be distributed to different functional modules according to needs, that is, the internal structure of the data access device of the medical management system is divided into different functional modules to complete all or part of the functions described above.
[0182] In addition, the data access device of the medical management system and the data access method of the medical management system provided in the above embodiments belong to the same concept, and the specific way in which each module performs operations has been described in detail in the method embodiments, which will not be repeated here.
[0183] Compared with the related art, the present scheme realizes secure access and display of target business data across different network environments in the medical management system, and builds a complete business access link between the access layer, the service layer, the business application layer and the data layer, ensuring that a business access request initiated by a user in an external network environment can be securely transmitted to the data layer of the internal network environment for processing after authentication, routing and data generation, and the encrypted target business data is returned to the access layer for decryption and display.
[0184] The above process realizes physical isolation and one-way secure transmission between the first network environment and the second network environment through the double one-way isolation exchange technology and the encryption and decryption mechanism, preventing internal data leakage or illegal access; at the same time, through the decryption and display of the data by the access layer, the user can efficiently and conveniently obtain the required business information under the premise of ensuring data security and compliance, thereby improving the availability and access security of medical data.
[0185] The above only describes some embodiments of the present application, and it should be noted that for those skilled in the art, without departing from the principles of the present application, some improvements and refinements can also be made, which should be regarded as the protection scope of the present application.
Claims
1. A data access method for a medical management system, characterized in that: The system includes an access layer, a service layer, a business application layer, and a data layer; wherein the data layer is deployed in a first network environment, and the access layer is deployed in a second network environment isolated from the first network environment; the method includes: Providing an access platform for the user at the access layer, and generating a service access request based on the service access operation of the user at the access platform, and sending the service access request to the service layer; the service access request is used to indicate the target service requested by the user; Invoking a target business module corresponding to the target business at the service layer according to the business access request, and forwarding the business access request to the business application layer according to the target business module; The business application layer constructs a data access request corresponding to the target business module according to the target business indicated by the business access request, and sends the data access request to the data layer; the data access request is used to request the data layer to obtain the target business data corresponding to the target business module; obtaining, at the data layer, target business data corresponding to the target business based on the data access request, encrypting the target business data, and returning the encrypted target business data to the access layer through a dual unidirectional isolation switching technology; wherein the dual unidirectional isolation switching technology is used to implement unidirectional secure transmission of business data between the first network environment and the second network environment; The encrypted target business data is decrypted at the access layer, and the decrypted target business data is displayed on the access platform, so that the user can view the target business data on the access platform.
2. The method according to claim 1, wherein The calling, at the service layer, of a target service module corresponding to the target service according to the service access request includes: determining a user type of the user according to the service access request; Based on the user type and according to the target service indicated by the service access request, a corresponding target service module is called.
3. The method according to claim 1, wherein The service access request includes a target hospital identifier and service data type; Generating a data access request according to the service access request at the service application layer and sending the data access request to the data layer includes: If the target hospital indicated by the target hospital identifier is not the hospital corresponding to the currently accessed platform, obtaining target member information based on the business access request analysis; generating a data access request based on the business data type indicated by the business access request and the target member information; The data layer access address of the target hospital is determined based on the target hospital identifier, and the data access request is sent to the data layer of the target hospital based on the data layer access address.
4. The method according to claim 3, wherein The obtaining of target member information based on the business access request parsing includes: Obtaining an access credential based on the service access request, and sending the access credential to a target access platform corresponding to the target hospital indicated by the target hospital identifier when the hospitals are interconnected; By interacting with one or more application programming interfaces of the target access platform, the target user information of the user on the target access platform is obtained based on the access credentials, and the target member information of the user on the target access platform is determined according to the target user information.
5. The method according to claim 3, wherein Acquiring target service data corresponding to the target service based on the data access request at the data layer includes: Based on the target member information in the data access request, searching for a target database corresponding to the target member information in the data layer of the target hospital; Based on the business data type indicated by the data access request, the target business data is searched in the target database.
6. The method according to claim 1, wherein After the data layer obtains the target service data corresponding to the target service based on the data access request, the method further includes: Perform semantic-level data parsing on the target business data to obtain a target business data subset associated with the user context information, and return the target business data subset to the access layer.
7. The method according to claim 1, wherein The dual unidirectional isolation switching technology includes a front-end processor, a back-end processor and a unidirectional optical gate; The step of returning the encrypted target service data to the access layer through the dual unidirectional isolation exchange technology includes: The first network environment deployed at the data layer is used to receive the encrypted target business data and transmit the target business data to the one-way optical gate; The one-way optical gate is set between the first network environment and the second network environment where the access layer is located, and the one-way optical gate only allows the target service data to be transmitted from the front-end to the back-end in a predetermined direction; The backend is deployed in the second network environment where the access layer is located, and is used to receive the target business data transmitted through the one-way optical gate and transmit the target business data to the access layer.
8. The method according to claim 1, wherein The sending the service access request to the service layer includes: A public communication domain and a secure communication domain are established in a communication network element through a 5G dual-domain private network, wherein the secure communication domain is connected to the first network environment where the data layer is located, and the public communication domain is connected to the second network environment where the access layer is located; performing dual-domain identity authentication on the user terminal corresponding to the access layer in the public communication domain and the secure communication domain based on a user identity authentication rule in the communication network element; If the identity authentication passes, if the service access request points to target service data in the first network environment, forwarding the service access request to the data layer through the secure communication domain; If the service access request is directed to an external Internet resource, the service access request is forwarded to an external server through the public communication domain.
9. The method according to any one of claims 1 to 8, wherein The system further includes a base layer; and the method further includes: Obtain resource usage information of the access layer, the service layer, the business application layer and the data layer through the basic layer; Allocate or adjust, at the basic layer, resources for data transmission between the access layer, the service layer, the business application layer, and the data layer based on the resource usage information; If it is detected that the resource usage of the access layer, the service layer, the business application layer or the data layer exceeds a set threshold, resources are re-allocated to the access layer, the service layer, the business application layer and / or the data layer through the basic layer.
10. A medical management system, characterized in that: The system includes an access layer, a service layer, a business application layer and a data layer; The access layer is used to provide an access platform for users, generate a service access request based on the service access operation of the user on the access platform, and send the service access request to the service layer; receiving the encrypted target service data sent by the data layer, decrypting the encrypted target service data, and displaying the decrypted target service data on the access platform so that the user can view the target service data on the access platform; the service access request is used to indicate the target service that the user requests to access; The service layer is configured to call a corresponding target business module according to the business access request, and forward the business access request to the business application layer according to the target business module; The business application layer is configured to construct a data access request corresponding to the target business module according to the target business indicated by the business access request, and send the data access request to the data layer; The data access request is used to request the data layer to obtain the target business data corresponding to the target business module; The data layer is configured to receive the data access request, obtain target business data corresponding to the target business based on the data access request, encrypt the target business data, and return the encrypted target business data to the access layer through a dual unidirectional isolation exchange technology; Among them, the data layer is deployed in a first network environment, and the access layer is deployed in a second network environment isolated from the first network environment; the dual unidirectional isolation switching technology is used to realize unidirectional secure transmission of business data between the first network environment and the second network environment.
Citation Information
Patent Citations
Method and system for isolating network transparent service access based on double one-way switching equipment
CN110912940A
Business processing method and device, equipment, and storage medium
CN112650732A
Electric power marketing data sharing application platform
CN114297290A
Remote medical monitoring system and method
CN116980438A
Equipment label management system based on big data
CN117807070A
Cited By
Data communication method suitable for internal and external network isolation scene
CN121217483A
