Medical information sharing method based on smart medical treatment

Abstract

The invention relates to the technical field of medical information sharing methods, in particular to a medical information sharing method based on intelligent medical treatment. The method comprises the following steps: firstly, deploying distributed intelligent gateway nodes in a medical institution, constructing a gateway network framework containing a home hospital address matching library, and dynamically associating patient identity features with home hospital codes; a trans-provincial data source is accurately locked through a two-factor positioning engine (medical insurance insured places and last doctor seeing records); the method comprises the following steps: capturing original medical data of a home in real time based on a streaming processing mechanism, generating a structured first-aid abstract (such as an allergy history and an operation record) through a dynamic conversion pipeline, and encrypting and packaging the structured first-aid abstract into a cross-domain first-aid data packet with a triple architecture by adopting a target public key; and finally, cross-provincial second-level safe direct arrival of key medical information is realized. According to the method, the problem of information blind areas caused by cross-provincial domain data retrieval failure in remote first aid is solved, and meanwhile, the data positioning precision and the transmission efficiency are continuously optimized through a closed-loop feedback mechanism.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of medical information sharing methods, in particular to a medical information sharing method based on smart medical treatment. BACKGROUND

[0002] With the popularization of smart medical technology, the coverage of medical data electrification has been significantly improved, but cross-regional medical collaboration still faces the challenge of information fragmentation. This contradiction is particularly acute in the context of emergency treatment in a foreign place: when a comatose patient suddenly becomes seriously ill in an unfamiliar city, the receiving hospital is forced to conduct exploratory treatment with risks or repeat tests because it cannot immediately access the patient's home hospital's key information such as allergy history and surgical records. Existing technologies usually alleviate the problem of local data sharing by establishing regional health information platforms (such as city health clouds), i.e., emergency centers can query the platform's pre-stored local patient records to obtain limited information.

[0003] Although regional platforms can collect medical data within a certain range, they still have obvious shortcomings when dealing with cross-provincial and cross-regional emergency needs: there is a lack of efficient and direct information exchange capabilities between medical systems in different provinces or regions. Specifically, when a patient's vital medical history information (such as severe allergy history to certain drugs, major disease diagnosis, or previous surgery) is stored in a system of a hospital in another province, existing platforms neither have a mechanism to automatically obtain these external data nor can they organize and present these foreign information to emergency doctors within the extremely short time required for emergency treatment. SUMMARY

[0004] The present application provides a medical information sharing method based on smart medical treatment, which dynamically locks the local medical data source through an intelligent gateway node and real-time extracts structured emergency summaries (such as allergy history and surgical records) based on an encrypted streaming mechanism, ultimately generating encrypted data packets that can be directly transmitted across provinces, thereby solving the problems raised in the background art, i.e.:

[0005] In the context of emergency treatment in a foreign place, the real-time retrieval of cross-provincial key medical information (such as allergy history and surgical records) is ineffective due to the closed architecture of existing regional health information platforms.

[0006] To achieve the above purpose, the medical information sharing method includes the following steps:

[0007] S1, deploying an intelligent gateway node in a medical institution, generating key configuration information including node identity, dynamic gateway registration index, local hospital address matching library, and encrypted public key certificate set through registration and configuration;

[0008] S2, performing medical data retrieval operations based on the key configuration information, the steps of which are as follows:

[0009] S2.1, use dynamic gateway registration index to establish node communication link;

[0010] S2.2, bind node identity to generate digital identity certificate;

[0011] S2.3, call local hospital address matching library to parse patient identity characteristics, and output target hospital code;

[0012] S2.4, load encrypted public key certificate set to build secure channel;

[0013] S3, execute cross-domain medical data access operation, and the steps are as follows:

[0014] S3.1, initiate structured emergency summary request based on target hospital code;

[0015] S3.2, convert local original data into standardized emergency summary data, and encrypt using target public key;

[0016] S3.3, generate cross-domain emergency data packet containing digital signature and encrypted summary, and access real-time cross-provincial key medical information.

