IP Library › Granted Patent US 12,682,996
Granted Patent B2
US 12,682,996 · App. 19/044,337 · Granted Jul 14, 2026

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)
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,682,996
App. No.
19/044,337
Granted
Jul 14, 2026
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 (32)

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

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

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

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

generate, in response to a determination that a current record exists for the user, a first single-purpose ID for a user, wherein the first single-purpose ID enables a blockchain system to use the first single-purpose ID instead of the user identifying information;

receive a first electronic prescription;

initiate a first transaction on the blockchain using the first single-purpose ID, the first electronic prescription, and no user-identifying information;

automatically receive preferences or legal requirements related to the user;

implement a smart contract configured to define workflow processes, triggering events, or pricing based on the automatically received preferences or legal requirements related to the user, and write an edit record to the blockchain;

generate and write a close record to the blockchain including output from the smart contract;

based on the output from the smart contract, initiate one or more digital currency transactions related to the first transaction once the close record has been written to the blockchain; and

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

2 . The electronic record data blockchain system of claim 1 , wherein the smart contract is used to streamline payments between stakeholders and the user.

3 . The electronic record data blockchain system of claim 1 , wherein the smart contract determines the final payment amount paid based on certain conditions.

4 . The electronic record data blockchain system of claim 1 , wherein the smart contract prompts the user to make a selection via a user device.

5 . The electronic record data blockchain system of claim 1 , wherein the blockchain system mitigates data discrepancies for electronic patient data.

6 . The electronic record data blockchain system of claim 1 , wherein once the first transaction is completed, the first single-purpose ID can only be used to read information associated with the first transaction from the blockchain.

7 . A method of processing a blockchain transaction, 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 user, the query including identifying information associated with the user;

generating, in response to a determination that a current record exists for the user, a first single-purpose ID for a user, wherein the first single-purpose ID enables a blockchain system to use the first single-purpose ID instead of the user identifying information;

receiving a first electronic prescription;

initiating a first transaction on the blockchain using the first single-purpose ID, the first electronic prescription, and no user-identifying information;

automatically receiving preferences or legal requirements related to the user;

implementing a smart contract configured to define workflow processes, triggering events, or pricing, based on the automatically received preferences or legal requirements related to the user, and write an edit record to the blockchain;

generating and writing a close record to the blockchain including output from the smart contract;

based on the output from the smart contract, initiating one or more digital currency transactions related to the first transaction once the close record has been written to the blockchain;

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

8 . The method of claim 7 , wherein the smart contract is used to streamline payments between stakeholders and the user.

9 . The method of claim 7 , wherein the smart contract determines the final payment amount paid based on certain conditions.

10 . The method of claim 7 , wherein the smart contract prompts the user to make a selection via a user device.

11 . The method of claim 7 , wherein the blockchain system mitigates data discrepancies for electronic patient data.

12 . The method of claim 7 , wherein once the first transaction is completed, the first single-purpose ID can only be used to read information associated with the first transaction from the blockchain.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 3, 2025
From: AUSTRING, RONALD RAYMOND; HILL, KENNETH A.; CROSSLIN, BRAD T.; FERGUSON, CLINTON S., III
To: ELECTRONIC HEALTH RECORD DATA, INC.
Reel/Frame 070093/0384 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 3, 2025
From: SYNERIO TECHNOLOGIES, INC.
To: TECHNOLOGIES IP, LLC
Reel/Frame 070093/0539 →
CHANGE OF NAME Recorded Feb 3, 2025
From: ELECTRONIC HEALTH RECORD DATA, INC.
To: SYNERIO TECHNOLOGIES, INC.
Reel/Frame 070609/0218 →
Continuity (5)
Continuation 18595305 · Mar 4, 2024
Continuation 16906710 · Jun 19, 2020
Provisional Application 62863655 · Jun 19, 2019
Provisional Application 62863637 · Jun 19, 2019
Related Publication 20250182867A1 · Jun 5, 2025
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/hty.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]