Financial sharing platform based on blockchain technology

Abstract

The application discloses a financial sharing platform based on a blockchain technology, relates to the field of the blockchain technology, and comprises a medical record access module, a responsibility token generation module, an authorization delegation module, a multi-institution examination and approval circulation module and an intelligent contract triggering module. The medical record access module is used for extracting original data from a medical insurance settlement terminal after an old person completes medical services related to medical insurance, generating a hash value of structured cost information of the original data, and then writing the hash value into a blockchain. The responsibility token generation module is used for generating a responsibility token according to the structured cost information. The authorization delegation module is used for receiving an on-chain delegation operation initiated by a patient or a legal relative of the patient after the token is generated, and transferring the operation permission of the token to other reimbursable agents. The multi-institution examination and approval circulation module is used for synchronously initiating an examination and approval request to an examination and approval subject in a responsibility token transmission process. The application solves the problems of non-unique examination and approval paths and unclear responsibility boundaries.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of blockchains, and particularly to a financial sharing platform based on blockchain technology. BACKGROUND

[0002] At present, the elderly often cannot efficiently complete the medical insurance fee reimbursement procedures in the medical process due to physical inconvenience and limited digital ability. In the prior art, medical insurance reimbursement mostly relies on paper submission and manual approval process, which is prone to problems such as reimbursement delay, approval error or repeated payment.

[0003] At the same time, the data of different approval links is difficult to unify, and the paper archives are at risk of loss and tampering, especially under the background of increasing urban aging, the manual approval path is not scalable, which seriously affects the medical experience and the efficiency of the use of funds of the elderly.

[0004] Therefore, there is an urgent need for a technical solution that can structure the expense information, make the approval process transparent, and clarify the responsibility subject under the premise of ensuring information security and non-tamperability, so as to realize the automation and collaboration of medical insurance expense reimbursement. SUMMARY

[0005] The present application aims to provide a financial sharing platform based on blockchain technology to solve the problems raised in the background.

[0006] To solve the above technical problems, the present application provides the following technical solution: a financial sharing platform based on blockchain technology, comprising a medical record access module, a responsibility token generation module, an authorization delegation module, a multi-agency approval transfer module and an intelligent contract triggering module, the medical record access module, the responsibility token generation module, the authorization delegation module, the multi-agency approval transfer module and the intelligent contract triggering module are communicatively connected with each other;

[0007] The medical record access module is used to extract original data from the medical insurance settlement terminal after the elderly complete medical services related to medical insurance, and generate a hash value of the structured expense information from the original data, and then write the hash value to the blockchain, wherein the original data includes expense details, item code, medical insurance payment amount, advance payment amount and treatment time;

[0008] The responsibility token generation module is used to generate a responsibility token according to the structured expense information;

[0009] The authorization delegation module is used to receive on-chain delegation operations initiated by the patient or his legal relatives after the token is generated, and transfer the operation authority of the token to other reimbursable agents;

[0010] The multi-agency approval circulation module is configured to initiate an approval request to an approval subject synchronously in a responsibility token transmission process according to a preset approval process table, and write an approval opinion, a digital signature of an approver, a processing timestamp and a state hash into a newly generated state snapshot block after each approval subject completes confirmation.

[0011] The smart contract triggering module is configured to judge token state consistency after all approval nodes complete approval, trigger a fund payment contract if all paths are valid and have no ambiguity, and directly transfer reimbursable funds into an account of a person who makes a deposit and write a payment result block.

[0012] According to the above technical solution, the medical record access module further includes a data extraction submodule, a data structured processing submodule, a hash calculation and transaction record generation submodule, and a blockchain writing submodule. The data extraction submodule is configured to establish a communication connection with a medical insurance settlement terminal, accurately extract original data from the medical insurance settlement terminal according to a preset protocol and interface specification after an old person completes medical insurance related medical services, the data structured processing submodule is configured to structure the extracted original data according to a set data structure template, the hash calculation and transaction record generation submodule is configured to generate a digest value for the structured data by using a secure hash algorithm, and the blockchain writing submodule is configured to broadcast the signed transaction record to a blockchain network for verification and consensus confirmation by a blockchain node.

[0013] According to the above technical solution, the specific working process of the medical record access module includes:

[0014] Step S1, a data structure template is set to structure the cost data in the original data;

