A method and system for secure storage of emergency medical records based on blockchain technology

Abstract

The present application provides a method and system for secure storage of first aid records based on blockchain technology. Among them, first aid record data generated in first aid events are received to obtain first aid record data containing timestamp and geographic location information; a hash algorithm is used for conversion to construct an unalterable data packet to obtain a data packet containing proof of authenticity and integrity of first aid information; the compliance and authority of the data packet are automatically reviewed by a smart contract to obtain a first aid record data packet that is allowed to join the blockchain network; a distributed consensus algorithm is used to synchronize between multiple nodes, and an off-chain computing mechanism is introduced to obtain first aid records that are securely and transparently stored under decentralized management; an access control interface is provided to enable relevant parties to query and verify first aid records in accordance with strict privacy protection rules, but unauthorized modification or deletion operations are not allowed. The technical solution provided by the present application improves the security, transparency and traceability of first aid records.

Description

Technical Field

[0001] This application relates to the fields of blockchain and zero-knowledge proof technology, and in particular to a method and system for secure storage of emergency medical records based on blockchain technology. Background Technology

[0002] In the field of emergency medical care, the rapid and accurate recording and transmission of emergency event data is crucial. Emergency records not only need to contain detailed patient information but also precise timestamps and geographic location information to ensure the timeliness and effectiveness of rescue operations. Furthermore, to guarantee the authenticity and integrity of the data and prevent tampering or forgery, advanced encryption technologies and distributed storage mechanisms must be introduced.

[0003] Currently, the management and storage of emergency medical records primarily rely on traditional centralized database systems. These systems typically handle emergency medical records by storing all records on a central server for easy management and retrieval. Human review of the records' compliance and access permissions ensures data validity. Basic encryption algorithms are used to protect data security, but sophisticated verification mechanisms are lacking.

[0004] However, while existing emergency medical record management systems meet basic needs to some extent, significant shortcomings remain: centralized databases are vulnerable to attack, and intrusion could lead to the leakage or alteration of large amounts of sensitive data. Manual review processes are time-consuming and error-prone, unable to process large volumes of emergency medical records in real time, impacting emergency response speed. Because data is managed by a single institution, other stakeholders find it difficult to verify the authenticity and integrity of the data, reducing system transparency and trust among parties. Traditional systems lack strict access control mechanisms, failing to effectively protect patient privacy and easily leading to unauthorized access and data misuse. Summary of the Invention

[0005] This application provides a method and system for secure storage of emergency medical records based on blockchain technology, which addresses the problems of low security, transparency, and traceability of emergency medical records in the prior art.

[0006] In a first aspect, embodiments of this application provide a method for secure storage of emergency medical records based on blockchain technology, including:

[0007] Receive emergency record data generated during emergency events, and add timestamps and geographic location information to each emergency record data to obtain emergency record data containing timestamps and geographic location information;

[0008] The emergency medical record data containing timestamps and geographic location information is transformed using a hash algorithm. Combined with the identity verification information of emergency medical personnel and the identifier of emergency medical equipment, an immutable data packet is constructed based on a zero-knowledge proof algorithm to obtain a data packet containing proof of the authenticity and integrity of emergency medical information.

[0009] Based on the data packet containing proof of the authenticity and integrity of the emergency information, the compliance and permissions of the data packet are automatically reviewed by a smart contract to obtain an emergency record data packet that is allowed to be added to the blockchain network;

[0010] By using a distributed consensus algorithm, the emergency medical records data packets that are allowed to be added to the blockchain network are synchronized among multiple nodes, and an off-chain computing mechanism is introduced to process a large number of transactions, resulting in emergency medical records that are securely and transparently stored in the absence of centralized management.

[0011] Based on the secure and transparently stored emergency medical records, an access control interface is provided, allowing relevant parties to query and verify the emergency medical records in accordance with strict privacy protection rules, but prohibiting unauthorized modification or deletion.

[0012] Optionally, the emergency medical record data containing timestamps and geographic location information is transformed using a hash algorithm, and combined with the identity verification information of the emergency medical personnel and the identifier of the emergency medical equipment, an immutable data packet is constructed based on a zero-knowledge proof algorithm to obtain a data packet containing proof of the authenticity and integrity of the emergency medical information, including:

[0013] Using a secure hash algorithm, emergency medical record data containing timestamps and geographic location information is processed to obtain a unique hash value. This unique hash value serves as a digital fingerprint of the emergency medical record data, ensuring the integrity and uniqueness of the data.

[0014] Based on the unique hash value, combined with the identity verification information of the emergency responders and the unique identifier of the emergency equipment, a composite data structure is constructed. The composite data structure contains the contents of the emergency record, associates the specific executor of the emergency operation with the equipment used, and increases the traceability of the data and the attribution of responsibility.

[0015] Based on the aforementioned composite data structure, a proof is created using a zero-knowledge proof algorithm. This proof allows evidence to be provided to a third party without revealing any actual contents of the emergency medical record, demonstrating the authenticity, completeness, and legality of the emergency medical record's source, thus obtaining a zero-knowledge proof.

[0016] Based on the zero-knowledge proof, the original emergency record hash, the emergency personnel's identity verification information, and the emergency equipment identifier are packaged together to form an immutable data packet. This data packet can be verified by nodes in the blockchain network to ensure that the emergency record has not been tampered with from generation to storage, and to verify the authenticity and reliability of the source of the emergency record, ultimately resulting in a data packet containing proof of the authenticity and integrity of the emergency information.

[0017] Optionally, the process of using a secure hash algorithm to process the emergency medical record data containing timestamps and geographic location information to obtain a unique hash value, which serves as a digital fingerprint of the emergency medical record data to ensure data integrity and uniqueness, includes:

[0018] Based on the emergency medical record data containing timestamps and geographic location information, a recognized secure hash algorithm is selected, which is collision resistant.

[0019] The aforementioned secure hash algorithm is used to process emergency medical record data containing timestamps and geographic location information to obtain a unique hash value. This unique hash value serves as the digital fingerprint of the emergency medical record data. Any slight change to the original data will result in a completely different hash value, ensuring the integrity and uniqueness of the data.

[0020] Based on the unique hash value, before adding the unique hash value to the blockchain, check whether there is an existing hash value with the same unique hash value in the current blockchain network to verify the uniqueness of the hash value and obtain the verified hash value;

[0021] Based on the verified hash value, the verified hash value is associated with the corresponding emergency medical record data to ensure that each emergency medical record has a unique digital fingerprint, which helps to build an immutable data packet and quickly locate and verify the emergency medical record when needed.

[0022] Optionally, based on the composite data structure, a proof is created using a zero-knowledge proof algorithm. This proof allows evidence to be provided to a third party without revealing any actual first aid record content, demonstrating the authenticity, completeness, and legality of the first aid record's source. This zero-knowledge proof includes:

[0023] Based on the constructed composite data structure, the underlying data for generating zero-knowledge proofs is prepared using the composite data structure.

[0024] By using a zero-knowledge proof algorithm to process the basic data, a zero-knowledge proof is created and obtained without disclosing any actual emergency medical record content. This zero-knowledge proof can provide evidence to a third party without disclosing the specific content of the emergency medical record, proving the authenticity, completeness, and legality of the source of the emergency medical record.

[0025] Based on the zero-knowledge proof, combined with the hash value, the identity verification information of the emergency responders, and the identifier of the emergency equipment in the composite data structure, the necessary verification information is provided for the subsequent construction of an immutable data packet, ensuring that the emergency record is not tampered with from generation to storage, and verifying the authenticity and reliability of the source of the emergency record.

[0026] Optionally, the use of a distributed consensus algorithm to synchronize the emergency medical record data packets allowed to be added to the blockchain network across multiple nodes, and the introduction of an off-chain computing mechanism to process a large number of transactions, results in emergency medical records that are securely and transparently stored in a decentralized management environment, including:

[0027] Using a distributed consensus algorithm, emergency medical record data packets that have passed smart contract review and are allowed to be added to the blockchain network are synchronized among nodes to obtain emergency medical record data packets that have reached a consensus and are verified to be valid by most nodes.

[0028] Based on the agreed and verified first aid record data package, the agreed and verified first aid record data package is added to the blockchain under decentralized management to generate valid first aid record data that is confirmed without a single controlling entity.

[0029] Based on the effective emergency medical record data, an off-chain computing mechanism is introduced to process a large amount of emergency medical record data or non-critical transactions that do not need to be reflected on the chain in real time, so as to meet the need for efficient processing and obtain preliminary results after off-chain computing.

[0030] Using a distributed consensus algorithm, the preliminary results after off-chain computation are verified again to ensure that the preliminary results after off-chain computation meet the standards for joining the main chain, and finally generate emergency rescue record data that is officially added to the blockchain.

[0031] Based on the emergency medical records data that are finally officially added to the blockchain, emergency medical records are obtained by combining further distributed consensus algorithms and off-chain computing mechanisms, and are securely and transparently stored in a decentralized management environment.

[0032] Optionally, the first aid records, stored securely and transparently, provide an access control interface, enabling relevant parties to query and verify the first aid records while adhering to strict privacy protection rules, but disallowing unauthorized modification or deletion operations, including:

[0033] Based on the first aid records that are securely and transparently stored in a decentralized management environment, an access control system is constructed. The access control system is configured to identify and verify the identity of the parties requesting to query or verify the first aid records, thereby obtaining an access control system that ensures that only authorized users operate in accordance with strict privacy protection rules.

[0034] By utilizing encryption technology and a permission management system, the access control system is enhanced to ensure that each query or verification request undergoes strict identity verification and permission checks, generating a protected access control interface that only allows requests that conform to preset permission rules to pass through.

[0035] Based on the protected access control interface, different access levels and permission ranges are customized for different roles and needs of relevant parties to obtain customized access permission settings, ensuring that different roles have appropriate access permissions;

[0036] By leveraging the immutability of blockchain, all query and verification activities based on the customized access permission settings are recorded and processed to generate unchangeable and transparent access logs, ensuring system transparency and post-audit capabilities.

[0037] Access control policies are automatically executed through smart contracts. Access requests recorded in the immutable and transparent access log are processed automatically according to pre-set rules, generating an access control execution mechanism guaranteed by smart contracts to ensure that unauthorized modification or deletion operations are not allowed.

[0038] It provides a logging function to record in detail every successful or attempted access behavior in the access control execution mechanism based on the smart contract, including information such as the visitor's identity, access time, and access content, and generates secure and tamper-proof log records stored on the blockchain.

[0039] Optionally, the step of automatically verifying the compliance and permissions of the data packet containing proof of the authenticity and integrity of the emergency information through a smart contract to obtain an emergency record data packet that is allowed to be added to the blockchain network includes:

[0040] Based on the data packet containing the proof of authenticity and integrity of the emergency information, the data packet containing the proof of authenticity and integrity of the emergency information is received and processed to ensure that each data packet contains the timestamp and geographical location information of the emergency event, as well as the identity verification information of the emergency personnel and the identifier of the emergency equipment, and to generate an emergency record data packet ready for review.

[0041] Using smart contracts to define review standards, based on the emergency medical record data package to be reviewed, rules and conditions in the smart contract are pre-set, including data format, validity of timestamps, rationality of geographical location information, accuracy of emergency personnel's identity verification information and emergency equipment identifiers, to generate a smart contract rule set;

[0042] Based on the smart contract rule set, the emergency medical record data packet to be reviewed is automatically processed for compliance review, verifying whether the data packet meets all preset conditions, and obtaining the data packet that has passed the preliminary compliance check;

[0043] Based on the data packet that has passed the initial compliance check, an authorization verification process is performed. The smart contract is used to confirm the identity and operation permissions of the emergency responder or submitter, and a data packet with sufficient permissions is generated.

[0044] Based on the data packet with sufficient permissions, the smart contract is used for final review. If the data packet with sufficient permissions passes all compliance and permission checks, a positive review result is generated. For data packets that fail the review, a negative review result is generated, and a notification mechanism is triggered to inform the relevant parties of the reason.

[0045] Based on the positive review results, the data packets that pass the smart contract review are marked to obtain emergency medical record data packets that are allowed to be added to the blockchain network.

