Distributed ledger system for managing medical records
Systems and methods are disclosed with respect to using a distributed ledger, such as a blockchain, for managing medical records. The medical records may be accessible by medical institutions such as hospitals, and may be controlled by the patient. The patient may, for example, decide which entities can access and/or edit the medical records.
1. A computer-implemented method for tracking medical histories, the method comprising:
implementing a plurality of servers, each of the plurality of servers maintaining a copy of a distributed ledger;
tracking, at the distributed ledger, (i) a plurality of insurance claims involving a patient and (ii) medical records associated with each of the plurality of insurance claims, including performing the following when an insurance claim involving the patient is filed:
(i) generating, at a first server from the plurality of servers, a particular transaction record representing the filed insurance claim, wherein the particular transaction record includes data pertaining to the filed insurance claim and data pertaining to a particular set of medical records associated with the filed medical insurance claim;
(ii) including transmitting the particular transaction record from the first server to the one or more other servers for a consensus analysis of the transaction record;
(iii) performing, via the plurality of servers, the consensus analysis of the particular transaction record utilizing a consensus mechanism, wherein performing the consensus analysis includes generating a hash value for the transaction record and utilizing the hash value for the transaction record to generate a hash value for a new block, including the transaction record, for the distributed ledger; and
(iv) when the consensus analysis indicates that the plurality of servers have formed a consensus, storing the new block including the particular transaction record to each copy of the distributed ledger at the plurality of servers;
when a request for a medical history report for the patient is received, (i) responding to the request by retrieving, from a copy of the distributed ledger maintained by one of the plurality of server, a medical history pertaining to the patient's filed insurance claims, wherein the medical history includes the medical records associated with each of the plurality of insurance claims and (ii) generating the medical history report based on the retrieved medical history.
2. The method of claim 1 , wherein the consensus mechanism is: a proof of work mechanism, a proof of stake mechanism, or a proof of activity mechanism.
3. The method of claim 1 , wherein the consensus mechanism is: a proof of burn mechanism, a proof of capacity mechanism, or a proof of elapsed time mechanism.
4. The method of claim 1 , wherein the transaction record includes data representing each of: an identity of an insured person, a description of an injury, and one or more medical costs.
5. The method of claim 4 , wherein the transaction record further includes data representing a payout amount.
6. The method of claim 1 , wherein at least one of the servers is a computer possessed by the patient.
7. The method of claim 1 , further including receiving from the patient a list of authorized parties, and wherein the medical history report is only generated when a party requesting the medical history report is on the list of authorized parties.
8. The method of claim 7 , wherein the distributed ledger tracks the list of authorized parties.
9. A system for tracking medical histories, the system comprising:
a plurality of servers each maintaining a copy of a distributed ledger for tracking (i) a plurality of insurance claims involving a patient and (ii) medical records associated with each of the plurality of insurance claims, wherein the plurality of servers includes a first server and one or more other servers;
wherein the first server includes a memory storing instructions that, when executed, cause the first server to:
(i) generate a transaction record including (a) data representing a filed insurance claim and (b) data representing medical information pertaining to the patient and to the filed insurance claim; and
(ii) transmit the transaction record to the one or more other servers for a consensus analysis of the transaction record;
wherein the one or more other servers from the plurality of servers are configured to: (i) perform the consensus analysis of the transaction record utilizing a consensus mechanism, wherein performing the consensus analysis includes generating a hash value for the transaction record and utilizing the hash value for the transaction record to generate a hash value for a new block, including the transaction record, for the distributed ledger; (ii) store the new block including the transaction record at the distributed ledger when the consensus analysis indicates that the plurality of servers have formed a consensus by storing the transaction record to each copy of the distributed ledger at the plurality of servers; and
wherein each of the plurality of servers is further configured to perform the following functions in response to receiving a request for a medical history report for the patient by: (i) retrieving, from a copy of the distributed ledger, a medical history pertaining to the patient's filed insurance claims, wherein the medical history includes the medical records associated with each of the plurality of insurance claims involving the patient, and (ii) generating the medical history report based on the retrieved medical history.
10. The system of claim 9 , wherein the consensus mechanism is: a proof of work mechanism, a proof of stake mechanism, or a proof of activity mechanism.
11. The system of claim 9 , wherein the consensus mechanism is: a proof of burn mechanism, a proof of capacity mechanism, or a proof of elapsed time mechanism.
12. The system of claim 9 , wherein the transaction record includes data representing each of: an identity of an insured person, a description of an injury, and one or more medical costs.
13. The system of claim 12 , wherein the transaction record further includes data representing a payout amount.
14. The system of claim 9 , wherein at least one of the servers is a computer possessed by the patient.
15. The system of claim 9 , further including receiving from the patient a list of authorized parties, and wherein the medical history report is only generated when a party requesting the medical history report is on the list of authorized parties.
16. The system of claim 15 , wherein the distributed ledger tracks the list of authorized parties.