[0017] In the above technical solution, the design concept is derived from the solution of the three contradictions of timeliness, security and cross-domain collaboration reliability in the medical emergency scene: first, the accurate mapping rules of the local hospital address matching library replace the static data cache of the traditional regional platform, solving the problem of "data source drift" caused by the flow of patients across provinces. If this design is missing, relying only on administrative regional division will not be able to dynamically track the latest local hospital of the patient, resulting in failure of key information positioning; second, the synchronous execution mechanism of streaming processing and encryption breaks through the serial bottleneck of traditional "conversion first and then encryption", if the regular process is to convert the original data completely and then encrypt, the data processing delay will exceed the golden time window of emergency; finally, the three-element encapsulation structure of the cross-domain emergency data packet binds the data source credibility through digital signature, guarantees the transmission confidentiality through encrypted summary, and controls the timeliness risk through life cycle parameters. If only single encryption transmission is used, it cannot meet the requirements of responsibility tracing and data self-destruction in medical collaboration.

[0018] On this basis, the cross-domain emergency data packet is standardized encrypted and integrity encapsulated, and the steps are as follows:

[0019] Extract the digital signature of the message header to verify the legitimacy of the requestor's identity;

[0020] Decompose the encrypted emergency summary fragment of the core data body;

[0021] Read the life cycle parameters marked by the routing control layer;

[0022] Generate a double-reinforced secure medical data transmission body.

[0023] In another technical solution, the reverse decryption operation is performed based on the private key certificate preset by the secure medical data call gateway to generate a cross-domain emergency cooperation closed-loop report including medical data items, use effect, operation compliance audit log and routing strategy suggestion.

[0024] This technical solution is based on the precise control demand of the whole life cycle management of medical data: firstly, the secure transmission body is constructed through threefold signature verification and dynamic parameter analysis (extracting signature verification identity, disassembling encrypted fragments, and reading life cycle parameters), if this step is missing, such as relying on a single encryption layer, it cannot simultaneously prevent counterfeit attacks in the middle of transmission (no signature verification), data tampering risks (no digest disassembly verification) and key long-term retention risks (no life cycle control); secondly, based on the closed-loop design of private key decryption and three-dimensional report generation, if only the basic decryption is performed without associating the audit log and the routing strategy (such as traditional medical systems), the cross-domain cooperation will fall into an inefficient cycle of "single effective, unable to iterate", which cannot optimize emergency decision rules through historical data review, nor can it eradicate the recurrence of cross-province transmission delays caused by rigid routing strategies.

[0025] Compared with the prior art, the beneficial effects of the present application are:

[0026] 1. The closed-loop feedback mechanism of the present application converts each cross-domain medical data call into a system evolution driving force. When an emergency doctor calls out-of-town surgical records or allergy history, the use efficiency and decision results automatically generate optimization parameters, dynamically correct the weight factor in the matching rules of the local hospital, and continuously improve the data positioning accuracy; at the same time, the network topology path is reconstructed according to the encryption transmission delay record, so that the medical information sharing network has the ability of self-training, and each call drives it to iterate and upgrade in a more accurate and efficient direction.

[0027] 2. Unlike the static running mode of traditional medical platforms, the present design deeply couples the data use value to the system evolution chain. The cross-province medical information obtained in clinical emergency not only serves the rescue decision at that time, but also continuously deposits into three kinds of core knowledge assets through the tamper-proof characteristics of block chain evidence: the path selection experience set for optimizing the local matching library, the security transmission parameter library for strengthening the encrypted channel, and the clinical utility atlas for calibrating the decision rule engine. These three together constitute the "dynamic gene library" of the intelligent medical cooperation network, so that the system naturally forms the precise compensatory ability of cross-domain medical cooperation in continuous operation. BRIEF DESCRIPTION OF DRAWINGS

[0028] Figure 1 It is a whole flow structure schematic diagram of the medical information sharing method based on intelligent medical treatment of the present application;

[0029] Figure 2The specific flowchart of step S1 of the present application is shown in the following. DETAILED DESCRIPTION