[0046] Secondly, embodiments of this application provide a secure storage system for emergency medical records based on blockchain technology, comprising:

[0047] The receiving module is used to receive emergency record data generated in emergency events, and to add timestamps and geographic location information to each emergency record data to obtain emergency record data containing timestamps and geographic location information;

[0048] The transformation construction module is used to transform the emergency record data containing timestamps and geographical location information using a hash function, and combine it with the identity verification information of emergency personnel and the identifier of emergency equipment to construct an immutable data packet based on a zero-knowledge proof algorithm, thereby obtaining a data packet containing proof of the authenticity and integrity of emergency information.

[0049] The review module is used to automatically review the compliance and permissions of the data packet containing proof of the authenticity and integrity of the emergency information through a smart contract, and obtain the emergency record data packet that is allowed to be added to the blockchain network.

[0050] The processing module is used to synchronize the emergency medical record data packets that are allowed to be added to the blockchain network across multiple nodes using a distributed consensus algorithm, and to introduce an off-chain computing mechanism to process a large number of transactions, so as to obtain emergency medical records that are securely and transparently stored in the absence of centralized management.

[0051] A module is provided for providing an access control interface based on the securely and transparently stored emergency medical records, enabling relevant parties to query and verify the emergency medical records in accordance with strict privacy protection rules, but disallowing unauthorized modification or deletion.

[0052] Thirdly, embodiments of this application provide a computing device, including a processing component and a storage component; the storage component stores one or more computer instructions; the one or more computer instructions are to be invoked and executed by the processing component to implement a secure storage method for emergency medical records based on blockchain technology as described in any of the first aspects.

[0053] Fourthly, embodiments of this application provide a computer storage medium storing a computer program, which, when executed by a computer, implements a secure storage method for emergency medical records based on blockchain technology as described in any of the first aspects.

[0054] In this embodiment, emergency medical record data generated during an emergency medical event is received, and a timestamp and geographic location information are appended to each record to obtain emergency medical record data containing timestamps and geographic location information. The data containing timestamps and geographic location information is then converted using a hash algorithm, and combined with the identity verification information of the emergency personnel and the identifier of the emergency equipment, an immutable data packet is constructed based on a zero-knowledge proof algorithm to obtain a data packet containing proof of the authenticity and integrity of the emergency medical information. Based on the data packet containing proof of the authenticity and integrity of the emergency medical information, the compliance and permissions of the data packet are automatically reviewed through a smart contract to obtain an emergency medical record data packet allowed to join the blockchain network. Using a distributed consensus algorithm, the emergency medical record data packet allowed to join the blockchain network is synchronized across multiple nodes, and an off-chain computing mechanism is introduced to process a large number of transactions, resulting in emergency medical records that are securely and transparently stored without centralized management. Based on the securely and transparently stored emergency medical records, an access control interface is provided, allowing relevant parties to query and verify emergency medical records while adhering to strict privacy protection rules, but unauthorized modification or deletion is not permitted.

[0055] The technical solution of this application has the following beneficial effects:

[0056] The data packets constructed using hash algorithms and zero-knowledge proofs ensure the authenticity and integrity of emergency medical information, preventing data tampering. Distributed consensus algorithms enable secure storage of emergency medical records in a decentralized environment, increasing system transparency and trust among parties. Smart contracts automatically verify the compliance and permissions of data packets, reducing manual intervention and improving verification efficiency and accuracy. The provided access control interface allows relevant parties to query and verify emergency medical records while strictly adhering to privacy protection rules, ensuring data security and privacy. The introduction of off-chain computation mechanisms effectively handles large volumes of transactions, improving system efficiency and response speed, and adapting to the high concurrency demands of emergency medical scenarios.

[0057] Furthermore, a secure hash algorithm is used to process the emergency medical record data, which includes timestamps and geographic location information, generating a unique hash value as a digital fingerprint to ensure data integrity and uniqueness. Based on the generated hash value, combined with the emergency responder's authentication information and the unique identifier of the emergency equipment, a composite data structure is constructed. This structure not only contains the content of the emergency medical record but also associates it with the specific executor of the emergency operation and the equipment used, increasing data traceability and accountability. A zero-knowledge proof algorithm is used to create a proof based on the composite data structure. This proof allows evidence to be provided to third parties, demonstrating the authenticity, integrity, and legality of the emergency medical record's origin, without revealing any actual content. The zero-knowledge proof, the original emergency medical record hash value, the emergency responder's authentication information, and the emergency equipment identifier are packaged together to form an immutable data packet. This data packet can be verified by nodes in the blockchain network, ensuring that the emergency medical record has not been tampered with from generation to storage and verifying its authenticity and reliability, ultimately resulting in a data packet containing proof of the authenticity and integrity of the emergency medical information. A distributed consensus algorithm is used to synchronize the emergency medical record data packets that have passed smart contract review and are allowed to be added to the blockchain network, ensuring that a majority of nodes reach consensus and verify the validity of the emergency medical record data packets. The process involves decentralizing the addition of agreed-upon and verified emergency medical record data packets to the blockchain, generating valid emergency medical record data that is confirmed without a single controlling entity. An off-chain computation mechanism is introduced to process large amounts of emergency medical record data or non-critical transactions that do not require immediate on-chain processing, meeting the need for efficient processing and yielding preliminary results after off-chain computation. These preliminary results are then re-verified to ensure they meet the standards for inclusion on the main chain, generating the final, officially added emergency medical record data to the blockchain. By combining further distributed consensus algorithms with off-chain computation mechanisms, the secure and transparent storage of emergency medical records in a decentralized management environment is achieved.

[0058] Data packets constructed using hash algorithms and zero-knowledge proofs ensure the authenticity and integrity of emergency medical information, preventing data tampering. Distributed consensus algorithms enable secure storage of emergency medical records in a decentralized environment, increasing system transparency and trust among parties. Smart contracts automatically review the compliance and permissions of data packets, reducing manual intervention and improving review efficiency and accuracy. The provided access control interface allows relevant parties to query and verify emergency medical records while strictly adhering to privacy protection rules, ensuring data security and privacy. The introduction of off-chain computing mechanisms effectively handles large volumes of transactions, improving system efficiency and response speed, and adapting to the high concurrency demands of emergency medical scenarios. By combining the identity verification information of emergency personnel and the identifiers of emergency medical equipment, data traceability and accountability are enhanced, facilitating subsequent responsibility determination and auditing.

[0059] These or other aspects of this application will become more apparent in the following description of the embodiments. Attached Figure Description

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

[0061] Figure 1 A flowchart illustrating a method for secure storage of emergency medical records based on blockchain technology, provided in this application embodiment;

[0062] Figure 2 A schematic diagram of the structure of a blockchain-based secure storage system for emergency medical records provided in this application embodiment;

[0063] Figure 3 This is a schematic diagram of the structure of a computing device provided in an embodiment of this application. Detailed Implementation

[0064] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.

[0065] In some of the processes described in the specification, claims, and accompanying drawings of this application, multiple operations appearing in a specific order are included. However, it should be clearly understood that these operations may not be executed in the order they appear herein, or may be executed in parallel. The operation numbers, such as 101, 102, etc., are merely used to distinguish different operations and do not themselves represent any execution order. Furthermore, these processes may include more or fewer operations, and these operations may be executed sequentially or in parallel. It should be noted that the descriptions such as "first," "second," etc., in this document are used to distinguish different messages, devices, modules, etc., and do not represent a chronological order, nor do they limit "first" and "second" to different types.

[0066] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0067] Figure 1 A flowchart illustrating a method for securely storing emergency medical records based on blockchain technology is provided in this application embodiment. Figure 1 As shown, the method includes:

[0068] 101. Receive emergency record data generated during emergency events, and add a timestamp and geographic location information to each emergency record data to obtain emergency record data containing timestamp and geographic location information;

[0069] In this step, emergency medical records are crucial documents in emergency medical scenarios, including basic patient information, a description of the patient's condition, and treatment measures. To ensure the time and location accuracy of these records, the system automatically attaches a precise timestamp and geographic location information to each emergency record data received. The timestamp records the specific time the emergency event occurred, while the geographic location information identifies the location where the emergency event took place. The combination of these two provides a solid foundation for subsequent data verification and accountability.

[0070] Emergency responders use mobile devices equipped with GPS modules and time synchronization capabilities to record emergency events. When an emergency responder submits a record, the system automatically retrieves the current timestamp and geolocation information from the device and saves them along with the record. This ensures that each emergency record contains not only detailed medical information but also accurate time and location information, guaranteeing data integrity and traceability.

[0071] In one specific embodiment, paramedics in the ambulance record the patient's initial diagnosis and treatment measures using a dedicated application. The application automatically obtains the current location from the ambulance's integrated GPS module and the current time from the device's system clock, then uploads this information along with the emergency record to a central server. For example, an emergency incident might occur at 13:05 on December 17, 2024, at 1000 Lujiazui Ring Road, Pudong New Area, Shanghai. This information is precisely appended to the emergency record, providing a reliable time and geographical reference for subsequent data processing.

[0072] 102. The emergency record data containing timestamps and geographical location information is converted using a hash algorithm, and combined with the identity verification information of the emergency personnel and the identifier of the emergency equipment, an immutable data packet is constructed based on a zero-knowledge proof algorithm to obtain a data packet containing proof of the authenticity and integrity of the emergency information.

[0073] In this step, a hash algorithm is a one-way encryption technique that maps data of arbitrary length to a fixed-length output, commonly used to generate digital fingerprints of data. Emergency medical records processed using a hash algorithm ensure that their content has not been tampered with during transmission and storage. Furthermore, combining the emergency responder's authentication information and the unique identifier of the emergency equipment further enhances the authenticity and legitimacy of the data's origin. Zero-knowledge proof algorithms allow for the verification of data authenticity without revealing specific content, thus protecting privacy while ensuring data credibility.

[0074] The system first uses a secure hash algorithm to hash the emergency medical record data, which includes timestamps and geolocation information, generating a unique hash value as a digital fingerprint. Then, the system constructs a composite data structure that combines the generated hash value, the emergency responder's authentication information, and the unique identifier of the emergency medical equipment. Next, based on this composite data structure, a zero-knowledge proof algorithm is used to create a proof that can provide evidence to a third party, without revealing any actual contents of the emergency medical record, proving the authenticity, completeness, and legitimacy of the record's origin.

[0075] Continuing from the previous embodiment, after the emergency medical record is uploaded, the system uses the SHA-256 algorithm to calculate the hash value of the record. Then, the system combines this hash value with the emergency responder's digital signature and the emergency medical device's serial number to form a composite data structure. Next, the system uses a zero-knowledge proof algorithm to generate a proof for this composite data structure. For example, emergency responder Zhang San signed the emergency medical record using his private key, combined with the emergency medical device's serial number "GJ123456". The system generates a zero-knowledge proof for this record, ensuring that any querying party can verify the authenticity of this emergency medical record without needing to view its contents.

[0076] Optionally, step 102, which involves using a hash algorithm to transform the emergency medical record data containing timestamps and geographic location information, and combining it with the emergency responder's authentication information and the emergency equipment's identifier, constructs an immutable data packet based on a zero-knowledge proof algorithm to obtain a data packet containing proof of the authenticity and integrity of the emergency medical information. This includes: processing the emergency medical record data containing timestamps and geographic location information using a secure hash algorithm to obtain a unique hash value, which serves as a digital fingerprint of the emergency medical record data to ensure data integrity and uniqueness; and constructing a composite data structure based on the unique hash value, combined with the emergency responder's authentication information and the emergency equipment's unique identifier. This composite data structure contains the content of the emergency medical record and is associated with the emergency medical information. The specific executors and equipment used in the operation are identified to increase data traceability and accountability. Based on the composite data structure, a zero-knowledge proof algorithm is used to create a proof that allows evidence to be provided to a third party without revealing any actual emergency medical record content, proving the authenticity, integrity, and legality of the emergency medical record's source. This results in a zero-knowledge proof. Based on this zero-knowledge proof, along with the original emergency medical record hash value, the emergency medical personnel's identity verification information, and the emergency medical equipment's identifier, an immutable data packet is formed. This data packet can be verified by nodes in the blockchain network to ensure that the emergency medical record has not been tampered with from generation to storage, and to verify the authenticity and reliability of the emergency medical record's source. Finally, a data packet containing proof of the authenticity and integrity of the emergency medical information is obtained.

