# US 12,217,840 B2 · Electronic healthcare record data blockchain system and process

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 12,217,840 B2
- Document ID: US12217840B2
- Status: Granted
- Kind: B2
- Application number: 18/595,305
- Filed: 2024-03-04
- Published: 2024-06-20
- Granted: 2025-02-04
- Earliest claimed: 2019-06-19
- Assignees: Technologies IP, LLC
- Applicants: Technologies IP, LLC
- Inventors: Ronald Raymond Austríng; Kenneth A. Hill, Sr.; Brad T. Crosslin; Clinton S. Ferguson, III
- Web page: https://patentgrep.com/patent/US12217840B2

## CPC

- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 40/04: Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
- G06Q 50/265: {Personal security, identity or safety}
- G07F 11/10: two or more magazines having a common delivery chute
- G16H 20/10: relating to drugs or medications, e.g. for ensuring correct administration to patients
- H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 63/0414: {during transmission, i.e. party's identity is protected against eavesdropping, e.g. by using temporary identifiers, but is known to the other party or parties involved in the communication}
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- G06Q 10/10: Office automation; Time management
- G06Q 20/3678: {e-cash details, e.g. blinded, divisible or detecting double spending}
- G06Q 30/0222: {During e-commerce, i.e. online transactions}
- G06Q 2220/00: Business processing using cryptography
- H04L 2209/42: Anonymization, e.g. involving pseudonyms
- H04L 2209/88: Medical equipments
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G07F: COIN-FREED OR LIKE APPARATUS (coin sorting G07D3/00; coin testing G07D5/00; {handling coins or paper currencies apart from payment activated apparatus G07D; payment architectures, schemes or protocols G06Q20/00})
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## 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

### Claim 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.

### Claim 2 (depends on 1)

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

### Claim 3 (depends on 2)

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.

### Claim 4 (depends on 1)

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

### Claim 5 (depends on 4)

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.

### Claim 6 (depends on 5)

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.

### Claim 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.

### Claim 8 (depends on 7)

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

### Claim 9 (depends on 8)

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

### Claim 10 (depends on 7)

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

### Claim 11 (depends on 10)

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.

### Claim 12 (depends on 11)

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

### Claim 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.

### Claim 14 (depends on 13)

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.

### Claim 15 (depends on 14)

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.

### Claim 16 (depends on 13)

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.

### Claim 17 (depends on 16)

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.

### Claim 18 (depends on 17)

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.

### Claim 19 (depends on 13)

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.

### Claim 20 (depends on 19)

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