[0015] Step S2, in the structured processing process, each cost item is split into several items to clearly record the service number, service name, cost amount and medical insurance reimbursement ratio fields;

[0016] Step S3, all fields are arranged in a fixed key-value pair format and sorted in dictionary order according to the field name;

[0017] Step S4, after sorting, the structured data is converted into a standard text string, and then a digest value is generated by using a secure hash algorithm;

[0018] Step S5, the digest value is combined with the patient identity number, hospital number and cost generation timestamp to form a transaction record, and then the hospital information system uses a pre-registered encryption private key to digitally sign the transaction record;

[0019] Step S6: After the signature is completed, the transaction is broadcast to the blockchain network and verified and consensus-confirmed by the blockchain nodes.

[0020] According to the technical solution, the responsibility token generation module further comprises a data receiving submodule, a to-be-signed string splicing submodule, a digital signature submodule, a data encapsulation submodule, and a blockchain submission submodule. The data receiving submodule is configured to receive a structured cost summary value written by the medical record access module, and provide a data basis for subsequent generation of the responsibility token. The to-be-signed string splicing submodule is configured to extract a patient unique identifier, a hospital number, a cost summary value, and a data generation timestamp from the received data, and sequentially splice them into a to-be-signed string. The digital signature submodule is configured to call a digital signature algorithm corresponding to a node private key, perform a private key signature operation on the spliced to-be-signed string, and generate a signature value. The data encapsulation submodule is configured to encapsulate the spliced to-be-signed string, the generated signature value, and a pre-allocated token unique number into a responsibility token data structure in field order, and submit the encapsulated responsibility token data structure to a blockchain network.

[0021] According to the technical solution, the authorization delegation module further comprises an authorization token generation submodule, a permission update submodule, and a proxy operation verification submodule. The authorization token generation submodule is configured to generate an authorization token corresponding to the original responsibility token on the blockchain. The permission update submodule is configured to write the specified operation permission in the authorization token into the permission field of the original responsibility token, and update the state of the original responsibility token. The proxy operation verification submodule is configured to verify the digital signature of the proxy and update the approval path and signature chain of the responsibility token in real time.

[0022] According to the technical solution, the smart contract triggering module further comprises a token state consistency judgment submodule and a fund payment contract triggering submodule. The token state consistency judgment submodule is configured to set a set of approval path sets, analyze the approval state nodes contained in each path, and detect whether there is path ambiguity by defining a path conflict judgment function. The fund payment contract triggering submodule is configured to trigger the fund payment contract according to the judgment result of the token state consistency judgment submodule, directly transfer the reimbursable amount into the account of the person who advances the payment, and write the payment result block.

[0023] According to the technical solution, the step of judging the token state consistency after the approval comprises the following steps:

[0024] A set of approval path sets is set: ;

[0025] Each path contains a set of approval state nodes ;

[0026] Each state node contains a signature value , a timestamp and a state hash ;

[0027] Define the path conflict judgment function:

[0028] ;

[0029] If there is any , the path is ambiguous, and the responsibility token circulation is frozen and an exception state identification block is generated.

[0030] According to the technical scheme, the specific working process of the responsibility token generation module includes:

[0031] Step A1: receiving the structured fee summary value written by the medical record access module;

[0032] Step A2: extracting the patient unique identifier, hospital number, fee summary value and data generation timestamp from the received data, and sequentially splicing them into a to-be-signed string;

[0033] Step A3: calling the digital signature algorithm corresponding to the node private key, performing private key signature operation on the to-be-signed string generated in step A2 to generate a signature value;

[0034] Step A4: encapsulating the to-be-signed string in step A2, the signature value generated in step A3 and the pre-allocated token unique number into a responsibility token data structure in field order, the data structure at least including token number, patient identifier, hospital identifier, fee summary value, timestamp, signature value and current approval state identifier;

[0035] Step A5: submitting the encapsulated responsibility token data structure to the blockchain network, and after the network node completes the digital signature verification and consensus confirmation, the responsibility token is used as an on-chain object that can be circulated in the multi-institutional approval circulation module.

[0036] According to the technical scheme, the specific working process of the authorization delegation module includes:

[0037] Step B1: receiving the authorization request initiated by the patient or his legal relatives on the chain, the authorization request containing the authorization type, the unique identifier of the agent and the authorization period;