[0077] Optionally, step 102, which involves processing the emergency medical record data containing timestamps and geographic location information using a secure hash algorithm to obtain a unique hash value, serves as the digital fingerprint of the emergency medical record data to ensure data integrity and uniqueness, includes: selecting a recognized secure hash algorithm based on the emergency medical record data containing timestamps and geographic location information, wherein the secure hash algorithm is collision resistant; processing the emergency medical record data containing timestamps and geographic location information using the secure hash algorithm to obtain a unique hash value, wherein the unique hash value serves as the digital fingerprint of the emergency medical record data, and any slight change to the original data will result in a completely different hash value, ensuring data integrity and uniqueness; checking whether there is an existing hash value identical to the unique hash value in the current blockchain network before adding the unique hash value to the blockchain to verify the uniqueness of the hash value, thereby obtaining a verified hash value; and associating the verified hash value with the corresponding emergency medical record data to ensure that each emergency medical record has a unique digital fingerprint, which helps to subsequently build an immutable data packet and quickly locate and verify a specific emergency medical record when needed.

[0078] In emergency medical record management, ensuring data integrity and uniqueness is paramount. Generating unique hash values ​​as digital fingerprints using secure hash algorithms effectively prevents data tampering. Furthermore, combining this with the identity verification information of emergency personnel and the identifiers of emergency equipment enhances data traceability and accountability. Zero-knowledge proof algorithms allow for the verification of data authenticity, integrity, and legitimate origin without revealing specific details.

[0079] In this step, a secure hash algorithm is a one-way encryption technique that maps data of arbitrary length to a fixed-length output. It is collision-resistant, meaning it is virtually impossible to find two different inputs that produce the same output. Common secure hash algorithms include SHA-256 and SHA-3. Collision resistance refers to the characteristic that a hash algorithm is unlikely to find two different inputs that produce the same hash value, ensuring the uniqueness and integrity of the data. Any slight change to the original data will result in a completely different hash value. A composite data structure combines the contents of emergency medical records with the identity information of emergency personnel and the identifiers of emergency medical equipment, forming a data structure containing more information. This not only increases the traceability of the data but also facilitates subsequent accountability and auditing. Zero-knowledge proof is a cryptographic protocol that allows one party to prove the truth of a statement to another without revealing any additional information. In emergency medical record management, it can be used to verify the authenticity of data without disclosing specific content.

[0080] First, based on the characteristics and security requirements of emergency medical record data, a recognized secure hash algorithm, such as SHA-256 or SHA-3, should be selected. These algorithms have good collision resistance and can ensure the uniqueness and integrity of the generated hash values.

[0081] Then, using a selected secure hashing algorithm, the emergency medical records data, which include timestamps and geographic location information, are processed to generate a unique hash value. This hash value serves as a digital fingerprint of the emergency medical records data; any slight alteration to the original data will result in a completely different hash value, ensuring the integrity and uniqueness of the data.

[0082] Next, before adding the generated hash value to the blockchain, the system checks if a duplicate hash value already exists in the current blockchain network. If a duplicate exists, it indicates that the emergency rescue record may have been recorded before or there is a conflict, requiring further investigation. Otherwise, the uniqueness of the hash value is confirmed.

[0083] Next, based on the verified hash value, it is associated with the corresponding emergency medical record data, ensuring that each emergency medical record has a unique digital fingerprint. This helps in the subsequent construction of immutable data packets and the rapid location and verification of specific emergency medical records when needed.

[0084] Furthermore, the verified hash value, the first responder's authentication information, and the unique identifier of the first responder's equipment are combined into a composite data structure. This structure not only contains the contents of the first responder's record but also links the specific executor of the first responder's operation and the equipment used, enhancing data traceability and accountability.

[0085] Furthermore, based on the composite data structure, a zero-knowledge proof algorithm is used to create a proof. This proof can provide evidence to a third party, demonstrating the authenticity, completeness, and legitimacy of the emergency medical records, without revealing any of the actual contents of the records.

[0086] Finally, the zero-knowledge proof, the original emergency medical record hash, the emergency responder's identity verification information, and the emergency medical equipment identifier are packaged together to form an immutable data packet. This data packet can be verified by nodes in the blockchain network to ensure that the emergency medical record has not been tampered with from its generation to storage, and to verify the authenticity and reliability of its source.

[0087] In this embodiment, it is assumed that, in a specific instance, paramedics in an ambulance use a dedicated application to record the patient's initial diagnosis and treatment. The application automatically obtains the current location from the GPS module integrated into the ambulance and the current time from the device's system clock, then uploads this information along with the emergency records to a central server. For example, an emergency incident occurred at 13:05 on December 17, 2024, at 1000 Lujiazui Ring Road, Pudong New Area, Shanghai.

[0088] First, the system chooses SHA-256 as the secure hash algorithm because it has strong collision resistance and a wide range of applications.

[0089] Secondly, the system uses the SHA-256 algorithm to calculate the hash value of the emergency record. Assuming the text content of the emergency record is "Patient Zhang San, abnormal heart rate, oxygen administered," its hash value is a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0u1v2w3x4y5z6.

[0090] Then, the system queries the current blockchain network to confirm that no other emergency rescue record has the same hash value a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0u1v2w3x4y5z6, ensuring the uniqueness of the hash value.

[0091] Next, the system associates the verified hash value with the emergency medical records, ensuring that each emergency medical record has a unique digital fingerprint.

[0092] Furthermore, the system combines the hash value a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0u1v2w3x4y5z6, the digital signature of the emergency responder Zhang San, and the serial number "GJ123456" of the emergency equipment into a composite data structure.

[0093] Furthermore, the system uses a zero-knowledge proof algorithm to generate a proof for this composite data structure, ensuring that any querying party can verify the authenticity of this emergency record without having to examine the specific content.

[0094] Ultimately, the system packages the zero-knowledge proof, hash value, first responder authentication information, and first responder equipment identifier together into an immutable data packet. This data packet is sent to various nodes in the blockchain network for verification, ensuring that the first responder record has not been tampered with from its generation to storage, and verifying the authenticity and reliability of its source.

[0095] Through the above steps, this invention not only ensures the authenticity and integrity of emergency medical records, but also provides an efficient verification mechanism and strict privacy protection, making it suitable for the high reliability and high security requirements of the emergency medical field.

[0096] Optionally, step 102, which involves creating a proof using a zero-knowledge proof algorithm based on the composite data structure, wherein the proof allows evidence to be provided to a third party without disclosing any actual emergency medical record content, proving the authenticity, integrity, and legality of the emergency medical record's source, and thus obtaining a zero-knowledge proof, includes: preparing basic data for generating the zero-knowledge proof based on the constructed composite data structure; processing the basic data using a zero-knowledge proof algorithm to ensure that a zero-knowledge proof is created and obtained without disclosing any actual emergency medical record content, wherein the zero-knowledge proof can provide evidence to a third party without disclosing the specific content of the emergency medical record, proving the authenticity, integrity, and legality of the emergency medical record's source; and, based on the zero-knowledge proof, combining the hash value in the composite data structure, the emergency medical personnel's authentication information, and the emergency medical equipment's identifier, providing necessary verification information for subsequently constructing an immutable data packet, ensuring that the emergency medical record is not tampered with during its generation and storage, and verifying the authenticity and reliability of the emergency medical record's source.

[0097] In this step, zero-knowledge proof is a cryptographic protocol that allows one party to prove the truth of a statement to another without revealing any additional information. In emergency medical record management, zero-knowledge proof can be used to verify the authenticity, integrity, and legitimacy of data without disclosing the specific contents of the emergency medical record, thus protecting patient privacy. The composite data structure contains the content of the emergency medical record, timestamps, geographic location information, emergency personnel authentication information, and unique identifiers for emergency medical equipment. This information collectively constitutes a data structure containing more information, increasing data traceability and facilitating subsequent accountability and auditing. Basic data refers to the initial input data used to generate the zero-knowledge proof. It includes key information extracted from the composite data structure, such as hash values, authentication information, and device identifiers. This basic data serves as input to the zero-knowledge proof algorithm, ensuring that the generated proof can effectively verify the authenticity, integrity, and legitimacy of the emergency medical record's origin. Verification information refers to the necessary verification information provided by combining the zero-knowledge proof and key elements in the composite data structure to subsequently construct an immutable data packet. This verification information ensures that the emergency medical record has not been tampered with from generation to storage and verifies the authenticity and reliability of its origin.

[0098] First, based on the constructed composite data structure, the system extracts and prepares the foundational data for generating zero-knowledge proofs. This includes, but is not limited to, the hash value of emergency medical records, the authentication information of emergency medical personnel, and the unique identifier of emergency medical equipment. This foundational data is the key input for generating zero-knowledge proofs.

[0099] Secondly, zero-knowledge proof algorithms are used to process the underlying data, ensuring that a zero-knowledge proof is created and obtained without disclosing any actual emergency medical record content. This proof can provide evidence to third parties, demonstrating the authenticity, completeness, and legality of the emergency medical record's source, without revealing its specific content. For example, the prover can use zero-knowledge proofs to demonstrate the validity of an emergency medical record to hospital administrators without disclosing specific patient medical information.

[0100] Finally, based on the generated zero-knowledge proof, combined with the hash value in the composite data structure, the first responder's authentication information, and the identifier of the first responder's equipment, necessary verification information is provided for subsequently constructing an immutable data packet. This verification information ensures that the first responder record has not been tampered with from generation to storage and verifies the authenticity and reliability of the first responder record's source. For example, a verifier can confirm the integrity of the first responder record by checking the zero-knowledge proof and the associated hash value.

[0101] In this embodiment, it is assumed that, in a specific instance, paramedics in an ambulance record the patient's initial diagnosis and treatment measures using a dedicated application. The application automatically obtains the current location from the GPS module integrated into the ambulance and the current time from the device's system clock, then uploads this information along with the emergency records to a central server. For example, an emergency incident occurred at 13:05 on December 17, 2024, at 1000 Lujiazui Ring Road, Pudong New Area, Shanghai.

[0102] The system first constructs a composite data structure, which includes the contents of the emergency record, the timestamp "2024-12-17, 13:05", the geographical location information "No. 1000, Lujiazui Ring Road, Pudong New Area, Shanghai", the digital signature of the emergency responder Zhang San, and the serial number of the emergency equipment "GJ123456".

[0103] Next, the system extracts basic data from the composite data structure, including the hash value of the emergency record a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0u1v2w3x4y5z6, the digital signature of the emergency responder Zhang San, and the serial number of the emergency equipment "GJ123456".

[0104] Furthermore, the system uses a zero-knowledge proof algorithm to process the underlying data and create a zero-knowledge proof. This proof can provide evidence to third parties, without revealing any actual contents of the emergency medical records, to demonstrate the authenticity, completeness, and legality of the records' origin.

[0105] For example, if an emergency medical record contains sensitive medical information, zero-knowledge proofs can prove the record's validity without revealing specific medical details. This protects patient privacy while ensuring the credibility of the emergency medical record.

[0106] Furthermore, based on the generated zero-knowledge proof, combined with the hash value a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0u1v2w3x4y5z6 in the composite data structure, the digital signature of emergency responder Zhang San, and the serial number "GJ123456" of the emergency equipment, the system provides the necessary verification information for subsequently constructing an immutable data packet.

[0107] These verification messages ensure that emergency medical records are not tampered with from generation to storage, and verify the authenticity and reliability of their source. For example, when hospital administrators need to query a specific emergency medical record, they can quickly confirm the record's validity and authenticity by verifying the zero-knowledge proof and associated hash value, without needing to view the specific medical information.

[0108] Through the steps described above, this invention not only ensures the authenticity and integrity of emergency medical records but also provides an efficient verification mechanism and strict privacy protection, making it suitable for the high reliability and security requirements of the emergency medical field. Furthermore, the application of zero-knowledge proofs enables reliable verification of emergency medical records while maintaining privacy, enhancing trust and transparency among all parties.