[0030] The technical solutions in the embodiments of the present application will be clearly and completely described in the embodiments of the present application in combination with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0031] Meanwhile, some technical terms are explained here:

[0032] The special heartbeat protocol refers to a double-effect maintenance mechanism for real-time monitoring of the survival state of an intelligent gateway node and the integrity of an encrypted communication link.

[0033] Currently, for the problem of real-time access failure of cross-provincial key medical information (such as allergy history, operation record) in an out-of-town emergency scene due to the closed architecture of the existing regional health information platform, the present application provides a medical information sharing method based on smart medical care, as shown in Figure 1 , including the following steps:

[0034] S1, deploying an intelligent gateway node in a medical institution, generating key configuration information including node identity identification, dynamic gateway registration index, local hospital address matching library and encrypted public key certificate set through registration and configuration;

[0035] S2, performing a medical data access operation based on the key configuration information, and the steps are as follows:

[0036] S2.1, establishing a node communication link using the dynamic gateway registration index;

[0037] S2.2, binding the node identity identification to generate a digital identity certificate;

[0038] S2.3, calling the local hospital address matching library to analyze the patient identity characteristics, and outputting the target hospital code;

[0039] S2.4, loading the encrypted public key certificate set to build a secure channel;

[0040] S3, performing a cross-domain medical data access operation, and the steps are as follows:

[0041] S3.1, initiating a structured emergency summary request based on the target hospital code;

[0042] S3.2, converting the local original data into standardized emergency summary data, and encrypting using the target public key;

[0043] S3.3, generating a cross-domain emergency data packet containing a digital signature and an encrypted abstract, and real-time access to key medical information across provinces.

[0044] Through the synergistic effect of the above steps, a real-time data channel of a cross-regional heterogeneous medical system is constructed, and structured emergency abstracts (such as drug contraindications and past diagnoses) of a patient's local hospital are obtained in a timely manner in a cross-provincial emergency scene, providing accurate information support for emergency decision-making and effectively eliminating information blind spots in cross-domain medical collaboration.

[0045] As shown in Figure 2 , step S1 of the present application is to deploy distributed medical intelligent gateway nodes in various medical institutions participating in medical information sharing and complete core function configuration. Specifically, the primary task of this step is to establish a decentralized network access infrastructure within the target region, enabling medical nodes at all levels to have basic capabilities for cross-domain communication and data calling.

[0046] To achieve this goal, first, a lightweight intelligent gateway agent software is deployed in each medical institution participating in the system, including provincial hospitals, city-level emergency centers, and county-level primary hospitals. This agent software, as a core access module, needs to be installed in the secure isolation area of the hospital information system. During deployment, each gateway node needs to submit a registration request to the central coordination service. After successful registration, the node will obtain a node identity issued by the system, and upload the standardized code of its affiliated medical institution (such as the unified social credit code) and its physical location information (including the province / city-level regional code) to the coordination service. The central coordination service builds and maintains a unified dynamic gateway registration index by collecting all network registration information, which records the location identifier and network status of all access nodes in real time, forming a map of the distributed network.

[0047] After registration, key routing functions are configured for each node. The core is to build a local hospital address matching library, which is generated according to the following rules: based on the insurance settlement system's insured area coding rules (the first 6 digits of the ID card mapping the region) and the patient's historical medical records (obtained from the regional platform), a mapping relationship table between the patient's identity information segment and the local hospital's standard code is dynamically generated. It should be noted that this matching library only stores the logical association of "identity feature code -> local hospital code" and does not involve the patient's original medical data. For example, when the patient's ID card number is input, the matching library can output the corresponding three-A hospital code of the medical insurance participating region.