[0038] Step B2: verify the sender's digital signature and the authorization person's identity certificate to confirm the legality and integrity of the authorization request;

[0039] Step B3: generating an authorized token corresponding to the original responsibility token on the blockchain, the authorized token containing the original token number, the agent identifier, the authorization type, the authorization start time and the authorization end time;

[0040] Step B4: writing the operation permission specified in the authorized token into the permission field of the original responsibility token, and updating the original responsibility token state to "authorization has taken effect", the updated information containing the agent ID, the authorization timestamp and the permission expiration label;

[0041] Step B5: publishing an authorization completion notification through the on-chain event broadcast mechanism, the notification recording the authorized token ID, the agent identifier and the validity period, and writing into a new state snapshot block;

[0042] Step B6: when the agent exercises the token operation permission, the agent's digital signature is verified and the approval path and signature chain of the responsibility token are updated in real time.

[0043] Compared with the prior art, the beneficial effects achieved by the present application are: by adopting the responsibility token mechanism and the on-chain approval path tracking mechanism, the present application realizes multi-agency information trust, process automatic judgment and intelligent fund distribution without changing the original approval system, and improves the overall reimbursement efficiency and fairness. BRIEF DESCRIPTION OF DRAWINGS

[0044] The accompanying drawings are used to provide a further understanding of the present application, and constitute a part of the specification, together with the embodiments of the present application, to explain the present application, and do not constitute a limitation on the present application. In the drawings:

[0045] Figure 1 A module composition schematic diagram of the financial sharing platform based on the blockchain technology is shown. DETAILED DESCRIPTION

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

[0047] Please refer to Figure 1 The present application provides a technical solution: a financial sharing platform based on the blockchain technology, comprising a medical record access module, a responsibility token generation module, an authorization delegation module, a multi-agency approval flow module and an intelligent contract triggering module, the medical record access module, the responsibility token generation module, the authorization delegation module, the multi-agency approval flow module and the intelligent contract triggering module being communicatively connected with each other;

[0048] The medical record access module is used to extract original data from the medical insurance settlement terminal after the old people complete medical services related to medical insurance, and generate a hash value of the structured cost information of the original data, and then write the hash value to the blockchain, wherein the original data includes cost details, item code, medical insurance payment amount, advance amount and treatment time;

[0049] The responsibility token generation module is used to generate a responsibility token according to the structured cost information;

[0050] The authorization delegation module is used to receive an on-chain delegation operation initiated by the patient or his legal relatives after the token is generated, and transfer the operation permission of the token to other reimbursable agents;

[0051] The multi-agency approval transfer module is used to initiate an approval request to multiple approval subjects such as street offices, mutual aid organizations and finance bureaus during the transfer of the responsibility token according to the preset approval process table, and write the approval opinion, the digital signature of the approver, the processing timestamp and the state hash to the newly generated state snapshot block after each approval subject completes the confirmation;

[0052] The smart contract triggering module is used to judge the consistency of the token state after all the approval nodes complete the approval, and if all the paths are valid and have no ambiguity, trigger the fund payment contract to directly transfer the reimbursable amount into the account of the payer, and write the payment result block.

[0053] The medical record access module further includes a data extraction submodule, a data structuring processing submodule, a hash calculation and transaction record generation submodule, and a blockchain writing submodule. The data extraction submodule is used to establish a communication connection with the medical insurance settlement terminal, and accurately extract original data from the medical insurance settlement terminal according to the preset protocol and interface specification after the old people complete medical services related to medical insurance. The data structuring processing submodule is used to structure the extracted original data according to the set data structure template. The hash calculation and transaction record generation submodule is used to generate a digest value for the structured data by using a secure hash algorithm. The blockchain writing submodule is used to broadcast the signed transaction record to the blockchain network for verification and consensus confirmation by the blockchain node.

[0054] The specific workflow of the medical record access module includes:

[0055] Step S1, set a data structure template to structure the cost data in the original data;

[0056] Step S2: During the structured processing, each cost item is split into several items, and the service number, service name, cost amount and medical insurance reimbursement ratio fields are recorded;

[0057] Step S3: Arrange all fields in a fixed key-value pair format and sort them in dictionary order according to field names to ensure consistency across systems;