[0109] This application recognizes that ensuring the authenticity and integrity of emergency medical records is crucial in the field of emergency medicine. Traditional centralized data management systems are vulnerable to tampering and privacy breaches, especially when sensitive medical information is involved. To overcome these challenges, the research team proposes a zero-knowledge proof-based solution that combines weighted hash values, composite data structures, and random salt values ​​to ensure data security and privacy protection for emergency medical records. This solution not only verifies the authenticity, integrity, and legitimacy of emergency medical records but also provides evidence without revealing any actual content, enhancing the system's transparency and trustworthiness. Therefore, a new alternative solution is proposed, which includes:

[0110] Optionally, step 102, which involves creating a proof using a zero-knowledge proof algorithm based on the composite data structure, allows providing evidence to a third party without revealing any actual first aid record content, proving the authenticity, completeness, and legality of the first aid record's source, thus obtaining a zero-knowledge proof, including:

[0111] Generate a weighted hash value using the following formula. :

[0112] ;

[0113] in, It is timestamp data, representing the time information of the emergency rescue record; Geographic location information indicates the location where the emergency occurred; , These are the weighting factors for timestamp data and geolocation information, respectively. , It is an exponential factor; It is a secure hash algorithm, such as SHA-256, used to generate fixed-length hash values. It is a one-way encryption technique that ensures that any change to the input data will result in a completely different output.

[0114] Construct a weighted composite data structure using the following formula. :

[0115] ;

[0116] in, It is a weighted composite data structure; Identity verification information of emergency responders; It is a unique identifier for emergency medical equipment; , These are the weighting factors for first aid personnel identification information and first aid equipment identifiers, respectively.

[0117] Prepare the basic data using the following formula. Used to generate zero-knowledge proofs:

[0118] ;

[0119] in, It is used to prepare the basic data for generating zero-knowledge proofs; It is a preparation function that converts the complex data structure into a basic data format suitable for processing by zero-knowledge proof algorithms; It is a random salt value, used to further obfuscate the underlying data, ensuring that different outputs will be produced even if the inputs are the same, thus preventing pre-compute attacks;

[0120] Weighted zero-knowledge proofs can be created using the following formula. :

[0121] ;

[0122] in, It is a weighted zero-knowledge proof; It is a zero-knowledge proof generation algorithm that uses specific mathematical methods or protocols to create a zero-knowledge proof; It is an exponential factor;

[0123] The following formula is used to construct weighted, tamper-proof data packets. :

[0124] ;

[0125] in, It is a weighted, immutable data packet; It is a packet packing function that combines all the necessary verification information into an immutable data packet; It is a scaling factor for the entire data packet, ensuring that each data packet is unique, thereby preventing replay attacks.

[0126] The following are detailed annotations for each parameter:

[0127] In generating weighted hash values In the formula, It is a weighted hash value used to ensure the integrity and uniqueness of timestamps and geolocation information in emergency response records. It is a secure hash algorithm, such as SHA-256, used to generate fixed-length hash values. It is a one-way encryption technique that ensures that any change to the input data will result in a completely different output. This is timestamp data, representing the time information of the emergency rescue record. It is usually represented in Unix timestamp format (i.e., the number of seconds since January 1, 1970). This is geographic location information, indicating the location where the emergency occurred. It can be latitude and longitude coordinates or other geocoding formats. It is a weighting factor for timestamp data, used to adjust the importance of timestamps in hash calculations. It is a weighting factor for geographic location information, used to adjust the importance of geographic location in hash calculation. It is an exponential factor of timestamp data, used to further adjust the impact of timestamps in hash calculations. It is an index factor of geographic location information, used to further adjust the impact of geographic location in hash calculation. It is a concatenation operator used to merge two strings or data sequences into a single unit.

[0128] Constructing weighted composite data structures In the formula, It is a weighted composite data structure that contains a weighted hash value, the identity verification information of the first responders, and the identifier of the first responder equipment. It is the weighted hash value generated in the previous step. It is the identity verification information of emergency responders, usually a unique user ID or digital signature. It is a unique identifier for emergency medical equipment, such as the equipment serial number or other unique identifier. It is a weighting factor for the identity verification information of emergency responders, used to adjust its importance in the composite data structure. It is a weighting factor for emergency medical equipment identifiers, used to adjust their importance in composite data structures.

[0129] Preparing basic data Used in generating zero-knowledge proof formulas, The underlying data used to generate zero-knowledge proofs is ensured to be suitable for processing by zero-knowledge proof algorithms. It is a preparation function that prepares the composite data structure. Convert the data to a basic data format suitable for zero-knowledge proof algorithms. This function may include data formatting, encoding conversion, and other operations. It is a random salt value used to further obfuscate the underlying data, ensuring that different outputs are produced even if the inputs are the same, thus preventing pre-compute attacks. A random salt value is a randomly generated string or number.

[0130] Creating weighted zero-knowledge proofs In the formula, It is a weighted zero-knowledge proof used to verify the authenticity, completeness, and legitimacy of first aid records without revealing the actual content. It is a zero-knowledge proof generation algorithm that uses specific mathematical methods or protocols to create a zero-knowledge proof. It is an exponential factor used to further enhance the security and complexity of zero-knowledge proofs.

[0131] In constructing weighted, tamper-proof data packets In the formula, It is a weighted, immutable data packet that contains all the necessary verification information and ensures that each data packet is unique, thereby preventing replay attacks. This is the packetization function, which combines all necessary verification information into an immutable data packet. This function may include operations such as data serialization and encryption. It is a scaling factor for the entire data packet, used to ensure that each data packet is unique. The scaling factor can be a randomly generated value or a fixed value determined based on other factors.

[0132] The detailed parameter annotations above provide a better understanding of the specific role and significance of each part of the formula. These formulas together form a complete process, from generating weighted hash values ​​to ultimately constructing weighted, immutable data packets, ensuring the authenticity and integrity of emergency medical records while providing an efficient verification mechanism and strict privacy protection. This solution is particularly suitable for the field of emergency medical care, effectively improving data security and transparency.

[0133] Suppose that in a city emergency medical services system, each emergency incident generates an emergency record containing a timestamp, geographic location, emergency responder authentication information, and emergency equipment identifiers. To ensure the security and authenticity of these records, the system uses the following formula to create a weighted zero-knowledge proof and construct an immutable data packet. The following is an example of the steps and calculation process:

[0134] The following is the method for generating weighted hash values. Steps:

[0135] Setting parameters: timestamp data (Converted to Unix timestamp: 1734469500);

[0136] Geographic location information (Converted to latitude and longitude coordinates: 31.2304, 121.5097); weighting factor , Exponential factor , ;

[0137] Calculation formula:

[0138] ;

[0139] Calculation results:

[0140] ;

[0141] ;

[0142] ;

[0143] ;

[0144] Assume the output of SHA-256 is a1b2c3d4e5f6g7h8i9j0k112m3n4o5p6q7r8s9t0u1v2w3x4y5z6;

[0145] The following describes the construction of a weighted composite data structure. Steps:

[0146] Setting parameters: First aid personnel's authentication information (Converted to unique ID: P001); Unique identifier for emergency medical equipment Weighting factors , ;

[0147] Calculation formula:

[0148] ;

[0149] ;

[0150] The following is the preparation of basic data. Steps for generating zero-knowledge proofs:

[0151] Setting parameters: Random salt value ;

[0152] Calculation formula: ;

[0153] Assumption The function will Convert the data to a basic data format suitable for zero-knowledge proof algorithms and attach a random salt value.

[0154] The following is about creating weighted zero-knowledge proofs. Steps:

[0155] Setting parameters: Exponential factor ;

[0156] Calculation formula:

[0157] ;

[0158] Assumption The function generates zero-knowledge proofs, and the exponential operation further enhances the security of the proofs.

[0159] The following is how to construct a weighted, immutable data packet. Steps:

[0160] Setting parameters: scaling factor ;

[0161] Calculation formula:

[0162] ;

[0163] Assumption The function combines all the necessary verification information into an immutable data packet and ensures that each data packet is unique by using a scaling factor.

[0164] Weighted hash value The calculated hash value a1b2c3d4e5f6g7h8i9j0k112m3n405p6q7r8s9t6u1v2w3x4y5z6 is a weighted representation of the emergency record's timestamp and geographic location information, ensuring the integrity and uniqueness of the data.

[0165] Weighted composite data structures : It includes weighted hash values, first responder authentication information, and first responder equipment identifiers, enhancing data traceability and accountability.

[0166] Basic data :pass Functions and random salt values, underlying data Further obfuscation is applied before generating zero-knowledge proofs to ensure that different outputs are produced even with the same input, preventing pre-computation attacks.

[0167] Weighted zero-knowledge proofs Created You can provide evidence to a third party to prove the authenticity, completeness, and legality of the emergency medical records without disclosing any of the actual contents of the records.

[0168] Weighted, immutable data packets : Constructed The data packet not only contains all the verification information, but also ensures that each packet is unique through a scaling factor, thus preventing replay attacks. Ultimately, this data packet can be verified by nodes in the blockchain network to ensure that the emergency medical record has not been altered from its generation to storage, and to verify the authenticity and reliability of its source.

[0169] Through the steps described above, this invention not only ensures the authenticity and integrity of emergency records but also provides an efficient verification mechanism and strict privacy protection, making it suitable for the high reliability and security requirements of the emergency medical field. Furthermore, the application of zero-knowledge proofs enables reliable verification of emergency records while maintaining privacy, enhancing trust and transparency among all parties.

[0170] 103. Based on the data packet containing proof of the authenticity and integrity of the emergency information, the compliance and permissions of the data packet are automatically reviewed by a smart contract to obtain the emergency record data packet that is allowed to be added to the blockchain network;

[0171] In this step, a smart contract is an automatically executed contract term deployed as code on the blockchain. It can automatically trigger specific operations, such as auditing and verifying the compliance and permissions of data packets, when preset conditions are met. Through smart contracts, the system can efficiently check whether each emergency medical record data packet conforms to established standards and rules, ensuring that only legitimate data packets can join the blockchain network.

[0172] Before emergency medical record data packets are uploaded to the blockchain network, they must undergo automatic review by a smart contract. The smart contract checks the hash value, the emergency responder's authentication information, and the identifier of the emergency equipment in the data packet to confirm that they meet preset security standards and permission requirements. If all conditions are met, the smart contract will approve the data packet for inclusion in the blockchain network; otherwise, the data packet will be rejected and returned to the submitter for correction.

[0173] Continuing with the previous implementation, the emergency medical record and its corresponding zero-knowledge proof are sent to a smart contract for review. The smart contract first verifies the validity of the emergency responder's digital signature and checks if the emergency medical device's serial number is registered in the system. Simultaneously, the smart contract also verifies the validity of the zero-knowledge proof to ensure the authenticity and completeness of the emergency medical record. Assuming that the emergency responder Zhang San's digital signature and the emergency medical device's serial number "GJ123456" are both verified, and the zero-knowledge proof is also successfully verified, the smart contract will approve the addition of this emergency medical record to the blockchain network. Conversely, if any condition is not met, the data packet will be marked as invalid and returned to the emergency responder for correction.

[0174] Optionally, step 103, which involves automatically reviewing the compliance and permissions of the data packet containing proof of the authenticity and integrity of the emergency information via a smart contract to obtain an emergency record data packet permitted to join the blockchain network, includes: receiving and processing the data packet containing proof of the authenticity and integrity of the emergency information, ensuring that each data packet contains a timestamp and geographical location information of the emergency event, as well as the identity verification information of the emergency personnel and the identifier of the emergency equipment, to generate an emergency record data packet ready for review; defining review standards using a smart contract, and pre-setting rules and conditions in the smart contract based on the emergency record data packet ready for review, including data format, validity of timestamps, reasonableness of geographical location information, accuracy of the identity verification information of emergency personnel and the identifier of emergency equipment, to generate smart contract rules. The system then performs automated compliance review on the emergency medical record data packets prepared for review, based on the smart contract rule set. This verifies whether the data packets meet all preset conditions, resulting in data packets that pass the initial compliance check. Based on these data packets, permission verification is performed, using the smart contract to confirm the identity and operating permissions of the emergency responder or submitter, generating data packets with sufficient permissions. Finally, based on these data packets with sufficient permissions, the smart contract performs a final review. If the data packets with sufficient permissions pass all compliance and permission checks, a positive review result is generated; otherwise, a negative review result is generated, and a notification mechanism is triggered to inform the relevant parties of the reason. Based on the positive review result, the data packets that pass the smart contract review are marked, resulting in emergency medical record data packets allowed to be added to the blockchain network.

