Decentralized data authentication system for creation of integrated lifetime health records
A decentralized data authentication system integrates blockchain technologies, independent verification software, a decentralized certificate authority system implemented in the cloud, and a centralized redundant database system that together form data portability systems and data longevity systems that enable the creation of integrated lifetime health records that can be accessed by the patient, provider, and payer using public/private keys. Data portability is provided through creation of a decentralized certificate authority system that allows users to sign and later verify data that has been offline. The decentralized certificate authority system also enables tracking of data and timestamping of data via a neutral timestamping mechanism, such as the blockchain, that cannot be altered.
1. A decentralized data authentication system comprising:
decentralized data storage;
a memory comprising instructions; and
one or more processors in communication with the memory, the one or more processors executing the instructions to implement a blockchain comprising a Merkle tree and:
a decentralized certificate authority including a certificate verification engine that takes a Merkle branch, record data, and users' keys as input and generates a hash of the record data, signs the hashed data using the users' keys to form signature data, and provides a validity response for the record data;
a Merkle tree engine including a blockchain OP_RETURN writer/reader that hashes the signature data and stores the hashed signature data in the Merkle tree of the blockchain and stores a Merkle root in the blockchain using an OP_RETURN opcode; and
a data connectivity cloud that encrypts and stores the signature data and Merkle tree created from the record data redundantly in the decentralized data storage,
wherein the Merkle tree engine comprises a hashing algorithm that receives input data, hashes the input data to create hashed data, signs the hashed data with a key assigned to a user to form signed hashed data, encrypts the signed hashed data, and stores the encrypted signed hashed data in the data connectivity cloud.
2. The system of claim 1 , wherein the decentralized certificate authority accepts record data, signature data, and a user's public key as input, computes the validity of a signature of the signature data, and returns the validity response indicating whether the record data may be imported into the system and stored in the decentralized data storage.
3. The system of claim 1 , wherein the blockchain timestamps the hashed signature data stored to the Merkle tree and the Merkle root and timestamps the Merkle root using the OP_RETURN opcode to generate timestamp data, and the timestamp data and a transaction and block hash from the Merkle root are stored in the data connectivity cloud.
4. The system of claim 1 , wherein the Merkle tree engine includes independent verification software that verifies that a user's Merkle branch for the user's records matches the Merkle root in the blockchain.
5. The system of claim 4 , wherein the independent verification software receives the user's Merkle branch, the user's record data, and the user's public key as input and generates a validity response indicating whether or not a verification test is passed using hash checksums and digital signature algorithms.
6. The system of claim 1 , wherein the blockchain comprises a lifetime health record of health data of a patient that is accessed and updated using the patient's public key and a physician's public key.
7. The system of claim 1 , wherein the decentralized certificate authority enables users to sign and later verify authenticity of a record that has been offline by checking a digital signature of the record against the record data stored in the decentralized data storage.
8. The system of claim 1 , wherein the data connectivity cloud comprises a centralized redundant database, the decentralized data storage, cloud storage, and storage local to a user processing device.
9. The system of claim 1 , wherein the Merkle tree engine further hashes the signed hashed data and stores the hashed signed hashed data into a Merkle tree of the Merkle tree engine.
10. The system of claim 9 , wherein the Merkle tree engine further encrypts the hashed signed hashed data and stores the encrypted hashed signed hashed data in the data connectivity cloud.
11. The system of claim 1 , wherein the Merkle tree engine broadcasts OP_RETURN validation data to user processing devices.
12. The system of claim 1 , wherein the Merkle tree engine compresses the signature data into a Merkle tree and uploads the Merkle tree of signature data to the data connectivity cloud.
13. The system of claim 1 , wherein the certificate verification engine takes the Merkle branch, a user's health record data, and a user's key as input and generates a response indicating whether the user's health record data matches the Merkle root in the blockchain.
14. A decentralized data authentication system comprising:
decentralized data storage;
a memory comprising instructions; and
one or more processors in communication with the memory, the one or more processors executing the instructions to implement a. blockchain comprising a Merkle tree and:
a decentralized certificate authority that accepts record data, signature data, and a user's public key as input, computes the validity of a signature of the signature data, and returns a validity response indicating whether the record data may be imported into the system and stored in the decentralized data storage, the decentralized certificate authority including a certificate verification engine that takes a Merkle branch, the record data, and users' keys as input and generates a hash of the record data, signs the hashed data using the users' keys to form signature data, and provides the validity response for the record data;
a Merkle tree engine including a blockchain OP_RETURN writer/reader that hashes the signature data and stores the hashed signature data in the Merkle tree of the blockchain and stores a Merkle root in the blockchain using an OP_RETURN opcode; and
a data connectivity cloud that encrypts and stores the signature data and Merkle tree created from the record data redundantly in the decentralized data storage,
wherein the blockchain timestamps the hashed signature data stored to the Merkle tree and the Merkle root and timestamps the Merkle root using the OP_RETURN opcode to generate timestamp data, and the timestamp data and a transaction and block hash from the Merkle root are stored in the data connectivity cloud.
15. The system of claim 14 , wherein the Merkle tree engine includes independent verification software that verifies that a user's Merkle branch for the user's records matches the Merkle root in the blockchain.
16. The system of claim 15 , wherein the independent verification software receives the user's Merkle branch, the user's record data, and the user's public key as input and generates a validity response indicating whether or not a verification test is passed using hash checksums and digital signature algorithms.
17. A decentralized data authentication system comprising:
decentralized data storage;
a memory comprising instructions; and
one or more processors in communication with the memory, the one or more processors executing the instructions to implement a blockchain comprising a lifetime health record of health data of a patient that is accessed and updated using the patient's public key and a physician's public key, the blockchain comprising a Merkle tree and:
a decentralized certificate authority including a certificate verification engine that takes a Merkle branch, a user's health record data, and a user's key as input and generates a hash of the record data, signs the hashed data using the users' keys to form signature data, and provides a response indicating whether the user's health record data matches the Merkle root in the blockchain;
a Merkle tree engine including a blockchain OP_RETURN writer/reader that hashes the signature data and stores the hashed signature data in the Merkle tree of the blockchain and stores a Merkle root in the blockchain using an OP_RETURN opcode; and
a data connectivity cloud that encrypts and stores the signature data and Merkle tree created from the record data redundantly in the decentralized data storage.
18. The system of claim 17 , wherein the decentralized certificate authority enables users to sign and later verify authenticity of a record that has been offline by checking a digital signature of the record against the record data stored in the decentralized data storage.
19. The system of claim 17 , wherein the Merkle tree engine compresses the signature data into a Merkle tree and uploads the Merkle tree of signature data to the data connectivity cloud.