[0058] Step S4: After sorting, convert the structured data into a standard text string, then generate a digest value using a secure hash algorithm; this digest value uniquely represents the entire content of the expense information and has the characteristics of irreversibility and unforgeability;

[0059] Step S5: Combine the digest value with the patient ID, hospital number, and expense timestamp into a transaction record, then use the pre-registered encryption private key to digitally sign the transaction record to ensure that the information is authentic and has not been tampered with;

[0060] Step S6: After signing, the transaction is broadcast to the blockchain network and verified and consensus confirmed by the blockchain node; verified transactions are permanently written into the blockchain ledger, forming an unalterable structured expense token, and connected in sequence with other historical transactions through a hash chain structure to form a complete token state chain.

[0061] The responsibility token generation module further includes a data receiving submodule, a to-be-signed string splicing submodule, a digital signature submodule, a data encapsulation submodule, and a blockchain submission submodule. The data receiving submodule is used to receive the structured expense digest value written by the medical record access module, providing a data basis for the generation of the subsequent responsibility token. The to-be-signed string splicing submodule is used to extract the patient unique identifier, hospital number, expense digest value, and data generation timestamp from the received data, and sequentially splice them into a to-be-signed string to provide a to-be-signed data object for the digital signature operation, ensuring the accuracy and integrity of the signature. The digital signature submodule is used to call the digital signature algorithm corresponding to the node private key to perform a private key signature operation on the spliced to-be-signed string to generate a signature value. The data encapsulation submodule is used to encapsulate the spliced to-be-signed string, the generated signature value, and the pre-allocated token unique number into a responsibility token data structure in field order, and submit the encapsulated responsibility token data structure to the blockchain network.

[0062] The authorization delegation module further includes an authorization token generation submodule, a permission update submodule, and a proxy operation verification submodule. The authorization token generation submodule is used to generate an authorization token corresponding to the original responsibility token on the blockchain. The permission update submodule is used to write the specified operation permission in the authorization token into the permission field of the original responsibility token and update the original responsibility token state. The proxy operation verification submodule is used to verify the proxy digital signature and update the approval path and signature chain of the responsibility token in real time.

[0063] The smart contract triggering module further comprises a token state consistency judgment submodule and a fund payment contract triggering submodule, the token state consistency judgment submodule is configured to set a set of approval path set, analyze the approval state nodes contained in each path, and detect whether there is path ambiguity by defining a path conflict judgment function, and the fund payment contract triggering submodule is configured to trigger the fund payment contract according to the judgment result of the token state consistency judgment submodule, and write the payment result block.

[0064] The approval state consistency judgment comprises the following steps:

[0065] A set of approval path set is set: ;

[0066] Each path contains a set of approval state nodes ;

[0067] Each state node contains a signature value , a timestamp and a state hash ;

[0068] A path conflict judgment function is defined:

[0069] ;

[0070] If there is any , the path is ambiguous, the responsibility token circulation is frozen, and an exception state identification block is generated; in the multi-party approval process, the algorithm ensures that the system can automatically detect state inconsistency, avoiding double payment or logical conflict problems caused by concurrent approval.

[0071] The specific working process of the responsibility token generation module comprises:

[0072] Step A1: receiving the structured fee summary value written by the medical record access module;

[0073] Step A2: extracting the patient unique identifier, hospital number, fee summary value and data generation timestamp from the received data, and sequentially splicing them into a to-be-signed string in order;

[0074] Step A3: calling the digital signature algorithm corresponding to the node private key, performing private key signature operation on the to-be-signed string generated in step A2 to generate a signature value;

[0075] Step A4: The to-be-signed string in step A2, the signature value generated in step A3, and the pre-assigned token unique number are encapsulated in the order of fields as a responsibility token data structure, which at least includes token number, patient identification, hospital identification, expense summary value, timestamp, signature value, and current approval status identification;

[0076] Step A5: The encapsulated responsibility token data structure is submitted to the blockchain network. After the network nodes complete digital signature verification and consensus confirmation, the responsibility token is used as an on-chain object that can be circulated in the multi-institutional approval circulation module.

[0077] The specific workflow of the authorization delegation module includes:

[0078] Step B1: Receive the authorization request initiated by the patient or his legal relatives on the chain, which contains the authorization type, agent unique identification, and authorization period;

[0079] Step B2: Verify the sender's digital signature and the authorization person's identity certificate to confirm the legality and integrity of the authorization request;