[0175] In this step, a smart contract is an automatically executed contract term deployed on the blockchain in the form of code. It can automatically trigger specific operations when preset conditions are met, such as auditing and verifying the compliance and permissions of data packets. Smart contracts are characterized by transparency, immutability, and automation, and are widely used in blockchain technology. The data packet containing proof of the authenticity and integrity of emergency information includes the timestamp of the emergency event, geographical location information, the identity verification information of the emergency responders, and the identifier of the emergency equipment. This information together constitutes a data structure containing more information, which not only increases the traceability of the data but also facilitates subsequent liability identification and auditing. Audit standards refer to the rules and conditions pre-set in the smart contract to ensure that the emergency record data packet meets established security standards and permission requirements. These standards include, but are not limited to, data format, the validity of the timestamp, the reasonableness of the geographical location information, the accuracy of the identity verification information of the emergency responders, and the accuracy of the emergency equipment identifier. Positive and negative audit results are two possible outcomes after the smart contract audit. A positive audit result indicates that the data packet has passed all compliance and permission checks and can be added to the blockchain network; a negative audit result indicates that the data packet has failed some checks, requires correction or further investigation, and triggers a notification mechanism to inform relevant parties of the reasons.

[0176] First, the system performs preliminary processing on the received data packets containing proof of the authenticity and integrity of emergency information, ensuring that each data packet contains necessary information such as timestamps, geographical location information, identification information of emergency personnel, and identifiers of emergency equipment. Then, it generates emergency record data packets ready for review.

[0177] Secondly, detailed review criteria are defined using smart contracts. Based on the emergency medical record data package to be reviewed, rules and conditions are pre-set in the smart contract. These rules and conditions cover data format, validity of timestamps, reasonableness of geographical location information, accuracy of emergency medical personnel's identity verification information, and accuracy of emergency medical equipment identifiers, forming a smart contract rule set.

[0178] Next, based on the smart contract rule set, the system performs automated compliance review on the emergency medical record data packets prepared for review, verifying whether the data packets meet all preset conditions. The resulting data packets pass the initial compliance check.

[0179] Furthermore, based on the data packet that has passed the initial compliance check, the system performs an authorization verification process, using a smart contract to confirm the identity and operational permissions of the first responder or submitter. This generates a data packet with sufficient permissions.

[0180] Furthermore, based on data packets with sufficient permissions, the system utilizes smart contracts for final review. If a data packet passes all compliance and permission checks, a positive review result is generated; for data packets that fail the review, a negative review result is generated, and a notification mechanism is triggered to inform the relevant parties of the reasons.

[0181] Finally, based on the positive review results, the system marks the data packets that have passed the smart contract review, thus obtaining emergency medical record data packets that are allowed to be added to the blockchain network.

[0182] In this embodiment, it is assumed that, in a specific instance, paramedics in an ambulance use a dedicated application to record the patient's initial diagnosis and treatment. The application automatically obtains the current location from the GPS module integrated into the ambulance and the current time from the device's system clock, then uploads this information along with the emergency records to a central server. For example, an emergency incident occurred at 13:05 on December 17, 2024, at 1000 Lujiazui Ring Road, Pudong New Area, Shanghai.

[0183] First, the system receives a data packet containing proof of the authenticity and completeness of the emergency information. This data packet includes the timestamp of the emergency event "2024-12-17, 13:05", the geographical location information "No. 1000, Lujiazui Ring Road, Pudong New Area, Shanghai", the identity verification information of the emergency responder Zhang San, and the serial number of the emergency equipment "GJ123456". A data packet containing the emergency record is then generated for review.

[0184] Secondly, the system utilizes smart contracts to define detailed review standards and pre-set rules and conditions. For example:

[0185] Data format: Ensure that the emergency medical record data packet is in the correct format.

[0186] Timestamp validity: Verify that the timestamp is within a reasonable range and consistent with the current time.

[0187] Reasonableness of geographical location information: Check whether the geographical location information is located in a reasonable emergency response area.

[0188] First aid personnel authentication information: confirms that the first aid personnel's digital signature is valid and that their identity has been registered in the system.

[0189] Accuracy of emergency equipment identifiers: Verify that the serial number of the emergency equipment exists in the system's registration list.

[0190] These rules and conditions together constitute the smart contract rule set, ensuring that emergency medical record data packets meet all security standards and permission requirements.

[0191] Next, based on the smart contract rule set, the system performs automated compliance review of the emergency medical record data packets to be reviewed. For example, the system verifies whether the timestamp "2024-12-17, 13:05" is within a reasonable range, whether the geographical location "No. 1000, Lujiazui Ring Road, Pudong New Area, Shanghai" is within the emergency response area, whether the digital signature of the emergency responder Zhang San is valid, and whether the emergency medical equipment serial number "GJ123456" is registered in the system.

[0192] If all conditions are met, the data packet passes the initial compliance check and proceeds to the next step of permission verification.

[0193] Then, the system performs permission verification based on the data packets that have passed the initial compliance check. For example, the system confirms whether emergency responder Zhang San has sufficient permissions to submit emergency records and verifies the legitimacy of his identity.

[0194] If the permission verification is successful, a data packet with sufficient permissions will be generated and proceed to the final review and processing stage.

[0195] Furthermore, the system uses smart contracts to perform final review of data packets with sufficient permissions. If the data packet passes all compliance and permission checks, a positive review result is generated; otherwise, a negative review result is generated, and a notification mechanism is triggered to inform the relevant parties of the reason. For example, if the data format of an emergency medical record is incorrect or the identity of the emergency responder fails verification, the system will generate a negative review result and send a notification to the emergency responder explaining the specific problem.

[0196] Finally, based on the positive review results, the system marks the data packets that pass the smart contract review, resulting in first aid record data packets that are allowed to be added to the blockchain network. For example, the system adds a "reviewed" tag to a first aid record that passes the review and officially adds it to the blockchain network.

[0197] Through the above steps, this invention not only ensures the authenticity and completeness of emergency medical records but also provides an efficient review mechanism and strict access control, meeting the high reliability and security requirements of the emergency medical field. Furthermore, the application of smart contracts makes the review process more transparent and automated, enhancing trust and transparency among all parties, while also improving review efficiency and accuracy.

[0198] 104. Using a distributed consensus algorithm, the emergency medical record data packets allowed to be added to the blockchain network are synchronized among multiple nodes, and an off-chain computing mechanism is introduced to process a large number of transactions, resulting in emergency medical records that are securely and transparently stored in the absence of centralized management.

[0199] In this step, distributed consensus algorithms are a type of technology that ensures multiple nodes reach consensus within a network and are widely used in blockchain systems. Through distributed consensus algorithms, the system can achieve the collaborative maintenance and updating of the emergency response record database by multiple nodes without a single controlling entity. Off-chain computation mechanisms are used to handle large volumes of transactions or non-critical transactions that do not need to be immediately reflected on-chain, improving system efficiency and responsiveness.

[0200] Once the emergency medical record data packets pass smart contract verification, the system uses a distributed consensus algorithm to synchronize these packets across multiple nodes. Each participating node votes on the data packets, ensuring a majority of nodes agree and verify their validity. For large amounts of emergency medical record data or non-critical transactions that do not need to be immediately reflected on the blockchain, the system introduces an off-chain computation mechanism for processing, reducing the burden on the main chain. Finally, the verified data packets will be officially added to the blockchain, achieving secure and transparent data storage.

[0201] After the emergency medical records are reviewed by the smart contract, the system initiates a distributed consensus algorithm, allowing nodes to synchronize and vote on the data packets. Assuming 10 nodes participate in the consensus, if 8 nodes agree on the validity of the emergency medical record (more than two-thirds majority), the record is officially added to the blockchain. Simultaneously, the system identifies some emergency medical records as non-critical transactions, such as routine vital sign monitoring data, and decides to temporarily process this data off-chain. The off-chain computation mechanism quickly processes this data and reintroduces the results to the main chain when appropriate, ensuring efficient system operation. For example, in a particular emergency medical event, in addition to emergency treatment measures, there is a large amount of vital sign monitoring data. This data is processed off-chain and only synchronized to the main chain when needed, improving the overall system performance.

[0202] Optionally, step 104, which utilizes a distributed consensus algorithm to synchronize the emergency medical record data packets allowed to be added to the blockchain network across multiple nodes and introduces an off-chain computing mechanism to process a large number of transactions, resulting in emergency medical records securely and transparently stored without centralized management, includes: using a distributed consensus algorithm to synchronize the emergency medical record data packets allowed to be added to the blockchain network after passing smart contract review, obtaining emergency medical record data packets that have reached consensus and been verified as valid by a majority of nodes; and, based on the consensus and verified valid emergency medical record data packets, adding them to the blockchain under decentralized management, generating emergency medical records stored securely and transparently without a single controlling entity. Confirmed valid emergency medical record data; based on the valid emergency medical record data, an off-chain computation mechanism is introduced to process large amounts of emergency medical record data or non-critical transactions that do not need to be reflected on the chain immediately, in order to meet the needs of efficient processing and obtain preliminary results after off-chain computation; using a distributed consensus algorithm, the preliminary results after off-chain computation are verified again to ensure that the preliminary results after off-chain computation meet the standards for joining the main chain, generating emergency medical record data that is finally officially added to the blockchain; based on the emergency medical record data that is finally officially added to the blockchain, through a combination of further distributed consensus algorithms and off-chain computation mechanisms, emergency medical records that are securely and transparently stored in a decentralized management environment are obtained.

[0203] In this step, distributed consensus algorithms are a technology that ensures multiple nodes reach consensus within a network and are widely used in blockchain systems. Through distributed consensus algorithms, the system can achieve the joint maintenance and updating of the emergency medical record database by multiple nodes without a single controlling entity. Common distributed consensus algorithms include Proof-of-Work, Proof-of-Stake, and Byzantine Fault Tolerance. Inter-node synchronization processing refers to distributing emergency medical record data packets, verified by smart contracts, to multiple nodes in the network and ensuring that all nodes have the same copy of the data. This step ensures data consistency and reliability. Decentralized management refers to the joint management and verification of data by distributed nodes without a central authority. This approach enhances the system's transparency and security, preventing single points of failure or tampering risks. Off-chain computation mechanisms are an optimization technique used to handle large numbers of transactions or non-critical transactions that do not need to be immediately reflected on the main chain. It reduces the burden on the main chain and improves system efficiency and responsiveness by performing computation and verification off-chain. Preliminary results refer to the results obtained after off-chain computation. These results need to be verified again through distributed consensus algorithms to ensure they meet the standards for inclusion on the main chain. The emergency medical records that are ultimately added to the blockchain refer to those that have undergone multiple verifications and processing before being confirmed and added to the blockchain. This data possesses immutability and high security, ensuring the authenticity and integrity of the emergency medical records.

[0204] First, the system uses a distributed consensus algorithm to synchronize emergency medical record data packets that have passed the smart contract review between nodes, ensuring that most nodes reach a consensus and verify the validity of the emergency medical record data packets.

[0205] Secondly, based on the agreed-upon and verified first aid record data packets, the system processes them under decentralized management and adds them to the blockchain, generating valid first aid record data that is confirmed without a single controlling entity.

[0206] Next, based on valid emergency medical records, the system introduces an off-chain computing mechanism to process large amounts of emergency medical records or non-critical transactions that do not need to be reflected on the chain in real time, in order to meet the need for efficient processing and obtain preliminary results after off-chain computation.