[0048] Meanwhile, to ensure the security of cross-node communication, security keys need to be exchanged between gateway nodes. The specific process is as follows: each node generates a dedicated asymmetric key pair, and transmits the public key part thereof to adjacent provinces or potential target nodes for review through an encrypted channel. The receiver binds the public key to the node identity and stores it in the local encrypted public key certificate library. At this point, each intelligent gateway node is endowed with five core capabilities: network access capability to access the point-to-point network through a secure protocol, identity identification capability through node identity and medical institution coding identification, routing positioning capability based on the data source inferred by the local hospital address matching library, secure communication foundation capability through the pre-stored public key to establish an encrypted channel, and network visibility capability to achieve global node positioning through the dynamic gateway registration index.

[0049] Finally, all intelligent gateway nodes that have completed deployment and initialization carry their key configuration information, including the node identity issued by the central coordination service, the dynamic gateway registration index synchronized throughout the network, the local hospital address matching library storing the mapping relationship, and the encrypted public key certificate set for secure communication, which together constitute the activated distributed gateway network framework. This complete technical architecture will be passed on to step S2 as a basic operating platform, providing three-layer support of network layer, routing layer and security layer for performing real-time cross-domain data review.

[0050] Step S2 of the present application is to realize the cooperative activation and functional closed loop of distributed medical intelligent gateway nodes through systematic integration. Specifically, after completing the basic deployment configuration, the pre-set technical components need to be converted into a complete functional system that can run in real time to support subsequent cross-domain medical data review operations.

[0051] First, the network access capability of the node is materialized into a channel. The intelligent gateway calls the preloaded transport layer security protocol set (TLS1.3) to establish a node communication link with the distributed point-to-point communication network. This process implements a double verification mechanism: on the one hand, it completes a two-way identity authentication handshake by exchanging digital certificates; on the other hand, it verifies the compliance status and network access qualifications of the target node by querying the dynamic gateway registration index maintained by the central coordination service in real time. This double guarantee enables the node to obtain the transmission capability of legal access to the distributed network, establishing a bottom channel foundation for cross-institution communication.

[0052] On this basis, the identity authentication system is solidified. The node identity obtained during registration is bound with the legal standard code of the medical institution through the hardware security module (HSM) to perform asymmetric key binding operation, and a non-detachable digital identity certificate is generated. The certificate contains the encrypted and signed institutional attribution information (including administrative division code and service type identification), which is automatically implanted in the message header check bit in all cross-domain communication requests. When the receiving gateway parses the certificate, it can instantly verify the legal authorization status of the data source, ensuring the traceability of the entire link operation.

[0053] Then the routing positioning capability core engine is activated. The node loads the built-in local hospital address matching library instance, which generates data source coordinates by real-time parsing of the key elements of the patient's identity. Specifically, the algorithm in the library automatically extracts the first 6 digits of the patient's ID card administrative division code and matches it with the pre-set national medical insurance coverage area mapping rules. At the same time, it associates the patient's latest medical records in the regional health information platform in the past 12 months, and calculates the target hospital code of the optimal local hospital through a weight decision model. The entire positioning process can complete the precise locking of cross-provincial data sources within 200 milliseconds.

[0054] Further deploy the security communication foundation capability encryption system. The node preloads a set of asymmetric encryption public key certificates authenticated by the central coordination service through the key manager, and stores them in the local encryption certificate cache area according to the target institutional standard code. When initiating a cross-domain data request, the system automatically retrieves the corresponding certificate to generate a temporary session key and build an end-to-end encrypted transmission channel. This mechanism ensures that sensitive data such as patient allergy history and surgical records are always in a dynamic encryption state during transmission, fundamentally avoiding the risk of man-in-the-middle attacks.

[0055] Subsequently, the global node visibility capability network penetration is strengthened. Relying on the continuous synchronization mechanism of dynamic gateway registration index, the central coordination service pushes the global node change data packet every 5 seconds through a special heartbeat protocol. The lightweight routing table maintained locally by the node is updated in real time with key metadata, including the IP address and port number of new nodes, the service invalidation timestamp of offline nodes, and the optimal path quality index of the cross-provincial backbone network (based on real-time delay and packet loss rate calculation).