[0080] Step B3: Generate an authorization token corresponding to the original responsibility token on the blockchain, which contains the original token number, agent identification, authorization type, authorization start time, and authorization expiration time;

[0081] Step B4: Write the operation permission specified in the authorization token into the permission field of the original responsibility token, and update the original responsibility token status to "authorization has taken effect", which contains the agent ID, authorization timestamp, and permission expiration label;

[0082] Step B5: Publish the authorization completion notification through the on-chain event broadcast mechanism, which records the authorization token ID, agent identification, and validity period, and writes into the new state snapshot block;

[0083] Step B6: When the agent exercises the token operation permission (including approval, query, and information submission), verify the agent's digital signature and update the responsibility token's approval path and signature chain in real time, thereby ensuring the traceability and non-repudiation of the agent's operation.

[0084] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks Figure 1 one or more flowcharts and / or blocks

[0085] These computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instructions which implement the function specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks Figure 1 one or more flowcharts and / or blocks

[0086] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks Figure 1 one or more flowcharts and / or blocks

[0087] The embodiments of the present application described above are merely intended to illustrate the present application, but not to limit the present application. The skilled in the art can make many modifications and improvements without departing from the spirit and scope of the present application, which should be protected by the claims.

Claims

1. A financial sharing platform based on blockchain technology, characterized in that, It includes a medical record access module, a responsibility token generation module, an authorization and delegation module, a multi-institutional approval and workflow module, and a smart contract triggering module. The medical record access module, responsibility token generation module, authorization and delegation module, multi-institutional approval and workflow module, and smart contract triggering module are interconnected. The medical record access module is used to extract raw data from the medical insurance settlement terminal after the elderly complete medical insurance-related medical services, generate a hash value of structured cost information from the raw data, and then write the hash value into the blockchain. The raw data includes cost details, project code, medical insurance payment amount, advance payment amount and consultation time. The responsibility token generation module is used to generate responsibility tokens based on the structured fee information; The authorization and delegation module is used to receive on-chain delegation operations initiated by the patient or their legal relatives after the token is generated, and to transfer the operation rights of the token to other reimbursement agents. The multi-agency approval workflow module is used to initiate approval requests to the approval entities simultaneously during the transfer of responsibility tokens according to the preset approval process table, and write the approval opinion, the approver's digital signature, the processing timestamp and the status hash into the newly generated status snapshot block after each approval entity completes the confirmation. The smart contract triggering module is used to determine the consistency of the token status after all approval nodes have completed the approval. If all paths are valid and unambiguous, the fund payment contract is triggered to directly transfer the reimbursement amount to the payer's account and write it into the payment result block. The responsibility token generation module further includes a data receiving submodule, a string concatenation submodule, a digital signature submodule, a data encapsulation submodule, and a blockchain submission submodule. The data receiving submodule receives the structured cost digest value written by the medical record access module, providing a data foundation for the subsequent generation of responsibility tokens. The string concatenation submodule extracts the patient's unique identifier, hospital number, cost digest value, and data generation timestamp from the received data and concatenates them sequentially into a string to be signed. The digital signature submodule calls the digital signature algorithm corresponding to the node's private key to perform a private key signing operation on the concatenated string to be signed, thereby generating a signature value. The data encapsulation submodule encapsulates the concatenated string to be signed, the generated signature value, and the pre-assigned unique token number into a responsibility token data structure according to the field order, and submits the encapsulated responsibility token data structure to the blockchain network. The specific workflow of the responsibility token generation module includes: Step A1: Receive the structured cost digest value written by the medical record access module; Step A2: Extract the patient's unique identifier, hospital number, cost summary value, and data generation timestamp from the received data, and concatenate them in order to form the string to be signed; Step A3: Call the digital signature algorithm corresponding to the node's private key to perform a private key signing operation on the string to be signed generated in Step A2 to generate a signature value; Step A4: Encapsulate the string to be signed in Step A2, the signature value generated in Step A3, and the pre-assigned unique token number into a responsibility token data structure in field order. The data structure includes at least the token number, patient identifier, hospital identifier, cost summary value, timestamp, signature value, and current approval status identifier. Step A5: Submit the encapsulated responsibility token data structure to the blockchain network. After the network nodes complete digital signature verification and consensus confirmation, the responsibility token becomes an on-chain object that can circulate in the multi-institution approval and circulation module.