[0207] Furthermore, using a distributed consensus algorithm, the preliminary results after off-chain computation are verified again to ensure that these preliminary results meet the standards for joining the main chain, thus generating the emergency medical record data that is finally officially added to the blockchain.

[0208] Finally, based on the emergency medical records data that are officially added to the blockchain, the system ensures that the emergency medical records are securely and transparently stored in a decentralized manner by combining further distributed consensus algorithms and off-chain computing mechanisms.

[0209] In this embodiment, it is assumed that, in a specific instance, paramedics in an ambulance use a dedicated application to record the patient's initial diagnosis and treatment. The application automatically obtains the current location from the GPS module integrated into the ambulance and the current time from the device's system clock, then uploads this information along with the emergency records to a central server. For example, an emergency incident occurred at 13:05 on December 17, 2024, at 1000 Lujiazui Ring Road, Pudong New Area, Shanghai.

[0210] First, the system receives the emergency medical record data packet that has passed the smart contract review. Using a distributed consensus algorithm, it distributes the packet to multiple nodes in the network. Each node independently verifies the packet to ensure it meets preset standards and conditions. Assuming 10 nodes participate in the consensus, and 8 nodes agree on the validity of the emergency medical record—a two-thirds majority—the record is officially confirmed as valid.

[0211] Secondly, based on the agreed-upon and verified emergency medical record data package, the system processes it by adding it to the blockchain under decentralized management. Each node adds the emergency medical record to its local blockchain copy, generating valid emergency medical record data that is confirmed without a single controlling entity. For example, the emergency medical record "Patient Zhang San, abnormal heart rate, oxygen given" is officially added to the blockchain, ensuring its immutability and transparency.

[0212] Next, based on valid emergency medical records, the system identified certain records as non-critical transactions, such as routine vital sign monitoring data, and decided to temporarily process this data off-chain. The off-chain computation mechanism quickly processed this data and reintroduced the results to the main chain when appropriate, ensuring efficient system operation. For example, emergency responders record a patient's heart rate and blood pressure every minute during an emergency; this data is processed off-chain and only synchronized to the main chain when needed, improving overall system performance.

[0213] Furthermore, utilizing a distributed consensus algorithm, the system re-verifies the preliminary results after off-chain computation. For example, assuming the off-chain computation mechanism processes 100 vital sign monitoring data points, the system resubmits these preliminary results to the distributed consensus algorithm for verification. If all preliminary results meet the preset standards, they will be officially added to the main chain; otherwise, non-compliant data will be marked as invalid and returned to the off-chain computation mechanism for correction.

[0214] Finally, based on the emergency medical records that are officially added to the blockchain, the system ensures that these records are securely and transparently stored in a decentralized manner through a combination of further distributed consensus algorithms and off-chain computation mechanisms. For example, the emergency medical record "Patient Zhang San, abnormal heart rate, oxygen administered" and its associated vital sign monitoring data are officially added to the blockchain to ensure their immutability and transparency, while protecting the patient's privacy.

[0215] Through the above steps, this invention not only ensures the authenticity and integrity of emergency medical records but also provides an efficient processing mechanism and strict access control, meeting the high reliability and security requirements of the emergency medical field. Furthermore, the application of distributed consensus algorithms and off-chain computation mechanisms makes the emergency medical record management system more efficient, transparent, and secure, enhancing trust and transparency among all parties, while also improving the system's response speed and processing capacity.

[0216] This application recognizes that ensuring the authenticity and integrity of emergency medical records is crucial in the field of emergency medicine. Traditional centralized data management systems are vulnerable to tampering and privacy breaches, especially when sensitive medical information is involved. To overcome these challenges, the research team proposes a solution based on a distributed consensus algorithm and off-chain computing mechanism, combining smart contract auditing, weighted synchronization, and consensus voting to ensure that emergency medical records are securely and transparently stored without centralized management. This solution not only verifies the validity of emergency medical records but also efficiently processes large volumes of transactions, improving system reliability and response speed. Therefore, a new alternative solution is proposed, which includes:

[0217] Optionally, in step 104, the distributed consensus algorithm is used to synchronize the emergency medical record data packets allowed to be added to the blockchain network across multiple nodes, and an off-chain computing mechanism is introduced to process a large number of transactions, resulting in emergency medical records that are securely and transparently stored in a decentralized management environment, including:

[0218] Audit formula via smart contract Obtain the approved emergency medical record data package. ;

[0219] in, This refers to a data unit containing emergency information that has undergone hashing and zero-knowledge proof processing;

[0220] Through the weighted synchronization formula This yields the synchronized data packets across multiple nodes; It is a weighted synchronization function used to synchronize data packets that have been reviewed and deemed acceptable by the smart contract. Synchronization is performed across multiple nodes; among them, It is the set of nodes participating in the consensus process; It is the weight factor for each node; Refers to smart contracts Data packets that have been reviewed and deemed acceptable;

[0221] Through consensus formula This yields a data packet that is agreed upon by a majority of nodes; This is a consensus function used to ensure that a majority of nodes agree on the validity of data packets. It returns true if and only if the sum of the weighted votes exceeds a set threshold; otherwise, it returns false.

[0222] in, Indicates the first The voting results of each node; This refers to the number of nodes participating in the consensus vote; It is The weight factor of each node; It is an exponential factor of the consensus voting result; It is an exponential factor of the threshold; This refers to the minimum percentage of votes required to reach a consensus; From 1 to An integer representing each node participating in the consensus vote;

[0223] By verifying the formula The resulting emergency rescue record data packet was ultimately agreed upon and verified by a majority of nodes. ; It is an exponential factor of the consensus voting result, which increases the security and complexity of the consensus mechanism, making the system more difficult to attack.

[0224] The following are detailed annotations for each parameter:

[0225] In smart contract audit formula middle, It is a data package of emergency medical records that has been reviewed and deemed qualified by the smart contract; This is a smart contract audit function used for verification. Compliance and permissions. This function checks whether data packets meet the standards for joining the blockchain network according to preset rules; The data unit containing emergency information has been processed using hashing and zero-knowledge proofs. It includes, but is not limited to, timestamps, geographic location, emergency responder authentication information, and identifiers for emergency equipment.

[0226] In the weighted synchronization formula middle, It is a weighted synchronization function used to synchronize data packets that have been reviewed and deemed acceptable by the smart contract. Synchronization across multiple nodes; It is a data package of emergency medical records that has been reviewed and deemed qualified by the smart contract; It is the set of nodes participating in the consensus process, for example ,in It is the number of nodes participating in the consensus; This is the weight factor for each node, representing the weight each node occupies during the synchronization process. The weight factor can be determined based on factors such as the node's historical performance and reliability.

[0227] In consensus formula middle, This is a consensus function used to ensure that a majority of nodes agree on the validity of data packets. It returns true if and only if the sum of the weighted votes exceeds a set threshold; otherwise, it returns false. It is the set of nodes participating in the consensus process, for example ,in It is the number of nodes participating in the consensus; This refers to the minimum percentage of votes required to reach a consensus, for example... This means that at least 75% of the nodes need to agree; It is The voting results of each node, where 0 represents dissent and 1 represents agreement; It is The weight factor of each node represents the weight of each node in the consensus vote; It is an exponential factor of the consensus voting result, which increases the security and complexity of the consensus mechanism, making the system more difficult to attack; It is an exponential factor of the threshold, used to adjust the strictness of the consensus threshold; From 1 to An integer representing each node participating in the consensus vote;

[0228] In verifying the formula middle, This is a verification function used to finally confirm the validity of the emergency medical record data packet; It is a data package of emergency medical records that has been reviewed and deemed qualified by the smart contract; It is the set of nodes participating in the consensus process; This is the minimum percentage of votes required to reach a consensus; It is the weight factor for each node.

[0229] It is an exponential factor of the consensus voting result; It is an exponential factor of the threshold; It is the emergency rescue record data packet that is ultimately agreed upon and verified as valid by the majority of nodes;

[0230] These detailed parameter annotations provide a better understanding of the specific role and significance of each part of the formula. Together, these formulas form a complete process, from smart contract review to final verification, ensuring the authenticity and integrity of emergency medical records while providing an efficient verification mechanism and strict privacy protection. This solution is particularly suitable for the field of emergency medical care, effectively improving data security and transparency.

[0231] In a city emergency medical services system, each emergency incident generates an emergency record containing a timestamp, geographic location, emergency responder authentication information, and emergency equipment identifiers. To ensure the authenticity and integrity of these records, the system employs the following formula to implement distributed consensus and off-chain computation mechanisms.

[0232] The following are the steps and calculation process of the embodiment:

[0233] Verification formula via smart contract:

[0234] ;

[0235] Parameter settings: It refers to a data unit containing emergency information that has undergone hashing and zero-knowledge proof processing. This is a smart contract audit function used for verification. Compliance and authority.

[0236] Assumption Includes the following information: Timestamp: 2024-12-17T13:05:00 (Unix timestamp: 1734469500); Geographic location: No. 1000, Lujiazui Ring Road, Pudong New Area, Shanghai (latitude and longitude: 31.2304, 121.5097); Emergency responder ID: P001; Emergency equipment ID: GJ123456; Zero-knowledge proof: ;

[0237] Return after smart contract review This indicates that the data packet has passed the review.

[0238] Through the weighted synchronization formula:

[0239] ;

[0240] Parameter settings: It is a data packet that has been reviewed and deemed qualified by the smart contract; It is the set of nodes participating in the consensus process, for example ; It is the weight factor of each node, for example (All nodes have equal weight);

[0241] Assumption Having passed the smart contract review, the system sends the data packet to all nodes participating in the consensus for synchronization. Each node receives and verifies the data packet according to its weight factor. Ultimately, all nodes reach a consensus and obtain the synchronized data packet. .

[0242] Through consensus formula:

[0243] ;

[0244] Parameter settings: Indicates the first The voting results of each node (0 indicates dissent, 1 indicates agreement); It is the number of nodes participating in consensus voting, for example ; It is The weight factors of each node, for example ; It is an exponential factor of the consensus voting result, for example ; It is an exponential factor of the threshold, for example ; This refers to the minimum percentage of votes required to reach a consensus, for example... .

[0245] Assume the voting results of each node are as follows: ; ; ; ; ;

[0246] Consensus calculation formula:

[0247] ;

[0248] Calculate the threshold:

[0249] ;

[0250] because Therefore, the consensus formula is invalid and a revote or parameter adjustment is required. The formula is verified as follows: .

[0251] Parameter settings: It is a data packet that has been reviewed and deemed qualified by the smart contract; It is the set of nodes participating in the consensus process; This is the minimum percentage of votes required to reach a consensus; It is the weight factor for each node; It is an exponential factor of the consensus voting result; It is an exponential factor of the threshold;

[0252] After a revote or parameter adjustment, assuming the consensus formula holds true, the system finally confirms... This indicates that the data packet has passed the verification of most nodes and has become a valid emergency rescue record data packet.

[0253] Through the above steps, this invention not only ensures the authenticity and integrity of emergency medical records, but also provides an efficient verification mechanism and strict privacy protection. Specifically:

[0254] Audit formula via smart contract This ensures that only emergency medical record data packets that meet the preset conditions can proceed to the next step of processing.

[0255] Through the weighted synchronization formula This ensures that multiple nodes can consistently receive and verify the same emergency record data packets, preventing data loss or alteration.

[0256] Consensus mechanism: through consensus formula This ensures that a majority of nodes agree on the validity of data packets. This step increases the system's security and complexity, making it more difficult to attack.

[0257] By verifying the formula Finally, valid emergency medical record data packages are confirmed to ensure their authenticity and completeness.

[0258] This solution is particularly suitable for the field of emergency medical care, as it can effectively improve data security and transparency, enhance trust among all parties, and ensure that emergency records are safely and transparently stored in a decentralized manner.

[0259] 105. Based on the secure and transparently stored emergency medical records, an access control interface is provided, enabling relevant parties to query and verify the emergency medical records in accordance with strict privacy protection rules, but prohibiting unauthorized modification or deletion.