[0056] Step S2 is deeply coupled through the system service bus to form a trinity of functional integration: the transmission authentication layer fuses network access capability and identity capability to build a trusted communication pipeline, providing a two-way authentication basis for cross-domain interaction; the data routing layer integrates routing positioning capability and secure communication capability, ensuring the accuracy and confidentiality of data transmission through precise address resolution and end-to-end encryption mechanism; the network governance layer internalizes the global node visibility capability, realizing dynamic monitoring of the network topology and path optimization. After the initialization of the runtime environment is completed, the integration generates a complete intelligent gateway running instance, which fully carries the distributed communication protocol stack, the digital identity certificate set encrypted by the hardware security module, the local positioning engine for real-time operation, the dynamic key pool preloaded with encrypted certificates, and the network topology table updated at a millisecond level, which together constitute a standardized functional module that can be directly deployed on the hospital front-end server. Finally, through binary serialization packaging, an executable capability image is formed, which is handed over to the cross-domain data retrieval process execution phase of step S3.

[0057] Step S3 of the present application is to execute real-time retrieval and standardized packaging of cross-domain medical data based on the executable capability image. Specifically, the core task of this step is to use the core components integrated in the intelligent gateway running instance handed over by step S2 to realize the accurate acquisition, dynamic conversion and secure transmission of key medical data of patients in the local hospital in emergency scenarios.

[0058] When receiving the executable capability image delivered by step S2, the system first loads the functional modules carried by it to the memory operation platform during the initialization of the runtime environment. This includes parsing the five core capability execution carriers packaged in the image: the distributed communication protocol stack builds a point-to-point transmission channel, the hardware encrypted identity certificate set provides node legitimacy authentication, the local positioning calculation engine maintains patient data source addressing capability, the dynamic encrypted certificate pool saves preloaded public key certificates, and the millisecond-level updated network topology table continuously tracks the status of all network nodes. These components together constitute the cross-domain data retrieval operation base, providing technical support for the subsequent processes of this step.

[0059] When initiating a cross-domain data retrieval request through the operation base, the local positioning calculation engine instantly parses the input patient identity information features. The engine automatically extracts the regional code segment in the patient's identity card number, combines it with the patient's medical insurance participation location attribute and last visit trajectory, and generates a standardized coded identifier for the target local hospital. The system then accesses the network topology table to obtain the service access coordinates corresponding to the code, and activates the secure transmission channel of the distributed communication protocol stack. The data request instruction is issued in the form of a structured tag vector, clearly marking the key data type identifiers that need to be retrieved, such as the allergy history set tag or the major surgery record tag, and other clinical emergency information.

[0060] The territorial hospital gateway starts a data dynamic conversion pipeline immediately after responding to the request. The local medical information system extracts the territorial raw data and maps it into a standardized emergency summary fragment in real time through the built-in streaming processor. The data routing layer uses an asymmetric encryption algorithm to encapsulate the summary data, and the encryption process can be represented as:

[0061] E data = Enc(PK target , D FHIR );

[0062] In the formula, E data represents the encrypted data block output;

[0063] Enc() is an encryption function;

[0064] PK target represents the public key of the target node extracted from the dynamic encryption certificate pool;

[0065] D FHIR represents the standardized emergency summary data.

[0066] The encryption mechanism ensures that the transmission process meets the compliance requirements of sensitive medical data.

[0067] Finally, a standardized cross-domain emergency data packet is generated, which is divided into three encapsulation layers: the message header is embedded with the node digital signature generated by the manual gateway hardware encryption identity certificate set, which is used to verify the integrity and legality of the data source for the receiver; the core data body encapsulates the encrypted emergency summary fragment, including the timestamp identifier and the content integrity check value; the routing control layer marks the target node identifier and the data life cycle parameter. The data packet is sent directly to the requesting medical node through the established encrypted transmission channel, serving as the direct input entity of step S4. The synchronously generated block chain record is written into the distributed ledger, which completely records the key audit elements of this cross-domain review.

[0068] Step S4 of the present application is to perform standardized encryption and integrity encapsulation based on the cross-domain emergency data packet. Specifically, the core task of this step is to secure the summary data transmitted to the receiving hospital gateway in step S3, ensuring its confidentiality and tamper resistance in emergency decision-making scenarios.

