IP Library › Granted Patent US 12,217,840
Granted Patent B2
US 12,217,840 · App. 18/595,305 · Granted Feb 4, 2025

Electronic healthcare record data blockchain system and process

Inventors: Ronald Raymond Austríng (English Harbour, AG); Kenneth A. Hill, Sr. (Fort Worth, TX); Brad T. Crosslin (Keller, TX); Clinton S. Ferguson, III (Arlington, TX)
Assignee: Technologies IP, LLC
G16H10/60G16H20/10H04L9/0637H04L9/50G06Q10/10G06Q20/3678G06Q30/0222G06Q2220/00
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,217,840
App. No.
18/595,305
Granted
Feb 4, 2025
Kind
B2
Abstract

An Electronic Health Record (EHR) data blockchain system configured to allow multiple entities (e.g., pharmacy industry entities and healthcare providers that can act as data, service, product and service providers, and consumers) to connect to an EHR patient transaction blockchain (e.g., EHR-DATA-BC) and an EHR Data Patient Portal (e.g., EHR-Data-PP) to provide a centralized location for messages and subsequent edits to ensure uniform message data is presented. The EHR data blockchain system can include an EHR Data API, an EHR patient transaction blockchain API, and an EHR patient transaction blockchain. The EHR data blockchain system can provide workflow on the blockchain that can utilize smart contracts to define workflow processes, expected outcomes, and financial costs. When a prescription transaction is complete, it will result in the settlement of each of the smart contracts that were added to the prescription workflow.

Claims (46)

1. An electronic health record data blockchain system configured to process a prescription transaction for a patient, comprising:

one or more computer-readable storage media configured to store a blockchain;

a computer system comprising one or more processors programmed to execute computer program instructions that, when executed, cause the computer system to:

receive a query related to a patient, the query including patient identifying information associated with the patient;

generate, in response to a determination that a current record exists for the patient, a first single-purpose patient ID (SPPID) for a patient, wherein the first SPPID enables the electronic health record data blockchain system to use the first SPPID instead of the patient identifying information, and the first SPPID can be used only until the prescription transaction is completed;

receive a first electronic prescription having a plurality of parameters from an electronic medical record system;

initiate a first prescription transaction on the blockchain using the first electronic prescription, the first SPPID, and no patient-identifying information;

generate a smart contract configured to determine whether any drug interactions exist such that changes need to be made to the prescription and write an edit record to the blockchain;

generate a close record indicating a drug and a price to be paid and write the close record to the blockchain;

initiate one or more digital currency transactions related to the prescription transaction once the close record has been written to the blockchain;

abandon use of the first SPPID after the close record has been written to the blockchain, wherein abandoning the use of the first SPPID after the close record has been written to the blockchain prevents exposure of information from a subsequent prescription transaction associated with another SPPID, such that any potential compromise of the first SPPID compromises information from the first prescription transaction and not the subsequent prescription transaction.

2. The electronic health record data blockchain system of claim 1 , wherein the prescription transaction edit changes a dosage amount or a dosage frequency.

3. The electronic health record data blockchain system of claim 2 , wherein the prescription transaction edit is generated from an analysis of received patient clinical data and the electronic prescription.

4. The electronic health record data blockchain system of claim 1 , wherein the prescription transaction edit changes the drug prescribed based on potential drug interactions.

5. The electronic health record data blockchain system of claim 4 , wherein the prescription transaction edit is generated from an analysis of transaction information with patient clinical data retrieved from the third-party databases.

6. The electronic health record data blockchain system of claim 5 , wherein the third party databases include information about potential drug interactions with other drugs and patient risk factors.

7. A method of providing blockchain-based electronic health record data patient transactions, the method implemented by a server system comprising one or more processors executing computer program instructions that, when executed, perform the method, comprising:

receiving a query related to a patient, the query including patient identifying information associated with the patient;

generating, in response to a determination that a current record exists for the patient, a first single-purpose patient ID (SPPID) for a patient, wherein the first SPPID enables the electronic health record data blockchain system to use the first SPPID instead of the patient identifying information, and the first SPPID can be used only until the prescription transaction is completed;

receiving a first electronic prescription having a plurality of parameters from an electronic medical record system;

initiating a first prescription transaction on the blockchain using the first electronic prescription, the first SPPID, and no patient-identifying information;

generating a smart contract configured to determine whether any drug interactions exist such that changes need to be made to the prescription and write an edit record to the blockchain;

generating a close record indicating a drug and a price to be paid and write the close record to the blockchain;

initiating one or more digital currency transactions related to the prescription transaction once the close record has been written to the blockchain;

abandoning use of the first SPPID after the close record has been written to the blockchain, wherein abandoning the use of the first SPPID after the close record has been written to the blockchain prevents exposure of information from a subsequent prescription transaction associated with another SPPID, such that any potential compromise of the first SPPID compromises information from the first prescription transaction and not the subsequent prescription transaction.

8. The method of claim 7 , wherein the prescription transaction edit changes a dosage amount or a dosage frequency.

9. The method of claim 8 , wherein the prescription transaction edit is generated from an analysis of received patient clinical data and the electronic prescription.

10. The method of claim 7 , wherein the prescription transaction edit changes the drug prescribed based on potential drug interactions.

11. The method of claim 10 , wherein the prescription transaction edit is generated from an analysis of transaction information with patient clinical data retrieved from the third-party databases.

12. The method of claim 11 , wherein the third-party databases include information about potential drug interactions with other drugs and patient risk factors.

13. An electronic health record data blockchain system configured to process a prescription transaction for a patient, comprising:

one or more computer-readable storage media configured to store a blockchain; and

a computer system comprising one or more processors programmed to execute computer program instructions to make one or more edits to a first prescription transaction stored on the blockchain, including:

an EHR application programming interface (API) configured to access and retrieve patient identifiable information (PII) and generate a non-patient-identifiable Single Purpose Patient ID (SPPID) for a patient, wherein the first SPPID enables the electronic health record data blockchain system to use the first SPPID instead of the patient identifying information, and abandon use of the first SPPID after the prescription transaction is completed, wherein abandoning the use of the first SPPID after the close record has been written to the blockchain prevents exposure of information from a subsequent prescription transaction associated with another SPPID, such that any potential compromise of the first SPPID compromises information from the first prescription transaction and not the subsequent prescription transaction, and

a blockchain API configured to:

store the SPPID and non-patient-identifying information related to the patient transaction on the blockchain, initiating the first prescription transaction on the blockchain using the first electronic prescription, the first SPPID, and no patient-identifying information;

generate a smart contract configured to determine whether any drug interactions exist such that changes need to be made to the prescription and write an edit record to the blockchain;

generate a close record indicating a drug and a price to be paid and write the close record to the blockchain;

initiate one or more digital currency transactions related to the prescription transaction once the close record has been written to the blockchain.

14. The electronic health record data blockchain system of claim 13 , wherein the blockchain API edits the prescription transaction by changing a dosage amount or a dosage frequency.

15. The electronic health record data blockchain system of claim 14 , wherein the prescription transaction edit is generated from an analysis of received patient clinical data and the electronic prescription.

16. The electronic health record data blockchain system of claim 13 , wherein the blockchain API edits the prescription transaction by changing the drug prescribed based on potential drug interactions.

17. The electronic health record data blockchain system of claim 16 , wherein the prescription transaction edit is generated from an analysis of transaction information with patient clinical data retrieved from the third-party databases.

18. The electronic health record data blockchain system of claim 17 , wherein the third party databases include information about potential drug interactions with other drugs and patient risk factors.

19. The electronic health record data blockchain system of claim 13 , wherein the smart contract exchanges digital currency between the parties involved in the smart contract.

20. The electronic health record data blockchain system of claim 19 , wherein the digital currency includes utility tokens or vouchers.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 7, 2024
From: AUSTRING, RONALD RAYMOND; HILL, KENNETH A., SR.; CROSSLIN, BRAD T.; FERGUSON, CLINTON S., III
To: ELECTRONIC HEALTH RECORD, INC.
Reel/Frame 066685/0421 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 7, 2024
From: SYNERIO TECHNOLOGIES, INC.
To: TECHNOLOGIES IP, LLC
Reel/Frame 066686/0660 →
CHANGE OF NAME Recorded Mar 7, 2024
From: ELECTRONIC HEALTH RECORD DATA, INC.
To: SYNERIO TECHNOLOGIES, INC
Reel/Frame 066884/0195 →
Continuity (4)
Continuation 16906710 · Jun 19, 2020
Provisional Application 62863655 · Jun 19, 2019
Provisional Application 62863637 · Jun 19, 2019
Related Publication 20240203548A1 · Jun 20, 2024
References Cited (30)
US 8917165B2 · Marques · 2014 [cited by applicant]
US 20020007284A1 · Schurenberg et al. · 2002 [cited by applicant]
US 20030005312A1 · Sato · 2003 [cited by applicant]
US 20090208011A1 · Ricciardi et al. · 2009 [cited by applicant]
US 20120323717A1 · Kirsch · 2012 [cited by applicant]
US 20160117471A1 · Belt · 2016 [cited by applicant]
US 20160335397A1 · Blum · 2016 [cited by applicant]
US 20180117446A1 · Tran et al. · 2018 [cited by applicant]
US 20180326291A1 · Tran · 2018 [cited by applicant]
US 20190034924A1 · Prabhu · 2019 [cited by applicant]
US 20190057763A1 · Stockert et al. · 2019 [cited by applicant]
US 20190156938A1 · Brunner · 2019 [cited by examiner]
US 20190198144A1 · Blackley · 2019 [cited by examiner]
US 20190206536A1 · Hausman · 2019 [cited by examiner]
US 20190303610A1 · Bodegas Martinez · 2019 [cited by examiner]
US 20200057867A1 · Aunger · 2020 [cited by examiner]
US 20200402624A1 · Austring · 2020 [cited by applicant]
US 20200402629A1 · Austring · 2020 [cited by applicant]
US 20210004990A1 · Lee · 2021 [cited by applicant]
US 20220092566A1 · Austring · 2022 [cited by applicant]
US 20220093225A1 · Austring · 2022 [cited by applicant]
WO 2017027974A1 · 2017 [cited by applicant]
WO WO2018064645A1 · 2018 [cited by examiner]
WO 2018152410A1 · 2018 [cited by applicant]
WO 2019083897A1 · 2019 [cited by applicant]
WO 2020041528A1 · 2020 [cited by applicant]
Li, P., Nelson, S. D., Malin, B. A., & Chen, Y. (2019). DMMS: A decentralized blockchain ledger for the management of medication histories. Blockchain in Healthcare Today, 2, n/a. doi:http://dx.doi.org/10.30953/bhty.v2.… [cited by examiner]
Shrier et al., Blockchain and health IT: Algorithms, Privacy, and Data—Whitepaper, Aug. 8, 2016, pp. 74-84. [cited by applicant]
Li, et al. (2019). DMMS: A decentralized blockchain ledger for the management of medication histories. Blockchain in Healthcare today, 2, n/z. doi:http://dx.doi.org/10.30953/bhty.v2.38 (Year: 2019). [cited by applicant]
Samsi, et al., A Mechanism for Privacy Preserving in Healthcare Organizations, pp. 208-213, Faculty of Computing, Universiti Teknologi Malaysia, 2014. [cited by applicant]