[0260] In this step, the access control interface serves as a security layer provided by the system, ensuring that only authorized parties can query and verify emergency medical records. Strict privacy rules restrict who can access which data, preventing unauthorized modification or deletion. In this way, the system ensures both the security and transparency of emergency medical records while protecting patient privacy.

[0261] The system provides an access control interface for first aid records, which strictly adheres to privacy protection rules. Only authenticated and authorized users can access specific first aid records. Every access request is logged for auditing and tracking purposes. Furthermore, the system is designed to disallow unauthorized modification or deletion, ensuring data integrity and reliability.

[0262] Finally, the system provides a secure access control interface for emergency medical records, accessible to hospital doctors and administrators. For example, if a doctor needs to access a patient's emergency medical records, they must first log in via two-factor authentication. After successful login, the doctor can only access emergency medical records relevant to their department, and all access activities are meticulously recorded for subsequent auditing. The system also employs strict access controls, preventing doctors from modifying or deleting emergency medical records even with access privileges, ensuring data authenticity and integrity. This mechanism not only protects patient privacy but also enhances the security and reliability of the emergency medical record management system.

[0263] Optionally, step 105, based on the securely and transparently stored emergency medical records, provides an access control interface to allow relevant parties to query and verify the emergency medical records while adhering to strict privacy protection rules, but prohibiting unauthorized modification or deletion. This includes: constructing an access control system based on the securely and transparently stored emergency medical records in a decentralized management environment; configuring the access control system to identify and verify the identity of relevant parties requesting to query or verify the emergency medical records, resulting in an access control system that ensures only authorized users operate according to strict privacy protection rules; enhancing the access control system using encryption technology and a permission management system to ensure that each query or verification request undergoes strict identity verification and permission checks, generating a protected access control interface that only allows requests conforming to preset permission rules to pass; and, based on the protected access control interface, tailoring the different roles and needs of relevant parties... The system requests and implements customized access levels and permission ranges to ensure appropriate access permissions for different roles. Leveraging the immutability of blockchain, all queries and verification activities based on these customized access permission settings are recorded, generating an unalterable and transparent access log to guarantee system transparency and post-audit capabilities. Access control policies are automatically executed via smart contracts, processing access requests recorded in the unalterable and transparent access log according to pre-defined rules, creating a smart contract-protected access control execution mechanism to prevent unauthorized modification or deletion. A logging function is provided to record every successful or attempted access behavior within the smart contract-protected access control execution mechanism, including visitor identity, access time, and access content, generating secure and immutable log records stored on the blockchain.

[0264] In this step, the access control system is a security mechanism used to manage who can access which resources. In the emergency medical record management system, the access control system ensures that only authorized users can perform query and verification operations according to strict privacy protection rules. Encryption technology is used to protect the confidentiality and integrity of data. Through encryption, the system can ensure that emergency medical records are not viewed or tampered with by unauthorized third parties during transmission and storage. The permission management system refers to the system used to define and manage user permissions. It ensures that each user can only access specific data and perform specific operations according to their role and needs. The access control interface is the interaction interface between the access control system and external users. It ensures that every query or verification request undergoes strict authentication and permission checks, allowing only requests that conform to preset permission rules to pass. Customized access permission settings are tailored to different roles and needs, providing different access levels and permission scopes for relevant parties. This ensures that different roles have appropriate access permissions, guaranteeing both system flexibility and data security. Immutable and transparent access logs, combined with the immutability of blockchain, record all query and verification activities. These logs not only ensure system transparency but also provide post-event auditing capabilities. The access control enforcement mechanism secured by smart contracts automatically executes access control policies, ensuring that unauthorized modification or deletion operations are not permitted. The application of smart contracts makes the access control process more transparent and automated. The logging function meticulously records every successful or attempted access, including visitor identity, access time, and access content, generating secure and tamper-proof log records stored on the blockchain.

[0265] First, based on the first aid records that are securely and transparently stored in a decentralized management environment, an access control system is built. The access control system is configured to identify and verify the identity of the parties requesting to query or verify the first aid records, thus obtaining an access control system that can ensure that only authorized users operate in accordance with strict privacy protection rules.

[0266] Secondly, the access control system is enhanced using encryption technology and a permission management system to ensure that every query or verification request undergoes strict authentication and permission checks, generating a protected access control interface. This interface only allows requests that conform to preset permission rules to pass through.

[0267] Next, based on the protected access control interface, different access levels and permission ranges are customized for different roles and needs of relevant parties, resulting in customized access permission settings to ensure that different roles have appropriate access permissions.

[0268] Furthermore, leveraging the immutability of blockchain, all query and verification activities based on customized access permission settings are recorded, generating unalterable and transparent access logs to ensure system transparency and post-audit capabilities.

[0269] Furthermore, by automatically executing access control policies through smart contracts, access requests recorded in the immutable and transparent access log are processed automatically according to pre-set rules, generating an access control enforcement mechanism guaranteed by smart contracts to ensure that unauthorized modification or deletion operations are not allowed.

[0270] Finally, a logging function is provided to record every successful or attempted access behavior in the access control execution mechanism based on smart contracts in detail, including information such as visitor identity, access time, and access content, and generate secure and tamper-proof log records stored on the blockchain.

[0271] In this embodiment, it is assumed that, in a specific instance, paramedics in an ambulance use a dedicated application to record the patient's initial diagnosis and treatment. The application automatically obtains the current location from the GPS module integrated into the ambulance and the current time from the device's system clock, then uploads this information along with the emergency records to a central server. For example, an emergency incident occurred at 13:05 on December 17, 2024, at 1000 Lujiazui Ring Road, Pudong New Area, Shanghai.

[0272] First, the system builds an access control system based on securely and transparently stored emergency medical records. This system can identify and verify the identities of relevant parties requesting access to or verification of emergency medical records, such as hospital doctors, emergency personnel, and administrators. The system ensures that only authorized users can operate in accordance with strict privacy protection rules.

[0273] Secondly, the system enhances the access control system using encryption technology and a permission management system. For example, it employs AES-256 encryption to protect the transmission and storage of emergency medical records, while defining each user's role and permissions through the permission management system. The system generates a protected access control interface, ensuring that every query or verification request undergoes rigorous authentication and permission checks.

[0274] Next, the system customizes different access levels and permission ranges based on different roles and needs. For example, hospital doctors can view a patient's specific emergency records but cannot modify them; emergency responders can add new emergency records but cannot view other emergency responders' records; administrators can review all emergency records but cannot directly participate in emergency operations. This customized access permission setting ensures that different roles have appropriate access permissions, guaranteeing both system flexibility and data security.

[0275] Furthermore, leveraging the immutability of blockchain, the system records all query and verification activities. For example, every time a doctor queries patient Zhang San's emergency medical records, the system records the query time, the doctor's identity information, and the specific content of the query on the blockchain. These immutable and transparent access logs not only ensure the system's transparency but also provide post-event auditing capabilities.

[0276] Furthermore, the system automatically enforces access control policies through smart contracts to ensure that unauthorized modification or deletion operations are not permitted. For example, when a user attempts to delete a first aid record, the smart contract automatically checks the user's permissions. If the user does not have deletion permissions, the request is rejected, and the attempted operation is recorded on the blockchain.

[0277] Finally, the system provides a logging function to record every successful or attempted access in detail. For example, the system records that Doctor A successfully queried patient Zhang San's emergency medical records at 2:30 PM on December 18, 2024, and that User B attempted to delete an emergency medical record at 3:00 PM on the same day but was refused. These log records are stored on the blockchain, ensuring their security and immutability, and providing a reliable basis for subsequent audits and investigations.

[0278] Through the above steps, this invention not only ensures the authenticity and integrity of emergency medical records but also provides an efficient access control mechanism and strict permission management, suitable for the high reliability and security requirements of the emergency medical field. Furthermore, the application of the access control system and smart contracts makes the emergency medical record management system more secure, transparent, and automated, enhancing trust and transparency among all parties, while also improving the system's response speed and processing capacity.

[0279] Figure 2 This application provides a schematic diagram of the structure of a secure storage system for emergency medical records based on blockchain technology, as shown in the embodiment of the present application. Figure 2 As shown, the system includes:

[0280] The receiving module 21 is used to receive emergency record data generated in emergency events, and to add a timestamp and geographic location information to each emergency record data to obtain emergency record data containing timestamp and geographic location information;

[0281] The conversion construction module 22 is used to convert the emergency record data containing timestamp and geographical location information using a hash function, and combine the identity verification information of emergency personnel and the identifier of emergency equipment to construct an immutable data packet based on a zero-knowledge proof algorithm, thereby obtaining a data packet containing proof of the authenticity and integrity of emergency information.

[0282] The review module 23 is used to automatically review the compliance and permissions of the data packet containing the proof of authenticity and integrity of the emergency information through a smart contract, and obtain the emergency record data packet that is allowed to be added to the blockchain network.

[0283] Processing module 24 is used to use a distributed consensus algorithm to synchronize the emergency medical record data packets that are allowed to be added to the blockchain network among multiple nodes, and to introduce an off-chain computing mechanism to process a large number of transactions, so as to obtain emergency medical records that are securely and transparently stored in the absence of centralized management.

[0284] Module 25 is provided to provide an access control interface based on the securely and transparently stored emergency medical records, enabling relevant parties to query and verify the emergency medical records in accordance with strict privacy protection rules, but not allowing unauthorized modification or deletion operations.

[0285] Figure 2 The aforementioned blockchain-based emergency medical record secure storage system can perform... Figure 1 The implementation principle and technical effects of the blockchain-based emergency record secure storage method described in the illustrated embodiment will not be repeated here. The specific methods by which each module and unit of the blockchain-based emergency record secure storage system performs its operations have been described in detail in the embodiments related to this method, and will not be elaborated upon here.

[0286] In one possible design, Figure 2 The blockchain-based emergency medical record secure storage system illustrated in this embodiment can be implemented as a computing device, such as... Figure 3 As shown, the computing device may include a storage component 31 and a processing component 32;

[0287] The storage component 31 stores one or more computer instructions, wherein the one or more computer instructions are invoked and executed by the processing component 32.

[0288] The processing component 32 is used to: receive emergency record data generated during emergency events, and add timestamps and geographic location information to each emergency record data to obtain emergency record data containing timestamps and geographic location information; convert the emergency record data containing timestamps and geographic location information using a hash algorithm, and combine it with the identity verification information of emergency personnel and the identifier of emergency equipment, and construct an immutable data packet based on a zero-knowledge proof algorithm to obtain a data packet containing proof of the authenticity and integrity of emergency information; automatically review the compliance and permissions of the data packet through a smart contract based on the data packet containing proof of the authenticity and integrity of emergency information to obtain an emergency record data packet that is allowed to join the blockchain network; use a distributed consensus algorithm to synchronize the emergency record data packet that is allowed to join the blockchain network among multiple nodes, and introduce off-chain computing mechanisms to process a large number of transactions to obtain emergency records that are securely and transparently stored in the absence of centralized management; and provide an access control interface based on the securely and transparently stored emergency records, so that relevant parties can query and verify emergency records under strict privacy protection rules, but unauthorized modification or deletion is not allowed.

[0289] The processing component 32 may include one or more processors to execute computer instructions to complete all or part of the steps in the above-described method. Alternatively, the processing component may be implemented as one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above-described method.

[0290] Storage component 31 is configured to store various types of data to support operations at the terminal. The storage component can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0291] Of course, computing devices may also include other components, such as input / output interfaces, display components, communication components, etc.

[0292] Input / output interfaces provide interfaces between processing components and peripheral interface modules, which can be output devices, input devices, etc.

[0293] The communication components are configured to facilitate wired or wireless communication between computing devices and other devices.

[0294] The computing device can be a physical device or an elastic computing host provided by a cloud computing platform. In this case, the computing device can refer to a cloud server, and the aforementioned processing components, storage components, etc., can be basic server resources rented or purchased from the cloud computing platform.

[0295] This application also provides a computer storage medium storing a computer program, which, when executed by a computer, can perform the above-described functions. Figure 1 The illustrated embodiment is a method for securely storing emergency medical records based on blockchain technology.