[0069] After receiving the cross-domain first-aid data packet output in step S3, the system first analyzes the three-layer encapsulation structure thereof: extracts the digital signature verification request party identity in the message header, disassembles the encrypted first-aid abstract fragment in the core data body, and reads the life cycle parameter marked in the routing control layer. On this basis, the built-in asymmetric encryption execution engine is called, and the encrypted data block in the data packet is input into the "Enc()" function for standardized processing. The function execution process strictly follows the preset encryption protocol logic: first, according to the target node identifier in the data packet, the corresponding public key certificate is matched from the local dynamic encryption certificate pool; then, the encryption algorithm is used to completely encapsulate the first-aid abstract, and the standard ciphertext data block that cannot be reversely analyzed is generated.

[0070] At the same time, the data integrity verification mechanism is started: the digital fingerprint of the original abstract content is calculated through the hash algorithm, and is implanted into the check bit of the ciphertext data block. Finally, the double-reinforced secure medical data transmission body is generated, which includes the non-detachable encrypted data core layer, the signature identification layer bound to the sender's identity, and the time stamp and life cycle control layer. After the transmission body is encapsulated through binary serialization, it is handed over to the data application execution link in step S5.

[0071] Step S5 of the present application is to realize first-aid decision support and system closed loop based on the secure medical data transmission body. Specifically, the core task of this step is to decrypt the standardized medical information and convert it into a clinically operable decision basis, and finally complete the technical goal of cross-domain first-aid cooperation.

[0072] When the secure medical data transmission body arrives at the first-aid system of the receiving hospital, the preset private key certificate of the gateway is called to perform reverse decryption operation. The original first-aid abstract is recovered by reversely executing the "Enc()" function logic, and the data hash value is verified synchronously to ensure the integrity. Then, the first-aid decision support engine is started, which intelligently analyzes the abstract key fields (such as the allergen "penicillin" and the operation history "coronary artery bypass") according to the clinical rules: automatically identifies the life-threatening items to generate red warning marks, pushes the contraindicated drug reminders to the first-aid monitoring equipment, and simultaneously associates the patient's physical sign data to establish an individualized treatment suggestion model.

[0073] After completing the first aid decision support, the system immediately performs a full-link closed-loop operation: first, the decrypted first aid summary is written into the local electronic medical record system and synchronized with the "cross-domain data source" mark, ensuring traceability of cross-institutional data; then, through the blockchain storage service, the data usage track and clinical decision basis are recorded completely, forming an unalterable distributed audit evidence chain; according to the preset life cycle parameters of the transmission body, the system automatically destroys the temporary encryption session key in the transmission process, completely eliminating the residual risk of sensitive data; finally, an encrypted response message containing data reception confirmation and clinical effectiveness evaluation results is fed back to the local hospital gateway, forming a cross-institutional collaborative closed loop. This operation system realizes the complete life cycle management of first aid data from cross-domain retrieval to clinical application through the four-dimensional linkage mechanism of data landing, storage audit, key destruction and feedback confirmation.

[0074] Finally, a cross-domain first aid collaboration closed-loop report is generated, which contains three parts: medical data items retrieved under the first aid scene and use effect, operation compliance audit log of participating institutions, and system-optimized routing strategy suggestion. Based on the report content, the system automatically feeds back the clinical use effect data to the first aid decision support engine to optimize the early warning rules, establishes a cross-institutional responsibility traceability mechanism through the blockchain storage audit log, and dynamically injects the routing strategy suggestion into the local address matching library and network topology table, continuously improving the accuracy and timeliness of subsequent cross-domain retrieval, thereby forming a self-driven medical collaboration closed loop of "clinical optimization-responsibility binding-system iteration", and finally building a continuously optimized smart medical collaboration ecosystem.

