System and method for healthcare security and interoperability
Embodiments facilitate interoperability and secure determination of healthcare costs. An entity may receive a first Electronic Health Record (EHR) sub-block with patient medical coverage information and first treatments and may transmit a first Device Drug Information (DIR) sub-block comprising first treatment classes corresponding to each first treatment, first treatment class members corresponding to each first treatment class, and corresponding first treatment class member cost information. In response, the entity may receive a second EHR sub-block comprising second treatments each: associated with a corresponding first treatment, and selected from corresponding first treatment class members. Upon receipt of a transaction confirmation, the entity may augment a multi-dimensional blockchain with a multi-dimensional block formed by linking: a DIR block including second treatment information, an EHR block including information based on the second EHR sub-block and a transaction block. Payment assistance information determined from the second EHR block may be transmitted to a patient.
1. A processor-implemented method at a first entity comprising:
receiving at least one encrypted first Electronic Health Record (EHR) sub-block decryptable by the first entity, wherein the at least one EHR sub-block comprises patient medical coverage information for a patient and one or more first treatments;
transmitting, in response to the first EHR sub-block, at least one encrypted first Device Drug Information (DIR) sub-block decryptable by at least one corresponding second entity, wherein the at least one first DIR sub-block comprises, for each of the one or more first treatments, a corresponding first treatment class, one or more corresponding first treatment class members associated with each corresponding first treatment class, and for each first treatment class member, corresponding first treatment class member cost information;
receiving, in response to the first DIR sub-block, an encrypted second EHR sub-block decryptable by the first entity, wherein the second EHR sub-block comprises one or more second treatments, wherein each of the one or more second treatments is associated with a corresponding first treatment and each second treatment is selected from the corresponding first treatment class members associated with the corresponding first treatment; and
augmenting, in response to a transaction confirmation, a multi-dimensional blockchain, wherein the multi-dimensional blockchain is augmented with a multi-dimensional block formed by linking: a DIR block comprising information associated with the one or more second treatments, an EHR block comprising information associated with the second EHR sub-block, and a transaction block.
2. The processor-implemented method of claim 1 , wherein, upon receiving the first EHR sub-block, the method further comprises:
determining, for each of the one or more first treatments, the corresponding first treatment class, wherein each corresponding first treatment class comprises the one or more corresponding first treatment class members; and
determining, for each corresponding first treatment class, the one or more corresponding first treatment class member cost information.
3. The processor-implemented method of claim 2 , further comprising:
determining, based on the corresponding first treatment class member cost information for each first treatment class, aggregate cost metrics based on at least one of: the one or more first treatments, or the one or more second treatments, or a combination thereof.
4. The processor-implemented method of claim 1 , wherein the first EHR sub-block comprises patient-specific parameters and the at least one treatment class is determined based on the patient-specific parameters.
5. The processor-implemented method of claim 4 , wherein the patient-specific parameters comprise patient co-morbidity information.
6. The processor-implemented method of claim 4 , wherein the patient-specific parameters comprise route of administration information.
7. The processor-implemented method of claim 4 , wherein the patient-specific parameters comprise safety and efficacy information.
8. The processor-implemented method of claim 4 , wherein the patient-specific parameters comprise patient location information.
9. The processor-implemented method of claim 1 , wherein, for each first treatment, the corresponding first treatment class and the one or more corresponding first treatment class member cost information for each treatment class member are determined based on the patient medical coverage information.
10. The processor-implemented method of claim 9 , wherein the one or more corresponding first treatment class member cost information is determined based further on providers located within a specified distance of a patient location, wherein location information for the patient is comprised in the first EHR sub-block.
11. The processor-implemented method of claim 1 , wherein the one or more corresponding first treatment class member cost information includes one or more of:
a patient specific out-of-pocket cost corresponding to each corresponding first treatment class member for a corresponding treatment unit; or
a patient-specific estimated total out-of-pocket cost corresponding to each corresponding first treatment class member for a typical treatment duration; or
a patient-specific estimated total out-of-pocket cost corresponding to each corresponding first treatment class member for the remaining duration of a medical coverage plan associated with the patient.
12. The processor-implemented method of claim 1 , wherein, upon receiving the second EHR sub-block, the method further comprises:
determining payment assistance information for at least one of the one or more second treatments; and
transmitting the payment assistance information with a transaction confirmation to a patient.
13. The processor-implemented method of claim 1 , further comprising:
transmitting a transaction confirmation comprising at least one prescription for the one or more second treatments along with payment assistance information to the patient.
14. A computing device for a first entity comprising:
a memory,
a communications interface, and
a processor coupled to the memory and the communications interface, wherein the processor is configured to:
receive at least one encrypted first Electronic Health Record (EHR) sub-block decryptable by the first entity, wherein the at least one EHR sub-block comprises patient medical coverage information for a patient and one or more first treatments;
transmit, in response to the first EHR sub-block, at least one encrypted first Device Drug Information (DIR) sub-block decryptable by at least one corresponding second entity, wherein the at least one first DIR sub-block comprises, for each of the one or more first treatments, a corresponding first treatment class, one or more corresponding first treatment class members associated with each corresponding first treatment class, and for each first treatment class member, corresponding first treatment class member cost information;
receive, in response to the first DIR sub-block, an encrypted second EHR sub-block decryptable by the first entity, wherein the second EHR sub-block comprises one or more second treatments, wherein each of the one or more second treatments is associated with a corresponding first treatment and each second treatment is selected from the corresponding first treatment class members associated with the corresponding first treatment; and
augment, in response to a transaction confirmation, a multi-dimensional blockchain, wherein the multi-dimensional blockchain is augmented with a multi-dimensional block formed by linking: a DIR block comprising information associated with the one or more second treatments, an EHR block comprising information associated with the second EHR sub-block, and a transaction block.
15. The computing device of claim 14 , wherein, upon receiving the first EHR sub-block, the method further comprises:
determine, for each of the one or more first treatments, the corresponding first treatment class, wherein each corresponding first treatment class comprises the one or more corresponding first treatment class members; and
determine, for each corresponding first treatment class, the one or more corresponding first treatment class member cost information.
16. The computing device of claim 15 , further comprising:
determine, based on the corresponding first treatment class member cost information for each first treatment class, aggregate cost metrics based on at least one of: the one or more first treatments, or the one or more second treatments, or a combination thereof.
17. The computing device of claim 14 , wherein the first EHR sub-block comprises patient-specific parameters and the at least one treatment class is determined based on the patient-specific parameters.
18. The computing device of claim 14 , wherein the one or more corresponding first treatment class member cost information includes one or more of:
a patient specific out-of-pocket cost corresponding to each corresponding first treatment class member for a corresponding treatment unit; or
a patient-specific estimated total out-of-pocket cost corresponding to each corresponding first treatment class member for a typical treatment duration; or
a patient-specific estimated total out-of-pocket cost corresponding to each corresponding first treatment class member for the remaining duration of a medical coverage plan associated with the patient.
19. The computing device of claim 14 , wherein, upon receiving the second EHR sub-block, the method further comprises:
determine payment assistance information for at least one of the one or more second treatments; and
transmit the payment assistance information with a transaction confirmation to a patient.
20. A non-transitory computer-readable medium comprising executable instructions to configure a processor to:
receive at least one encrypted first Electronic Health Record (EHR) sub-block decryptable by the first entity, wherein the at least one EHR sub-block comprises patient medical coverage information for a patient and one or more first treatments;
transmit, in response to the first EHR sub-block, at least one encrypted first Device Drug Information (DIR) sub-block decryptable by at least one corresponding second entity, wherein the at least one first DIR sub-block comprises, for each of the one or more first treatments, a corresponding first treatment class, one or more corresponding first treatment class members associated with each corresponding first treatment class, and for each first treatment class member, corresponding first treatment class member cost information;
receive, in response to the first DIR sub-block, an encrypted second EHR sub-block decryptable by the first entity, wherein the second EHR sub-block comprises one or more second treatments, wherein each of the one or more second treatments is associated with a corresponding first treatment and each second treatment is selected from the corresponding first treatment class members associated with the corresponding first treatment; and
augment, in response to a transaction confirmation, a multi-dimensional blockchain, wherein the multi-dimensional blockchain is augmented with a multi-dimensional block formed by linking: a DIR block comprising information associated with the one or more second treatments, an EHR block comprising information associated with the second EHR sub-block, and a transaction block.