[0296] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0297] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, i.e., they may be located in one location or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of the present embodiment. Persons of ordinary skill in the art will be able to understand and implement the present invention without inventive effort.

[0298] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

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

Claims

1. A method for securely storing emergency medical records based on blockchain technology, characterized in that, include: Receive emergency record data generated during emergency events, and add timestamps and geographic location information to each emergency record data to obtain emergency record data containing timestamps and geographic location information; The emergency medical record data containing timestamps and geographic location information is transformed using a hash algorithm. Combined with the identity verification information of emergency medical personnel and the identifier of emergency medical equipment, an immutable data packet is constructed based on a zero-knowledge proof algorithm to obtain a data packet containing proof of the authenticity and integrity of emergency medical information. Based on the data packet containing proof of the authenticity and integrity of the emergency information, the compliance and permissions of the data packet are automatically reviewed by a smart contract to obtain an emergency record data packet that is allowed to be added to the blockchain network; By using a distributed consensus algorithm, the emergency medical records data packets that are allowed to be added to the blockchain network are synchronized among multiple nodes, and an off-chain computing mechanism is introduced to process a large number of transactions, resulting in emergency medical records that are securely and transparently stored in the absence of centralized management. Based on the secure and transparently stored emergency medical records, an access control interface is provided, allowing relevant parties to query and verify the emergency medical records in accordance with strict privacy protection rules, but unauthorized modification or deletion is not allowed. The process of automatically verifying the compliance and permissions of the data packet containing proof of the authenticity and integrity of the emergency medical information through a smart contract to obtain an emergency medical record data packet that is allowed to be added to the blockchain network includes: Based on the data packet containing the proof of authenticity and integrity of the emergency information, the data packet containing the proof of authenticity and integrity of the emergency information is received and processed to ensure that each data packet contains the timestamp and geographical location information of the emergency event, as well as the identity verification information of the emergency personnel and the identifier of the emergency equipment, and to generate an emergency record data packet ready for review. By using smart contracts to define review standards, and based on the emergency medical record data packets to be reviewed, rules and conditions in the smart contract are pre-set, including data format, validity of timestamps, rationality of geographical location information, accuracy of emergency personnel's identity verification information and emergency equipment identifiers, to generate a smart contract rule set; based on the smart contract rule set, the emergency medical record data packets to be reviewed are automatically processed for compliance review, verifying whether the data packets meet all preset conditions, and obtaining data packets that pass the preliminary compliance check.

2. The method according to claim 1, characterized in that, The method involves using a hash algorithm to transform the emergency medical record data containing timestamps and geographic location information, and combining this with the identity verification information of the emergency medical personnel and the identifiers of the emergency medical equipment. Based on a zero-knowledge proof algorithm, an immutable data packet is constructed to obtain a data packet containing proof of the authenticity and integrity of the emergency medical information, including: Using a secure hash algorithm, emergency medical record data containing timestamps and geographic location information is processed to obtain a unique hash value. This unique hash value serves as a digital fingerprint of the emergency medical record data, ensuring the integrity and uniqueness of the data. Based on the unique hash value, combined with the identity verification information of the emergency responders and the unique identifier of the emergency equipment, a composite data structure is constructed. The composite data structure contains the contents of the emergency record, associates the specific executor of the emergency operation with the equipment used, and increases the traceability of the data and the attribution of responsibility. Based on the aforementioned composite data structure, a proof is created using a zero-knowledge proof algorithm. This proof allows evidence to be provided to a third party without revealing any actual contents of the emergency medical record, demonstrating the authenticity, completeness, and legality of the emergency medical record's source, thus obtaining a zero-knowledge proof. Based on the zero-knowledge proof, the original emergency record hash, the emergency personnel's identity verification information, and the emergency equipment identifier are packaged together to form an immutable data packet. This data packet can be verified by nodes in the blockchain network to ensure that the emergency record has not been tampered with from generation to storage, and to verify the authenticity and reliability of the source of the emergency record, ultimately resulting in a data packet containing proof of the authenticity and integrity of the emergency information.

3. The method according to claim 2, characterized in that, The process utilizes a secure hash algorithm to process emergency medical record data containing timestamps and geographic location information, obtaining a unique hash value. This unique hash value serves as a digital fingerprint of the emergency medical record data, ensuring data integrity and uniqueness. This includes: Based on the emergency medical record data containing timestamps and geographic location information, a recognized secure hash algorithm is selected, which is collision resistant. Using the aforementioned secure hash algorithm, emergency medical record data containing timestamps and geographic location information is processed to obtain a unique hash value, which serves as the digital fingerprint of the emergency medical record data. Based on the unique hash value, before adding the unique hash value to the blockchain, check whether there is an existing hash value with the same unique hash value in the current blockchain network to verify the uniqueness of the hash value and obtain the verified hash value; Based on the verified hash value, the verified hash value is associated with the corresponding emergency medical record data to ensure that each emergency medical record has a unique digital fingerprint, which helps to build an immutable data packet and quickly locate and verify the emergency medical record when needed.

4. The method according to claim 2, characterized in that, The method involves creating a proof using a zero-knowledge proof algorithm based on the composite data structure. This proof allows evidence to be provided to a third party without revealing any actual first aid record content, demonstrating the authenticity, completeness, and legality of the first aid record's source. The zero-knowledge proof includes: Based on the constructed composite data structure, the underlying data for generating zero-knowledge proofs is prepared using the composite data structure. By using a zero-knowledge proof algorithm to process the basic data, a zero-knowledge proof is created and obtained without disclosing any actual emergency medical record content. This zero-knowledge proof can provide evidence to a third party without disclosing the specific content of the emergency medical record, proving the authenticity, completeness, and legality of the source of the emergency medical record. Based on the zero-knowledge proof, combined with the hash value, the identity verification information of the emergency responders, and the identifier of the emergency equipment in the composite data structure, verification information is provided for the subsequent construction of an immutable data packet, ensuring that the emergency record is not tampered with from generation to storage, and verifying the authenticity and reliability of the source of the emergency record.

5. The method according to claim 1, characterized in that, The method utilizes a distributed consensus algorithm to synchronize emergency medical record data packets that are allowed to be added to the blockchain network across multiple nodes, and introduces an off-chain computing mechanism to process a large number of transactions, resulting in emergency medical records that are securely and transparently stored in a decentralized management environment, including: Using a distributed consensus algorithm, emergency medical record data packets that have passed smart contract review and are allowed to be added to the blockchain network are synchronized among nodes to obtain emergency medical record data packets that have reached a consensus and are verified to be valid by most nodes. Based on the agreed and verified first aid record data package, the agreed and verified first aid record data package is added to the blockchain under decentralized management to generate valid first aid record data that is confirmed without a single controlling entity. Based on the effective emergency medical record data, an off-chain computing mechanism is introduced to process a large amount of emergency medical record data or non-critical transactions that do not need to be reflected on the chain in real time, so as to meet the need for efficient processing and obtain preliminary results after off-chain computing. Using a distributed consensus algorithm, the preliminary results after off-chain computation are verified again to ensure that the preliminary results after off-chain computation meet the standards for joining the main chain, and finally generate emergency rescue record data that is officially added to the blockchain. Based on the emergency medical records data that are finally officially added to the blockchain, emergency medical records are obtained by combining further distributed consensus algorithms and off-chain computing mechanisms, and are securely and transparently stored in a decentralized management environment.

6. The method according to claim 1, characterized in that, The aforementioned securely and transparently stored emergency medical records provide an access control interface, enabling relevant parties to query and verify the records while adhering to strict privacy protection rules. However, unauthorized modification or deletion is not permitted, including: Based on the first aid records that are securely and transparently stored in a decentralized management environment, an access control system is constructed. The access control system is configured to identify and verify the identity of the parties requesting to query or verify the first aid records, thereby obtaining an access control system that ensures that only authorized users operate in accordance with strict privacy protection rules. By utilizing encryption technology and a permission management system, the access control system is enhanced to ensure that each query or verification request undergoes strict identity verification and permission checks, generating a protected access control interface that only allows requests that conform to preset permission rules to pass through. Based on the protected access control interface, different access levels and permission ranges are customized for different roles and needs of relevant parties to obtain customized access permission settings, ensuring that different roles have appropriate access permissions; By leveraging the immutability of blockchain, all query and verification activities based on the customized access permission settings are recorded and processed to generate unchangeable and transparent access logs, ensuring system transparency and post-audit capabilities. Access control policies are automatically executed through smart contracts. Access requests recorded in the immutable and transparent access log are processed automatically according to pre-set rules, generating an access control execution mechanism guaranteed by smart contracts to ensure that unauthorized modification or deletion operations are not allowed. It provides a logging function to record in detail every successful or attempted access behavior in the access control execution mechanism based on the smart contract, including information such as the visitor's identity, access time, and access content, and generates secure and tamper-proof log records stored on the blockchain.

7. The method according to claim 1, characterized in that, After receiving the data packet that has passed the initial compliance check, the following is also included: Based on the data packet that has passed the initial compliance check, an authorization verification process is performed. The smart contract is used to confirm the identity and operation permissions of the emergency responder or submitter, and a data packet with sufficient permissions is generated. Based on the data packet with sufficient permissions, the smart contract is used for final review. If the data packet with sufficient permissions passes all compliance and permission checks, a positive review result is generated. For data packets that fail the review, a negative review result is generated, and a notification mechanism is triggered to inform the relevant parties of the reason. Based on the positive review results, the data packets that pass the smart contract review are marked to obtain emergency medical record data packets that are allowed to be added to the blockchain network.

8. A secure storage system for emergency medical records based on blockchain technology, characterized in that, include: The receiving module is used to receive emergency record data generated in emergency events, and to add timestamps and geographic location information to each emergency record data to obtain emergency record data containing timestamps and geographic location information; The transformation construction module is used to transform the emergency record data containing timestamps and geographical location information using a hash function, and combine it with the identity verification information of emergency personnel and the identifier of emergency equipment to construct an immutable data packet based on a zero-knowledge proof algorithm, thereby obtaining a data packet containing proof of the authenticity and integrity of emergency information. The review module is used to automatically review the compliance and permissions of the data packet containing proof of the authenticity and integrity of the emergency information through a smart contract, and obtain the emergency record data packet that is allowed to be added to the blockchain network. The processing module is used to synchronize the emergency medical record data packets that are allowed to be added to the blockchain network across multiple nodes using a distributed consensus algorithm, and to introduce an off-chain computing mechanism to process a large number of transactions, so as to obtain emergency medical records that are securely and transparently stored in the absence of centralized management. A module is provided for providing an access control interface based on the securely and transparently stored emergency medical records, enabling relevant parties to query and verify the emergency medical records in accordance with strict privacy protection rules, but not allowing unauthorized modification or deletion operations; The step of automatically verifying the compliance and permissions of the data packet containing proof of the authenticity and integrity of the emergency medical information through a smart contract to obtain an emergency medical record data packet that is allowed to be added to the blockchain network includes: Based on the data packets containing proof of the authenticity and integrity of the emergency information, the system receives and processes these data packets, ensuring that each packet contains a timestamp and geographic location information of the emergency event, as well as the identity verification information of the emergency personnel and the identifier of the emergency equipment, generating an emergency record data packet ready for review. The system then uses smart contracts to define review standards, pre-setting rules and conditions in the smart contract based on the emergency record data packets ready for review. These rules include data format, validity of the timestamp, reasonableness of the geographic location information, and accuracy of the identity verification information of the emergency personnel and the identifier of the emergency equipment, generating a smart contract rule set. Based on the smart contract rule set, the system performs automated compliance review of the emergency record data packets ready for review, verifying whether the data packets meet all preset conditions, resulting in a data packet that passes the initial compliance check.

9. A computing device, characterized in that, It includes a processing component and a storage component; the storage component stores one or more computer instructions; the one or more computer instructions are invoked and executed by the processing component to implement a secure storage method for emergency medical records based on blockchain technology as described in any one of claims 1 to 7.

10. A computer storage medium, characterized in that, The device contains a computer program that, when executed by a computer, implements a secure storage method for emergency medical records based on blockchain technology as described in any one of claims 1 to 7.

Images