[0075] The present application solves the problem of cross-provincial data retrieval failure caused by the closed architecture of the existing regional platform by locking the patient's local key medical nodes and dynamically grabbing structured first aid summaries (such as allergy history, surgical records) relying on the streaming encryption engine, realizes the accurate calling of local medical records in the out-of-town first aid scene, and effectively eliminates the medical collaboration information blind area.

[0076] The basic principles, main features and advantages of the present application are shown and described above. Those skilled in the art should understand that the present application is not limited by the above examples, and the above examples and descriptions in the specification are only preferred examples of the present application and are not intended to limit the present application. Without departing from the spirit and scope of the present application, various changes and improvements can be made to the present application, and these changes and improvements all fall within the scope of the claimed present application. The scope of protection of the present application is defined by the appended claims and their equivalents.

Claims

1.A medical information sharing method based on smart medical care, characterized by, The method comprises the following steps: S1, deploying an intelligent gateway node in a medical institution, generating key configuration information including node identity, dynamic gateway registration index, local hospital address matching library, and encrypted public key certificate set through registration and configuration; S2, performing medical data retrieval operation based on the key configuration information, the steps are as follows: S2.1, establishing node communication link using dynamic gateway registration index; S2.2, generating digital identity certificate by binding node identity; S2.3, calling local hospital address matching library to analyze patient identity characteristics, and outputting target hospital code; S2.4, loading encrypted public key certificate set to build secure channel; S3, performing cross-domain medical data retrieval operation, the steps are as follows: S3.1, initiating structured emergency summary request based on target hospital code; S3.2, converting local original data into standardized emergency summary data, and encrypting using target public key; S3.3, generating cross-domain emergency data packet containing digital signature and encrypted summary, and retrieving real-time cross-provincial key medical information. 2.The smart care-based medical information sharing method of claim 1, wherein: In S1, when the node is registered through the central coordination service, the medical institution standardized code and physical location information are synchronously uploaded, and the dynamic gateway registration index is constructed by the central coordination service. 3.The smart care-based medical information sharing method of claim 1, wherein: The generation rule of the local hospital address matching library is that based on the first 6 administrative division codes of the patient's identity card and the last medical institution record, it is dynamically mapped to the local hospital standard code. 4.The smart care-based medical information sharing method of claim 1, wherein: The encrypted public key certificate set is generated by the following way: the intelligent gateway node exchanges the public key of the asymmetric key pair, and after binding with the node identity, it is stored in the local encrypted public key certificate library. 5.The smart care-based medical information sharing method of claim 1, wherein: In S2.2, the node identity is bound by the hardware security module to generate the digital identity certificate through the asymmetric key binding operation. 6.The smart care-based medical information sharing method of claim 1, wherein: In S2.4, when building the secure channel, the public key certificate is stored according to the target institution standard code, and a temporary session key is generated based on the certificate. 7.The smart care-based medical information sharing method of claim 1, wherein: In S3.2, the standardized emergency summary data conversion is realized by real-time mapping of local original data fields through a stream processor to generate a structured data set containing allergy history and operation record label. 8.The smart care-based medical information sharing method of claim 7, wherein: When the target public key is used for encryption in S3.2, the encryption function formula is as follows: E data = Enc(PK target , D FHIR ); In the formula, E data represents the encrypted data block output Enc() is the encryption function; PK target represents the target node public key extracted from the dynamic encryption certificate pool; D FHIR Indicates standardized emergency summary data. 9.The smart care-based medical information sharing method of claim 1, wherein: The steps of performing standardized encryption and integrity encapsulation on the cross-domain emergency data packet are as follows: Extracting the digital signature of the message header to verify the identity of the request party; Disassembling the encrypted emergency summary fragment of the core data body; Reading the life cycle parameters marked by the routing control layer; Generating a double-reinforced secure medical data transmission body. 10.The smart care-based medical information sharing method of claim 9, wherein: Based on the private key certificate preset in the secure medical data retrieval gateway, the reverse decryption operation is performed to generate a cross-domain emergency collaboration closed-loop report including medical data items, use effect, operation compliance audit log, and routing strategy suggestion.

Images