Encrypted data store for records

1. A method performed by a processing system, the method comprising:

receiving a patient key from a patient;

accessing a provider identifier corresponding to a first provider;

generating a first provider key based on the patient key and the provider identifier;

determining a first location in a metadata tree of the patient for a first electronic health record;

generating a first record key for the first electronic health record based on the first location and the first provider key corresponding to the first provider;

encrypting the first electronic health record using the first record key to generate a first encrypted record;

providing the first encrypted record to an encrypted data store;

updating the first location in the metadata tree to include a first reference to the first encrypted record in the encrypted data store; and

providing the metadata tree to a metadata store that is accessible by a second provider.

2. The method of claim 1 wherein a second location in the metadata tree includes a second reference to a second encrypted record in the encrypted data store, wherein the second encrypted electronic health record is generated by a second provider, and wherein the second provider is not affiliated with the first provider.

3. The method of claim 2 further comprising:

receiving a second record key for the second encrypted record, the second record key generated based on the second location in the metadata tree that includes the second reference and a second provider key corresponding to the second provider, the second provider key generated from the patient key;

accessing the second encrypted record from the encrypted data store; and

decrypting the second encrypted record using the second record key.

4. The method of claim 1 further comprising:

determining a second location in the metadata tree of the patient for a second electronic health record;

generating a second record key for the second electronic health record based on the second location and the first provider key;

encrypting the second electronic health record using the second record key to generate a second encrypted record; and

providing the second encrypted record to the encrypted data store.

5. The method of claim 4 wherein the first record key differs from the second record key such that the first record key is not usable to decrypt the second encrypted record and the second record key is not usable to decrypt the first encrypted record.

6. A processing system comprising:

a set of one or more processors; and

a memory storing a set of instructions that, when executed by the set of processors, cause the set of processors to:

access a metadata tree from a metadata store that is accessible to a patient, a first provider, and a second provider that is not affiliated with the first provider;

determine a first location in the metadata tree of the patient that corresponds to a first encrypted electronic health record in an encrypted data store;

generate a first record key for the encrypted electronic health record based on the first location and a first provider key corresponding to first provider;

generate the first provider key based on a patient key corresponding to the patient;

access the first encrypted electronic health record from the encrypted data store using the first reference; and

decrypt the first encrypted electronic health record using the first record key.

7. The processing system of claim 6 wherein the first location in the metadata tree includes a first reference to the first encrypted electronic health record in the encrypted data store, wherein a second location in the metadata tree includes a second reference to a second encrypted electronic health record in the encrypted data store, wherein the second encrypted electronic health record is generated by the second provider, and wherein the second provider is not affiliated with the first provider.

8. The processing system of claim 7 wherein the first record key is not usable to decrypt the second encrypted electronic health record, wherein a second record key is usable to decrypt the second encrypted electronic health record, and wherein the second record key is not usable to decrypt the first encrypted electronic health record.

9. An article comprising at least one non-transitory machine-readable storage medium storing instructions that, when executed by a processing system, cause the processing system to:

access a metadata tree comprising a first location including a first reference to a first encrypted electronic health record in an encrypted data store and a second location including a second reference to a second encrypted electronic health record in the encrypted data store, wherein the second encrypted electronic health record is generated by a second provider that is not affiliated with a first provider;

determine the first location in the metadata tree of a patient that corresponds to the first encrypted electronic health record, the first encrypted electronic health record generated by the first provider;

receive a first record key for the first encrypted electronic health record, the first record key generated based on the first location and a first provider key corresponding to the first provider, the first provider key generated based on a patient key corresponding to the patient;

update the first location in the metadata tree to include the first reference to the first encrypted electronic health record in the encrypted data store;

access the first encrypted electronic health record from the encrypted data store using the first reference; and

decrypt, by the second provider, the first encrypted electronic health record using the first record key.

10. The article of claim 9 , wherein the first record key is not usable to decrypt the second encrypted electronic health record, wherein a second record key is usable to decrypt the second encrypted electronic health record, and wherein the second record key is not usable to decrypt the first encrypted electronic health record.

11. The article of claim 9 , wherein the instructions, when executed by the processing system, cause the processing system to:

request the first record key from the first provider; and

receive the first record key from the first provider.

12. The article of claim 9 , wherein the instructions, when executed by the processing system, cause the processing system to:

request the first record key from the patient; and

receive the first record key from the patient.

13. The article of claim 9 , wherein the instructions, when executed by the processing system, cause the processing system to:

determine the second location in the metadata tree of the patient for the second encrypted electronic health record;

receive a second record key for the second encrypted electronic health record based on the second location and the first provider key;

update the second location in the metadata tree to include the second reference to the second encrypted electronic health record in the encrypted data store;

access the second encrypted electronic health record from the encrypted data store using the second reference; and

decrypt, by the second provider, the second encrypted electronic health record using the second record key.

14. The article of claim 13 , wherein the instructions, when executed by the processing system, cause the processing system to:

request the second record key from the first provider; and

receive the second record key from the first provider.

15. The article of claim 13 , wherein the instructions, when executed by the processing system, cause the processing system to:

request the second record key from the patient; and

receive the second record key from the patient.