2. The financial sharing platform based on blockchain technology according to claim 1, characterized in that: The medical record access module further includes a data extraction submodule, a data structuring processing submodule, a hash calculation and transaction record generation submodule, and a blockchain writing submodule. The data extraction submodule is used to establish a communication connection with the medical insurance settlement terminal. After the elderly complete medical insurance-related medical services, it accurately extracts the original data from the medical insurance settlement terminal according to the preset protocol and interface specifications. The data structuring processing submodule is used to organize the extracted original data in a structured manner according to the set data structure template. The hash calculation and transaction record generation submodule is used to generate a digest value from the structured data using a secure hash algorithm. The blockchain writing submodule is used to broadcast the signed transaction records to the blockchain network for verification and consensus confirmation by blockchain nodes.

3. The financial sharing platform based on blockchain technology according to claim 2, characterized in that: The specific workflow of the medical record access module includes: Step S1: Set up a data structure template to organize the cost data in the original data in a structured way; Step S2: During the structured processing, each expense item is broken down into several entries, clearly recording the service number, service name, expense amount, and medical insurance reimbursement ratio fields; Step S3: Arrange all fields in a fixed key-value pair format and sort them alphabetically by field name; Step S4: After sorting, the structured data is converted into a standard text string, and then a digest value is generated using a secure hash algorithm; Step S5: Combine the digest value with the patient's identification number, hospital number, and the time stamp of the charge generation into a transaction record. Then, the hospital information system uses the pre-registered encryption private key to digitally sign the transaction record. Step S6: After signing, the transaction is broadcast to the blockchain network and verified and confirmed by blockchain nodes.

4. The financial sharing platform based on blockchain technology according to claim 1, characterized in that: The authorization delegation module further includes an authorization token generation submodule, a permission update submodule, and a proxy operation verification submodule. The authorization token generation submodule is used to generate an authorization token on the blockchain that corresponds one-to-one with the original responsibility token. The permission update submodule is used to write the operation permissions specified in the authorization token into the permission field of the original responsibility token and update the status of the original responsibility token. The proxy operation verification submodule is used to verify the agent's digital signature and update the approval path and signature chain of the responsibility token in real time.

5. The financial sharing platform based on blockchain technology according to claim 1, characterized in that: The smart contract triggering module further includes a token status consistency judgment submodule and a fund payment contract triggering submodule. The token status consistency judgment submodule is used to set a set of approval paths, analyze the approval status nodes contained in each path, and detect whether there is path ambiguity by defining a path conflict judgment function. The fund payment contract triggering submodule is used to trigger the fund payment contract for paths that meet the judgment conditions based on the judgment result of the token status consistency judgment submodule, directly transfer the reimbursement amount to the payer's account, and write it into the payment result block.

6. The financial sharing platform based on blockchain technology according to claim 1, characterized in that: Determining token status consistency after approval includes the following steps: Define a set of approval paths: ; Each path Includes a set of approval status nodes ; Each state node contains a signature value. timestamp With state hash ; Define a path conflict determination function: ； If there exists any If the path is ambiguous, the circulation of the responsibility token will be frozen and an abnormal status identifier block will be generated.

7. The financial sharing platform based on blockchain technology according to claim 4, characterized in that: The specific workflow of the authorization delegation module includes: Step B1: Receive an authorization request initiated on the blockchain by the patient or their legal relative. The authorization request includes the authorization type, the agent's unique identifier, and the authorization period. Step B2: Verify the legality and completeness of the authorization request by checking the sender's digital signature and the authorizing person's identity credentials; Step B3: Generate an authorization token on the blockchain that corresponds one-to-one with the original responsibility token. The authorization token includes the original token number, agent identifier, authorization type, authorization start time, and authorization end time. Step B4: Write the operation permissions specified in the authorization token into the permission field of the original responsibility token, and update the status of the original responsibility token to "authorization has taken effect". The updated information includes the agent ID, authorization timestamp and permission expiration tag. Step B5: Publish an authorization completion notification through the on-chain event broadcast mechanism. The notification records the authorization token ID, agent identifier, and validity period, and is written into a new state snapshot block. Step B6: When the agent exercises the token operation authority, verify the agent's digital signature and update the approval path and signature chain of the responsibility token in real time.

Images