System and method of electronic health record permissioning and monetization
A system and method for electronic health record permissioning and monetization that can grant or deny access to patient data and pay one or more entities for access to the data is presented. The present disclosure provides for a system configured to provide a patient the ability to: ‘grant,’ ‘deny,’ ‘update,’ and ‘revoke’ the permission to read data for a specific entity, and specific properties within that entity, from their personal data records (e.g., an electronic health record, a Global Patient Record (GPR), pharmaceutical records, demographic records, financial records, criminal records, or other suitable personal information). A Data-Read-Permission request can be a ‘Property Collection’ (PC) containing specific properties that describe the read permission rights and an amount the Data-Client is willing to offer for the Data-Read-Permission rights. This PC can be written as part of a blockchain transaction (TX1), which can be issued by the Data-Client.
1. An electronic health record data read system, comprising:
a blockchain configured to store a plurality of transactions and patient data;
a blockchain reader configured to read blocks from the blockchain;
a global patient record (GPR) database having encrypted and unencrypted GPR data; and
a decrypt server configured to receive a data request from a data client and verify read permission by querying the GPR database to identify the GPR data covered by a preexisting and valid read permission contract, wherein the decrypt server decrypts the encrypted GPR data stored in the GPR database, and wherein the encrypted GPR data is decrypted using the private key of a node where it was stored in the blockchain.
2. The system of claim 1 , wherein the decrypt server can receive a read request generated by the data client.
3. The system of claim 2 , wherein the read request is a message identifying GPR data to be queried and returned.
4. The system of claim 1 , wherein the decrypt server can transmit a read response to the data client.
5. The system of claim 4 , wherein the read response is a message including the requested GPR data.
6. The system of claim 1 , wherein the blockchain reader processes each blockchain transaction within a block and determines if a blockchain transaction contains GPR data.
7. The system of claim 6 , wherein the GPR data is loaded into the GPR database if the blockchain transaction contains GPR data.
8. The system of claim 1 , wherein the GPR data includes a plurality of electronic health records for a plurality of patients.
9. The system of claim 1 , wherein the decrypt server determines if the data client is authorized to transmit the data request.
10. The system of claim 9 , wherein the authorization determination is performed by checking a digital signature provided with the read request.
11. A method of reading electronic health record data, comprising:
storing a plurality of transactions and patient data on a blockchain;
reading blocks from the blockchain via a blockchain reader;
storing encrypted and unencrypted GPR data in a global patient record (GPR) database; and
receiving, via a decrypt server, a data request from a data client and verifying read permission by querying the GPR database to identify the GPR data covered by a preexisting and valid read permission contract, wherein the decrypt server decrypts the encrypted GPR data stored in the GPR database, and wherein the encrypted GPR data is decrypted using the private key of a node where it was stored in the blockchain.
12. The method of claim 11 , wherein the decrypt server can receive a read request generated by the data client.
13. The method of claim 12 , wherein the read request is a message identifying GPR data to be queried and returned.
14. The method of claim 11 , wherein the decrypt server can transmit a read response to the data client.
15. The method of claim 14 , wherein the read response is a message including the requested GPR data.
16. The method of claim 11 , wherein the blockchain reader processes each blockchain transaction within a block and determines if a blockchain transaction contains GPR data.
17. The method of claim 16 , wherein the GPR data is loaded into the GPR database if the blockchain transaction contains GPR data.